If it defaults to off, it shouldn't be a problem.
> okay, first the good reason :)
> currently it is not possible to compile a kernel with
> root NFS support, which in case of NFS failure, (or
> missing NFS/network options) boots from HD, instead
> it asks you to insert a Floppy ...
For 2.5, it might be more useful if the default NFS-on-root
configuration is to wait for 60 seconds, and retry, if there is an
error. If a machine is re-booted remotely, and it can't contact the
server for any reason, it's not really very desirable to have it wait
for you to insert a floppy :-)
> and now ad 'user visible change' ...
> what if I make it CONFIG_NOFLOPPY_FALLBACK and
> change the #ifdef to #ifndef ? This would give
> the same (strange?) behaviour as now, but an option
> to disable the fallback (to floppy) ...
I'm not really sure how useful the root filesystem on floppy option
is. I'd imagine that it is probably a relic from the times when a lot
of people booted the kernel image directly, instead of using a
bootloader. It would be quite useful in those circumstances, as you
wouldn't have a bootloader prompt to override the default for the root
Since 2.6 will no longer have the in-kernel bootloader, I suggest we
remove this functionality as well, and replace it with the wait 60
seconds and retry functionalily I described above.
It would be worth putting this in to 2.4, though.
Oh, and it would be even better if it tried the second floppy drive in
the case that the first one didn't contain a disk, (in case somebody
wants to mount a 5.25" floppy as the root filesystem, and their 5.25"
drive is the secondary one).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/