It's not that easy. You can have ext2 filesystems on ROM devices or a
network block device. And it should be possible to compile a kernel w/o IDE
and SCSI, but with ext2fs and nbd.
If you want to put a warning for this case, OK, go ahead.
> Likewise, a kernel compiled with NFS support but without networking
> support doesn't make a great deal of sense, but appears selectable; I
> can't check at the moment, so can't be sure re that at this point...
... and the needed modules can still be added and inserted.
The modules add significant complexity to your sanity checks.
There are so many ways to screw your system if you are root and don't think
enough before you are doing something. Un*x is about saving the user from
doing stupid things but not root.
If there are easy and obviously correct sanity checks (when you do something
which never makes sense), then add a warning or error message.
In the kernel configuration process, there aren't many such cases, which
aren't already prevented, IMHO.
I don't think, Linus will accept anything apart from cases, where it's
obvious, that this configuration won't be any good.
Regards,
-- Kurt Garloff <K.Garloff@ping.de> (Dortmund, FRG) PGP key on http://student.physik.uni-dortmund.de/homepages/garloffThe second clause "open source code of derivative works" has been the most controversial (and, potentially the most successful) aspect of CopyLeft licensing. -- Halloween Document
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/