On 04/15/2015 01:47 AM, Martin Vaeth wrote: > walt <w41...@gmail.com> wrote: >> >> it tries to read from the floppy and prints an error message to the console > > No. The kernel does not do this. It is either udev or some other > part of your init system which does this. > >> "mount" at a bash prompt, and then spams the screen >> with errors about /dev/fd0. > > And again it is not the kernel. Obviously, it is the > bashcomp shell scripts which do it in some case, here. > >> Could/should kernel patch number 38 really introduce new behavior? > > It might toggle that for some reason e.g. /dev/fd0 was not visible > or accessible before. (Or at least not in the way how udev and > bashcomp expected to access it.)
I've been wondering about this new behavior of "mount" and I'm still puzzled why "mount" or bashcomp or udev or the kernel or anybody else needs to poll the physical devices to find out which filesystems are mounted. The kernel must know at *all* times which filesystems it has already mounted, right? Wrong?
