(inspite of the fact that they're there as I showed you before)
sudo mount -t smbfs -o dmask=777,fmask=777,uid=0,gid=0,auto,rw,nouser,credentials=/etc/fstab_smb_credentials_1 //192.168.3.1/data /home/akshoslaa/mistress
gives me the familiar delay, followed by the usual "Could not resolve mount point /home/akshoslaa/mistress"
now for the fun bit :P
I left fstab uncommented, and changed the network drives to noauto and rebooted.
No delay loading hal
no errors starting kde
I can ls the mount points (unmounted) without the delay or errors
I can manually mount each of drives with no delays or errors (eg sudo mount mistress) and access their contents normally.
This gives me a convinient enough work around, I can just set a startup script to mount the drives from noauto once kde is loaded. Now we just need to work out whats going wrong so it can be fixed properly :P (I'm still guessing it's a side effect of whatever went wrong with 43962, and once that gets fixed my problem will disappear too...
alrighty, 'unfixing' fstab and rebooting gives back the long wait for hal
the long delay for ls returns, if giving the following errors:
$ ls -ld mistress Media/Movies Media/Series wwwroot
ls: mistress: Input/output error
ls: Media/Movies: Input/output error
ls: Media/Series: Input/output error
ls: wwwroot: Input/output error
(inspite of the fact that they're there as I showed you before)
sudo mount -t smbfs -o dmask=777, fmask=777, uid=0,gid= 0,auto, rw,nouser, credentials= /etc/fstab_ smb_credentials _1 //192.168.3.1/data /home/akshoslaa /mistress
gives me the familiar delay, followed by the usual "Could not resolve mount point /home/akshoslaa /mistress"
now for the fun bit :P
I left fstab uncommented, and changed the network drives to noauto and rebooted.
No delay loading hal
no errors starting kde
I can ls the mount points (unmounted) without the delay or errors
I can manually mount each of drives with no delays or errors (eg sudo mount mistress) and access their contents normally.
This gives me a convinient enough work around, I can just set a startup script to mount the drives from noauto once kde is loaded. Now we just need to work out whats going wrong so it can be fixed properly :P (I'm still guessing it's a side effect of whatever went wrong with 43962, and once that gets fixed my problem will disappear too...