I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
Don't boot with them mounted.
On Mon, 2007-05-14 at 22:37 -0400, oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
-- regards, Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
On Tuesday 15 May 2007, Michael A Peters wrote:
Don't boot with them mounted.
On Mon, 2007-05-14 at 22:37 -0400, oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
It doesn't seem to make any difference, just 2 days ago I got the message that only root can mount while working on something I needed to take back to a user account on another machine. So I become root, mounted the sonofabitch, and then chown -R user:user it back to the user that needed it mounted in the first place. Then found that user still couldn't write to the device because that user on the ubuntu box it came from was uid 1000, where he was uid 500 on this box. So an hour's walking back and forth between buildings later, I get samba working well enough to mount that whole machine as a share on this box, with root running samba, then root launched krusader could copy things both ways, while apparently translating the uid's. But I never was able to smbclient -L and see the [home] share I setup in the smb.conf out there. That's all I really wanted, but somebody decided that wasn't supposed to work.
Ditto for umount, even though the user owns everything on that usb keychain gizmo, "only root can umount" That is BS to me, and we spread it on cornfields to grow 120 bushels to the acre where I come from.
To TPTB: If you want us to use our machines as normal users, then let normal users USE the everyday tools we need to get our projects done. YOUR idea of security seems to be to harrass the hapless user trying to do a job, and make him spend an hour or more doing what should have been a 5 second file move, 5 seconds assuming he was a slow typer.
Until such time, then be aware that I run everything as root here unless a specific projet requires otherwise. And selinux is turned off for exactly the same reason. This is after all, my machine, and if I want to have it do something its capable of, then get the hell out of the way and let me get it done.
At 09:12 15/05/2007, you wrote:
On Tuesday 15 May 2007, Michael A Peters wrote:
Don't boot with them mounted.
On Mon, 2007-05-14 at 22:37 -0400, oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
It doesn't seem to make any difference, just 2 days ago I got the message that only root can mount while working on something I needed to take back to a
Gene,
You might have seen my thread from a couple of days ago. There was an update to FC5. Following that there's a load of errors during boot. I offered to post my log file but nobody has so far expressed any interest in examining it, and now my USB flash drives don't mount. I've put my son under strict instructions NOT to update his FC5 machine, otherwise I won't be able to write a backup to flash after rsync-ing it over the network to his PC.
I'm at work right now. The action I just took with my office desktop was to run QTParted to remove the FC5 partitions from this machine, then run the Dapper Drake installer. I've just selected the old XP install from the new grub setup to make sure it still works as before (it does) and in a minute I'm going to try out the new Kubuntu install, see if I can get things set up like before with my FC5 ~/* backup.
Dave
on 05/15/2007 12:35 AM Michael A Peters wrote:
Don't boot with them mounted.
I did not. The machine has not been rebooted for a week already. I tried to unplug and plug the flash drives couple times. I prefer to mound the stuff manually, therefore "Mount removable drives when hot-plugged" options in gnome-volume-properties is unchecked on my system. So I open nautilus as regular user, and mount the drive there, but it comes out mounted under root.
On Mon, 2007-05-14 at 22:37 -0400, oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
-- regards, Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
Thanks to everyone who bothered to reply. I managed to solve the problem and the credit for help goes to Chun-Chung Chen (who appears to be reading the list but not signed up for it, so he mailed to me separately). The problem seems to be with the gnome-mount package, particularly with broken gconf parameters for the one. It is not clear whether the configuration was broken when installing the gnome-mount package itself or by some other package. In order to fix the glitch with permission on mounted external storage I had to add "mount_options" key to the /system/storage/default_options/vfat/ path. The key has to be of type List with the items of type String. The problem is resolved by adding just one value to the list, namely "uid=". This role of key is described on gnome-mount man page, although this page seems to be rather outdated.
Later it was found that simple reinstallation of the gnome-mount package solves the problem and similar keys are added for many other file systems.
On Mon, 2007-05-14 at 22:37 -0400, oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
-- regards, Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
damned, it is driving me crazy. /var/log/messages says "mounted /dev/sda1 on behalf of uid 501" This is my uid!!! I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference. Where are these freaking hal rules located? I want to fix this manually.
on 05/14/2007 10:37 PM oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
Same goes for my Sony Ericsson W850i with built in Memory stick. What gives?
On 18/05/07, oleksandr korneta atenrok@gmail.com wrote:
damned, it is driving me crazy. /var/log/messages says "mounted /dev/sda1 on behalf of uid 501" This is my uid!!! I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference. Where are these freaking hal rules located? I want to fix this manually.
on 05/14/2007 10:37 PM oleksandr korneta wrote:
I'm not sure when this began, but I just discovered that all my usb storage devices are mounted in a way that root appears to be the owner of all the files. Now I can't write anything to my flash drive, unless I open the root console. I'm sure It wasn't like this before, and I suspect it happened after one of the updates. Is there a way to fix this manually?
this is FC6 here.
-- regards, Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On Thu, 2007-05-17 at 21:28 -0400, oleksandr korneta wrote:
damned, it is driving me crazy. /var/log/messages says "mounted /dev/sda1 on behalf of uid 501" This is my uid!!! I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference.
On FC6? I don't see that problem. I'm seeing things mounted with my user ID but root as the group ID. I can still do what I want with the device (mount, unmount, play with the files, etc.).
Tim,
on 05/17/2007 11:59 PM Tim wrote:
On Thu, 2007-05-17 at 21:28 -0400, oleksandr korneta wrote:
damned, it is driving me crazy. /var/log/messages says "mounted /dev/sda1 on behalf of uid 501" This is my uid!!! I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference.
On FC6? I don't see that problem. I'm seeing things mounted with my user ID but root as the group ID. I can still do what I want with the device (mount, unmount, play with the files, etc.).
I'm really happy fro you that you don't have this problem. I did not see it either since fresh install of FC6, until couple weeks ago (cant tell exact time). Now _all_ my removable storage (DAPs, pen-drives, all the media cards through cardreader) is mounted read-only on this system. Now, who tells me what packages have something to do with this situation, I will trace their update and try to roll back to previous version?
PS: I hate the person who came up with *brilliant* idea to move all the removable stuff mounting configurations from fstab, everything was so clear and easy there...
oleksandr korneta:
I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference.
Mine's: ls -Zd /media/ drwxr-xr-x root root system_u:object_r:mnt_t /media/
And the /media parent directory permissions wouldn't affect write permissions in sub-directories inside /media (e.g. /media/drive/file). SELinux could be biting you.
Tim:
On FC6? I don't see that problem. I'm seeing things mounted with my user ID but root as the group ID. I can still do what I want with the device (mount, unmount, play with the files, etc.).
oleksandr korneta:
I'm really happy fro you that you don't have this problem. I did not see it either since fresh install of FC6, until couple weeks ago (cant tell exact time).
Ok. Didn't know, until then that you're using FC6, too. I've been keeping up-to-date with mine, I tend to run updates every other day or so, and nothing recently has caused me problems. I hadn't noticed any problems a little further back, but I hadn't used a flash drive during that time. Are you up-to-date?
Now _all_ my removable storage (DAPs, pen-drives, all the media cards through cardreader) is mounted read-only on this system.
What file system are you using on them? FAT doesn't have separate user permissions, so will get what the mount applies to it. Other systems do have user ownership, and can/will use the ones on the drive's file system.
Now, who tells me what packages have something to do with this situation, I will trace their update and try to roll back to previous version?
You should probably look through your /var/log/yum.log (if you used yum to update). I haven't looked into what packages, but HAL, UDEV and gnome-mount are some of the things that could be involved.
PS: I hate the person who came up with *brilliant* idea to move all the removable stuff mounting configurations from fstab, everything was so clear and easy there...
As far as I'm concerned, removable media ought to work all by itself, without you having to do anything with fstab. It's the damn computer, it should figure out what to do.
Removable media can be a right pain with fstab, but you can still use it. Though be prepared for headaches when it comes to things not being connected at boot, USB drives that get plugged into different USB sockets or connected in different orders (/dev/sda one day, /dev/sdb the next time you plug it in after plugging in another device, first).
on 05/18/2007 12:08 PM Tim wrote:
oleksandr korneta:
I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference.
Mine's: ls -Zd /media/ drwxr-xr-x root root system_u:object_r:mnt_t /media/
mine is: $ ls -Zd /media/ drwxrwxrwx root root system_u:object_r:mnt_t:s0 /media/
And the /media parent directory permissions wouldn't affect write permissions in sub-directories inside /media (e.g. /media/drive/file). SELinux could be biting you.
My SELinux was disabled at install and it stays that way (just checked).
Tim:
On FC6? I don't see that problem. I'm seeing things mounted with my user ID but root as the group ID. I can still do what I want with the device (mount, unmount, play with the files, etc.).
oleksandr korneta:
I'm really happy fro you that you don't have this problem. I did not see it either since fresh install of FC6, until couple weeks ago (cant tell exact time).
Ok. Didn't know, until then that you're using FC6, too. I've been keeping up-to-date with mine, I tend to run updates every other day or so, and nothing recently has caused me problems. I hadn't noticed any problems a little further back, but I hadn't used a flash drive during that time. Are you up-to-date?
yes. I use smart and update the system at least once a week from official repositories.
Now _all_ my removable storage (DAPs, pen-drives, all the media cards through cardreader) is mounted read-only on this system.
What file system are you using on them? FAT doesn't have separate user permissions, so will get what the mount applies to it. Other systems do have user ownership, and can/will use the ones on the drive's file system.
All these media have FAT16/32 filesystem. I know that FAT does not have filesystem-lever permission policies, and that is why I blame my system.
Now, who tells me what packages have something to do with this situation, I will trace their update and try to roll back to previous version?
You should probably look through your /var/log/yum.log (if you used yum to update). I haven't looked into what packages, but HAL, UDEV and gnome-mount are some of the things that could be involved.
No. I use smart, but this:
$ rpm -qa hal udev gnome-mount --last udev-095-17.fc6 Thu 18 Jan 2007 08:51:38 AM EST hal-0.5.8.1-6.fc6 Fri 05 Jan 2007 07:42:08 PM EST gnome-mount-0.5-2.fc6 Fri 03 Nov 2006 06:38:08 PM EST
tells me that the last time any these were updated was a while ago. This problem showed up much later.
PS: I hate the person who came up with *brilliant* idea to move all the removable stuff mounting configurations from fstab, everything was so clear and easy there...
As far as I'm concerned, removable media ought to work all by itself, without you having to do anything with fstab. It's the damn computer, it should figure out what to do.
Tim, one thing I know for sure that in FC4 all the configuration was managed through fstab and when I used to plug the pen drive the mount point was created in /media and correspondent string was added to fstab (thanks to whatever package was in charge of it). Thus, I was able to either mount it manually or through the file-browser. And everything was clear and transparent. And now this topic is 4 days old and no one even can tell me where is the hal policy stored, so I can identify the problem and fix it manually.
Removable media can be a right pain with fstab, but you can still use it. Though be prepared for headaches when it comes to things not being connected at boot, USB drives that get plugged into different USB sockets or connected in different orders (/dev/sda one day, /dev/sdb the next time you plug it in after plugging in another device, first).
I am familiar with this, and I know that pain, but at least whenever something was wrong I knew it is my fault and I have enough expertise to fix it. Now I know nothing.
On Fri, 18 May 2007 21:42:16 -0400 oleksandr korneta atenrok@gmail.com wrote:
<snip>
on 05/18/2007 12:08 PM Tim wrote:
oleksandr korneta:
PS: I hate the person who came up with *brilliant* idea to move all the removable stuff mounting configurations from fstab, everything was so clear and easy there...
As far as I'm concerned, removable media ought to work all by itself, without you having to do anything with fstab. It's the damn computer, it should figure out what to do.
Tim, one thing I know for sure that in FC4 all the configuration was managed through fstab and when I used to plug the pen drive the mount point was created in /media and correspondent string was added to fstab (thanks to whatever package was in charge of it). Thus, I was able to either mount it manually or through the file-browser. And everything was clear and transparent. And now this topic is 4 days old and no one even can tell me where is the hal policy stored, so I can identify the problem and fix it manually.
Hear! Hear! Exactly.
Removable media can be a right pain with fstab, but you can still use it. Though be prepared for headaches when it comes to things not being connected at boot, USB drives that get plugged into different USB sockets or connected in different orders (/dev/sda one day, /dev/sdb the next time you plug it in after plugging in another device, first).
I am familiar with this, and I know that pain, but at least whenever something was wrong I knew it is my fault and I have enough expertise to fix it. Now I know nothing.
On Friday 18 May 2007 02:28, oleksandr korneta wrote:
damned, it is driving me crazy. /var/log/messages says "mounted /dev/sda1 on behalf of uid 501" This is my uid!!! I mount the drive, but the root appears to be the owner and I have no write access! I even made /media world-writable - no difference. Where are these freaking hal rules located? I want to fix this manually.
Listen, people, I don't want to give the impression that I'm some sort of a smug bastard, but this afternoon I nuked my hard drive, reinstalled XP into a bit bigger partition than before, then installed Dapper Drake.
I plugged in a USB flash drive and it "Just Worked" like FC5 used to do for me a few days ago.
Also transferred a picture file from my phone via Bluetooth, like I used to be able to do with FC5 up until a couple of months ago. Need to add normal users to the appropriate groups to get USB mass storage, CD and audio to work for them, but it's quite easy to do and I guess that's done for data security in office environments.
Dave
-
David Fletcher -
David Hunter -
Gene Heskett -
Michael A. Peters -
oleksandr korneta -
stan -
Tim