Mansour Al Akeel <mansour.alak...@gmail.com> posted 49f731db.1080...@gmail.com, excerpted below, on Tue, 28 Apr 2009 13:42:03 -0300:
> --- /media/ > !!! copy > /var/tmp/portage/sys-apps/hal-0.5.11-r8/image/media/.keep_sys-apps_hal-0 > -> /media/.keep_sys-apps_hal-0 failed . > !!! [Errno 2] No such file or directory: > '/media/.keep_sys-apps_hal-0#new' > > >>> Failed to install sys-apps/hal-0.5.11-r8, Log file: > Trying to create a file manually under /media is failing, even as a root > I don't have permission to write to that folder! Which is really strange. > > $ ls -l / [...] > drwxr-xr-x 2 root root 0 Apr 28 04:15 media [...] Two things. First, that "/media/.keep_sys-apps_hal-0#new" looks strange, like it may be trying to create the file with the #new in the filename, instead of as a comment, the obvious intent. If that's it, it's an ebuild issue and would need a bug filed. However #2 below looks like the real culprit. Second, not being able to write under /media even as root... You aren't running SELinux or some such, right? What about quotas? Is / or /media mounted read-only or with any other "interesting" options? How long has it been since you've fscked that partition? Maybe there's some corruption of some sort. Assuming none of the above questions lead anywhere, and with any dynamic mounts (thumb drives, cds, etc) unmounted, is /media empty? Assuming so, what about rmdir-ing it, then creating it again? Is it now writable? (If there's something in it, try temporarily moving it to something like /media.bak, so you can then create the new dir.) At one point I had a script in /tmp that simply wouldn't execute. I had forgotten that I was mounting /tmp with the noexec option. =:^( Once I figured out what was happening it was an easy enough fix, but it took me awhile to figure out! Thus, I've a bit of experience with "interesting" mount options. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
