On Sun, Feb 24, 2008 at 22:27:44 +0000, Adam Hardy wrote: > Paul Cartwright on 24/02/08 19:19, wrote: >> On Sun February 24 2008, Adam Hardy wrote: >>> Using xfce, Thunar used to pick up on the new usb storage device and put an >>> icon in its tree pane for me with the usb stick's name. Clicking on that >>> would then mount it to /media >>> >>> hal still creates /dev/sda and /dev/sda1 but I can't see it as a mounted >>> file system. >>> >>> ls -la /dev/sda1/ returns "not a directory" >> >> the mount point for the "special" file /dev/sda1 would be in /media. /dev/sda >> wait, /dev/sda1 is my root filesystem. my USB stick is /dev/sdf . >> >> mount /dev/sdf /media/sdf1 >> >> >> what is the output of the mount command on your system as it normally boots: >> >> what folders do you have under /media? >> >> if sda1 is your USB stick, what happens when you type: >> >> mount /dev/sda1 /media/sda1 ( assuming you have a folder sda1 under /media) > > under /media: > drwxr-xr-x 4 root root 4096 2008-02-21 19:17 . > drwxr-xr-x 23 root root 4096 2008-02-20 09:02 .. > lrwxrwxrwx 1 root root 6 2005-03-09 21:04 cdrom -> cdrom0 > drwxr-xr-x 2 root root 4096 2005-03-09 21:04 cdrom0 > lrwxrwxrwx 1 root root 7 2005-03-09 21:04 floppy -> floppy0 > drwxr-xr-x 2 root root 4096 2005-03-09 21:04 floppy0 > -rw-r--r-- 1 root root 0 2008-02-21 19:17 .hal-mtab > --wS--x--T 1 root root 0 2006-11-13 22:14 .hal-mtab-lock > > .hal-mtab-lock appeared red on my terminal which looked bad, and 'file > .hal-mtab-lock' said 'setuid sticky empty', so I deleted it. Didn't help > much. > > I can run the mount command, no problem, as root - but the trick before > was that hal or thunar was taking care of that automatically, along with > permissions.
First of all, a clarification: Hal does not create the device nodes (/dev/sda1, etc.), udev does. Udev seems to work as intended on your system. Hal is the hardware abstraction layer, allowing your desktop environment (and other processes) to interact with your hardware in an abstracted/unified manner. For an illustration, run "lshal | less" and you will get an exhaustive overview of the hardware known to hal with its various properties listed. I think the next thing to try is what happens if your run (as your normal user) pmount-hal /dev/sda1 (Change /dev/sda1 to the correct device node of the filesystem.) If this works without errors, run "mount" to see which mount point was chosen. Also check if you can unmount the stick (again as your normal user) with pumount /dev/sda1 If all of the above works then the problem most probably lies with thunar. If it does not work then we will hopefully get some meaningful error messages. (Also check the syslog and/or dmesg in that case.) -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
