Hello all.<br><br>historical preface:-)<br>I have a friend of mine pc where, due to virus/dialers, etc I removed windows and installed fedora.<br>He only has a modem for internet connection, so I initially installed f7 test3 to have him see the flavour and let me know about it.<br>
All was ok for his needs (internet, text editing, cd ripping, digikam, etc) and so the pc remained at that stage.<br><br>Only problem he reported lately was that when inserting an usb key, with normal user profile the access was read only, while logged as root had also write access.<br>
<br>So some time ago I updated the system directly via dvd to f8 (actually f8 rc3: MAGIC ALL WENT SMOOTHLY!!! COMPLIMENTS!) and then manually installed updated packages (till mid january).<br>But this problem still remains...<br>
Any opinion about the cause to investigate: hal / old config file or else?<br>I compared the process with the same key with mine (also f8) and his pc.<br>Both report in log file the same message such as (note the last line):<br>
<br>Jan 26 17:53:09 tekkaman kernel: usb 2-2: new high speed USB device using ehci_hcd and address 3<br>Jan 26 17:53:09 tekkaman kernel: usb 2-2: configuration #1 chosen from 1 choice<br>Jan 26 17:53:09 tekkaman kernel: Initializing USB Mass Storage driver...<br>
Jan 26 17:53:09 tekkaman kernel: scsi8 : SCSI emulation for USB Mass Storage devices<br>Jan 26 17:53:09 tekkaman kernel: usbcore: registered new interface driver usb-storage<br>Jan 26 17:53:09 tekkaman kernel: USB Mass Storage support registered.<br>
Jan 26 17:53:14 tekkaman kernel: scsi 8:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] 3987456 512-byte hardware sectors (2042 MB)<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] Write Protect is off<br>
Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] 3987456 512-byte hardware sectors (2042 MB)<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] Write Protect is off<br>
Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through<br>Jan 26 17:53:14 tekkaman kernel: sdb: sdb1<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: [sdb] Attached SCSI removable disk<br>Jan 26 17:53:14 tekkaman kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0<br>
Jan 26 17:53:15 tekkaman gnome-keyring-daemon[2458]: adding removable location: volume_uuid_E0FD_1813 at /media/KINGSTON<br>Jan 26 17:53:15 tekkaman gnome-keyring-daemon[7222]: adding removable location: volume_uuid_E0FD_1813 at /media/KINGSTON<br>
Jan 26 17:53:15 tekkaman hald: mounted /dev/sdb1 on behalf of uid 500<br><br><br>but actually on his pc the directory /media/KINGSTON is writable only by root<br>Doing an iterated "ls -l" on my pc I see this sequence while inserting the usb key:<br>
<br>[root@tekkaman valeria]# ll /media<br>total 4<br>drwxr-xr-x 2 root root 4096 2007-12-30 01:23 IPOD<br><br>[root@tekkaman valeria]# ll /media<br>total 8<br>drwxr-xr-x 2 root root 4096 2007-12-30 01:23 IPOD<br>drwx------ 2 root root 4096 2008-02-13 23:47 KINGSTON<br>
<br>[root@tekkaman valeria]# ll /media<br>total 36<br>drwxr-xr-x 2 root root 4096 2007-12-30 01:23 IPOD<br>drwxr-xr-x 4 gcecchi root 16384 1970-01-01 01:00 KINGSTON<br><br>So it seems a two (or more) step process....<br>
On his pc the dir remains actually<br>drwxr-xr-x 4 root root 16384 1970-01-01 01:00 KINGSTON<br><br>even if connected as a normal user to gnome session.<br>Thanks for your opinions and suggestions.<br>Gianluca<br><br>