[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: auto-mounting disks that might not be present (e.g. usb drives)



In <[🔎] pan.2010.02.04.14.28.16@gmail.com>, Camaleón wrote:
>On Fri, 05 Feb 2010 00:01:17 +1030, Arthur Marsh wrote:
>> The response I received to
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568200 suggest that the
>> responder thinks that running fsck on a non-existent device is the
>> proper behaviour /-:.
>
>I've also found some "opposition" from developers while reporting bugs ;-)
>
>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:

$ df -Ph
Filesystem            Size  Used Avail Use% Mounted on
/dev/md0              981M  466M  515M  48% /
tmpfs                 2.0G  8.0K  2.0G   1% /lib/init/rw
udev                   10M  272K  9.8M   3% /dev
tmpfs                 2.0G   12K  2.0G   1% /dev/shm
/tmp                  2.0G   32M  2.0G   2% /tmp
/dev/mapper/monster-home  1.2T  1.1T  109G  92% /home
/dev/mapper/monster-media  4.3T  4.2T  120G  98% /home/bss/media
/dev/mapper/monster-opt  1.0G   33M  992M   4% /opt
/dev/mapper/monster-srv  1.0G   37M  988M   4% /srv
/dev/mapper/monster-usr  8.0G  5.7G  2.4G  72% /usr
/dev/mapper/monster-usr.local  1.0G   36M  989M   4% /usr/local
/dev/mapper/monster-var  4.0G  1.3G  2.8G  31% /var
/dev/mapper/monster-var.cache  8.0G  4.1G  4.0G  51% /var/cache
/dev/mapper/monster-var.tmp  4.0G  398M  3.7G  10% /var/tmp

-- 
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.


Reply to: