Bill Wisse wrote:

I have an external USB drive which I access through Kwikdisk, mount, and then "open in filemanager".No problem here. When I want to write to it , I need to be root. It wasn't a problem in 9.1, I just opened the program as root , mount and open in Filemanager. However since I upgraded to 9.2 , I can still do the same as *user* but when I open the program as root , mount, the "open in Filemanager" doesn't work anymore. I click on that option and nothing happens, what means I cannot write to that disk anymore.

Anybody an idea to fix this?

Thanks.

I did 2 things, I haven't checked which one or if both are needed to do the trick, also I haven't got the drive in /etc/fstab, perhaps with suitable options there, it may be all that is necessary. chown root.users <mountpoint> chmod a+rw <mountpoint> Now I have full read/write access to the drive. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====

On Tue, 14 Dec 2004 07:34:32 -1100, Bill Wisse wrote:

On Tuesday 14 December 2004 05:02, Sunny wrote:

...

On Mon, 13 Dec 2004 21:17:44 -1100, Bill Wisse wrote:

...

I have an external USB drive which I access through Kwikdisk, mount, and then "open in filemanager".No problem here. When I want to write to it , I need to be root. It wasn't a problem in 9.1, I just opened the program as root , mount and open in Filemanager. However since I upgraded to 9.2 , I can still do the same as *user* but when I open the program as root , mount, the "open in Filemanager" doesn't work anymore. I click on that option and nothing happens, what means I cannot write to that disk anymore.

Anybody an idea to fix this?

I never used external disk and kwickdisk, but most probably there is a line in /etc/fstab for that drive. Can you post that line?

Thanks /dev/sda1 /data1 auto noauto,user 0 0

try thsi: /dev/sda1 /data1 auto user,exec,dev,suid,rw,gid=600,umask=000,quiet 0 0 With 9.0 I used this settings with my digital camera (recognized as mass storage, i.e. as usb disk). I had never problems to read/write to it. And.. change gid=xxx to your user gid. Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85

Bill Wisse wrote:

On Tuesday 14 December 2004 06:04, Sid Boyce wrote:

...

I did 2 things, I haven't checked which one or if both are needed to do the trick, also I haven't got the drive in /etc/fstab, perhaps with suitable options there, it may be all that is necessary.

chown root.users <mountpoint> chmod a+rw <mountpoint>

Now I have full read/write access to the drive. Regards

I tried this , also what sunny suggested, but... still the same " open in Filemanager" works as user but not as Root. Is there a CLI command to open this disk so I can see it's contents?

Thanks for your help.

I've tried it as root, both with KDE and GNOME, I can open the drive and copy files to the drive using the filemanagers or from the command line. It seems to be a permissions problem, but I would have expected the two suggestions from Sunny and I would have worked. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====

Bill Wisse wrote:

On Tuesday 14 December 2004 14:13, Sid Boyce wrote:

...

I've tried it as root, both with KDE and GNOME, I can open the drive and copy files to the drive using the filemanagers or from the command line. It seems to be a permissions problem, but I would have expected the two suggestions from Sunny and I would have worked.

Well, I'll don't know anymore. :-) I opened Konqueror , Filemanger, Devices and there my drive came up twice. (In kwikdisk only once) Once as /data1 and once as /media/usb xx6578 etc. I clicked on the last one and had complete access again!

Go figure.

I disabled subfs early on as it seemed to just cause confusion, it's still not at the quality that amd was years ago and hasn't been accepted into the vanilla kernel, it still has a ways to go I think. Unless it's causing you undue grief, I'd recommend working out a routine for handling it and wait for things to improve. USB can be tricky, on later kernels it's not a scsi device, so on kernel.org kernels >=2.6.9, it's /dev/ub?. Typical behaviour here - the mains plug to the power supply for this HD enclosure isn't the best fit, so if accidentally the lead is stepped on, it powers off/on, so it went from /dev/uba to /dev/ubb and now /dev/ubc until the next reboot, it seems hotplug is saying uba has failed, here comes another one, that must be ubb etc. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====