On Thursday 04 February 2010 09:04:08 Camaleón wrote: > On Thu, 04 Feb 2010 08:50:58 -0600, Boyd Stephen Smith Jr. wrote: > > In <[🔎] pan.2010.02.04.14.28.16@gmail.com>, Camaleón wrote: > >>But I still find the point valid: if a mount point defined in "fstab" is > >>not present at boot time, it should warn the user and log the error but > >>the boot process should not be stopped at all because the mount point is > >>not critical (i.e., is not root "/") for the system to properly start. > > > > There are filesystems other than '/' that I need to have a fully > > functional system: > > Yes, but the mount point of the OP is not critical for his system, that > was what I wanted to say. And the kernel must be aware of that device is > trivial and can be skipped without any drawbacks. Why must the kernel be aware of that? That's a human decision, not a technical one. I can certainly see reasons that a device attached via USB might be considered to the user to be critical. In any case, /etc/fstab is for *static* file systems. It is *not* for file systems that may or may not be there when the system is booting (or otherwise in operation). -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.