I haven't tested that mount command yet, but figured I'd let you know the result of my 'typo testing'
my network drives are currently mounted.
to achieve this, I 'typoed' out each of the appropriate lines from fstab (I used 3's just to be sure) and rebooted. The long delay loading HAL didn't happen, neither did the dialogue telling me that "the process for the system protocol died unexpectedly" error I have been getting upon forst starting KDE. I opened up a terminal and checked that the drives hadn't mounted (which they hadn't), edited fstab to remove the '3's and ran a sudo mount -v -a...
akshoslaa@akhshamineth:~$ sudo mount -v -a
mount: proc already mounted on /proc
mount: /dev/hda1 already mounted on /media/xp
mount: /dev/hda4 already mounted on /media/dapper_old
mount: /dev/hdb1 already mounted on /media/windows_data
mount: /dev/sda1 already mounted on /media/Documents
mount: /dev/sdb1 already mounted on /media/Media
mount: /media/Documents/Desktop already mounted on /home/akshoslaa/Desktop
mount: /media/Documents/Documents already mounted on /home/akshoslaa/Documents
mount: /media/Documents/Games already mounted on /home/akshoslaa/Games
mount: /media/Documents/dev already mounted on /home/akshoslaa/dev
mount: /media/Documents/bin already mounted on /home/akshoslaa/bin
mount: /media/Media already mounted on /home/akshoslaa/Media_Local
/home/akshoslaa/mistress: invalid option -- v
Password:
/home/akshoslaa/Media/Movies: invalid option -- v
Password:
/home/akshoslaa/Media/Series: invalid option -- v
Password:
/home/akshoslaa/wwwroot: invalid option -- v
Password:
nothing was mounted
akshoslaa@akhshamineth:~$ mount
/dev/hda2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
varrun on /var/run type tmpfs (rw)
varlock on /var/lock type tmpfs (rw)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
devshm on /dev/shm type tmpfs (rw)
lrm on /lib/modules/2.6.15-22-386/volatile type tmpfs (rw)
/dev/hda1 on /media/xp type ntfs (rw,nls=utf8,umask=007,gid=46)
/dev/hda4 on /media/dapper_old type ext3 (rw)
/dev/hdb1 on /media/windows_data type vfat (rw,utf8,umask=007,gid=46)
/dev/sda1 on /media/Documents type ext3 (rw)
/dev/sdb1 on /media/Media type ext3 (rw)
/media/Documents/Desktop on /home/akshoslaa/Desktop type none (rw,bind)
/media/Documents/Documents on /home/akshoslaa/Documents type none (rw,bind)
/media/Documents/Games on /home/akshoslaa/Games type none (rw,bind)
/media/Documents/dev on /home/akshoslaa/dev type none (rw,bind)
/media/Documents/bin on /home/akshoslaa/bin type none (rw,bind)
/media/Media on /home/akshoslaa/Media_Local type none (rw,bind)
//192.168.3.1/data on /home/akshoslaa/mistress type smbfs (rw)
//192.168.3.1/Movies on /home/akshoslaa/Media/Movies type smbfs (rw)
//192.168.3.1/Series on /home/akshoslaa/Media/Series type smbfs (rw)
//192.168.3.1/wwwroot on /home/akshoslaa/wwwroot type smbfs (rw)
akshoslaa@akhshamineth:~$ ls Media/Series/
Copy of Cereni - Holophonic.mp3 Series/ Thumbs.db
Recycled/ !Sort/
it's odd, it says nothing was mounted, but the drives are coming up just fine. -v is making it ask for the password to the samba shares (it doesn't ask if I just use -a, I just checked)
I'm guessing that the typos are preventing it from trying to mount during boot (so commenting the lines out should have the same effect) thereby avoiding whatevers going wrong during boot. Once everythings up and running I can mount them fine, but only if I didn't try during boot.
I was getting the same sort of delay as with hald/mount -a when I tried to ls the mount points. (before commenting them out of fstab)
yep, they're there (it was all working fine (and has been for quite some time) untill the hald update the other day)
akshoslaa@ akhshamineth: ~$ ls -ld mistress Media/Movies Media/Series wwwroot
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 Media/Movies
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 Media/Series
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 mistress
drwxr-xr-x 1 root root 4096 2006-05-12 11:01 wwwroot
I haven't tested that mount command yet, but figured I'd let you know the result of my 'typo testing'
my network drives are currently mounted.
to achieve this, I 'typoed' out each of the appropriate lines from fstab (I used 3's just to be sure) and rebooted. The long delay loading HAL didn't happen, neither did the dialogue telling me that "the process for the system protocol died unexpectedly" error I have been getting upon forst starting KDE. I opened up a terminal and checked that the drives hadn't mounted (which they hadn't), edited fstab to remove the '3's and ran a sudo mount -v -a...
akshoslaa@ akhshamineth: ~$ sudo mount -v -a Documents/ Desktop already mounted on /home/akshoslaa /Desktop Documents/ Documents already mounted on /home/akshoslaa /Documents Documents/ Games already mounted on /home/akshoslaa /Games Documents/ dev already mounted on /home/akshoslaa/dev Documents/ bin already mounted on /home/akshoslaa/bin /Media_ Local /mistress: invalid option -- v /Media/ Movies: invalid option -- v /Media/ Series: invalid option -- v /wwwroot: invalid option -- v akhshamineth: ~$ mount remount- ro) 2.6.15- 22-386/ volatile type tmpfs (rw) utf8,umask= 007,gid= 46) umask=007, gid=46) Documents/ Desktop on /home/akshoslaa /Desktop type none (rw,bind) Documents/ Documents on /home/akshoslaa /Documents type none (rw,bind) Documents/ Games on /home/akshoslaa /Games type none (rw,bind) Documents/ dev on /home/akshoslaa/dev type none (rw,bind) Documents/ bin on /home/akshoslaa/bin type none (rw,bind) /Media_ Local type none (rw,bind) /mistress type smbfs (rw) 3.1/Movies on /home/akshoslaa /Media/ Movies type smbfs (rw) 3.1/Series on /home/akshoslaa /Media/ Series type smbfs (rw) 3.1/wwwroot on /home/akshoslaa /wwwroot type smbfs (rw) akhshamineth: ~$ ls Media/Series/
mount: proc already mounted on /proc
mount: /dev/hda1 already mounted on /media/xp
mount: /dev/hda4 already mounted on /media/dapper_old
mount: /dev/hdb1 already mounted on /media/windows_data
mount: /dev/sda1 already mounted on /media/Documents
mount: /dev/sdb1 already mounted on /media/Media
mount: /media/
mount: /media/
mount: /media/
mount: /media/
mount: /media/
mount: /media/Media already mounted on /home/akshoslaa
/home/akshoslaa
Password:
/home/akshoslaa
Password:
/home/akshoslaa
Password:
/home/akshoslaa
Password:
nothing was mounted
akshoslaa@
/dev/hda2 on / type ext3 (rw,errors=
proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
varrun on /var/run type tmpfs (rw)
varlock on /var/lock type tmpfs (rw)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
devshm on /dev/shm type tmpfs (rw)
lrm on /lib/modules/
/dev/hda1 on /media/xp type ntfs (rw,nls=
/dev/hda4 on /media/dapper_old type ext3 (rw)
/dev/hdb1 on /media/windows_data type vfat (rw,utf8,
/dev/sda1 on /media/Documents type ext3 (rw)
/dev/sdb1 on /media/Media type ext3 (rw)
/media/
/media/
/media/
/media/
/media/
/media/Media on /home/akshoslaa
//192.168.3.1/data on /home/akshoslaa
//192.168.
//192.168.
//192.168.
akshoslaa@
Copy of Cereni - Holophonic.mp3 Series/ Thumbs.db
Recycled/ !Sort/
it's odd, it says nothing was mounted, but the drives are coming up just fine. -v is making it ask for the password to the samba shares (it doesn't ask if I just use -a, I just checked)
I'm guessing that the typos are preventing it from trying to mount during boot (so commenting the lines out should have the same effect) thereby avoiding whatevers going wrong during boot. Once everythings up and running I can mount them fine, but only if I didn't try during boot.
I was getting the same sort of delay as with hald/mount -a when I tried to ls the mount points. (before commenting them out of fstab)