Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is bizarre. Burn files and directories to CD from Windows. Copy them to Slack. Because the files show as executable, chown and chmod them as appropriate.
drwx------ 2 j users 608 Oct 3 05:16 AC-DC 1977 Let There Be Rock
Try to move them with gentoo. Permission denied, error code 13. Well, a search tells me that means '#define EACCESS' or something but now what? Try it from aterm. Permission denied. Look inside the directory and see the *files* are gone. The directory just won't go. 'chmod' and 'chown' again just to be sure. 'rm' 'rm -r' 'rm -rf' 'rmdir' 'mv'. Ditto. As root, 'rm -r $DIR' works. As user 'cp' works.
I would suspect an arcane 'sticky bit' or something but how the hell did it get set? Why does't it show? How to get rid of it? How can I 'chmod' and 'chown' and 'ls' and 'cp' a directory that I own, yet can't move or remove it?
PS - I'm trying to move them to and from the same partition, so that's not it.
I've just had a bunch of crap sitting on an XP filesystem and not really caring - mp3s I'd ripped, when ripping oggs on Linux was giving me stuff to listen to. But now that I'm trying to integrate them I'm having *all kinds* of problems.
I've rebooted Windows on the Celeron and I'm just going to retag them, rename them, tar them up this time, and re-burn them - hopefully when I untar them on the Athlon they'll be cooperative? Still curious about what the hell is going on, though. Can't figure out if I'm making a bonehead tyro mistake or if there's some obscure flaw somewhere. Don't want it to happen again, though.
600 - and those delete without problem when I try to remove the directory - just the directory stays. I also thought about there maybe being hidden files in the directory but 'ls -a/A' didn't turn anything up.
Solid dashes, but the same for the directory and for the files in it (without the -d). I use reiser - is that an ext2 special, or generally applicable?
--Oops. Didn't see your edit - lemme check...
-- I think that's it. 'ls -dl' on the directory I'm trying to delete shows it right. But on the directory containing it, it's got read and execute permission but no write. So that's how I can copy and list and so on, but not delete/move. The directories above that go back to read and write. But how'd it get that way? And I should start hunting for the fix myself now, but I'm frazzled - would chattr do it, or is there a weird switch to 'chmod'?
Hell, I'm just making a new post - 4 edits is ridiculous. It almost made sense to me but, if I don't have write access (and how do 'ls -l' from above and 'ls -dl' inside, show different perms?) and that's why I can't delete the directory - how can I delete the files? Seems like that wouldn't be permitted, either.
Chattr/lsattr work on/list extended attributes. If you/anything else doesn't use them they won't get set/listed. Files within a dir are entries in the list of that dir, subdirs are listed in their parent dir list. So to be able to delete files the dir they're in should have write set, and to delete a dir inside a dir, the parent dir needs write set.
Ah. So in dir/subdir/file there's a list 'file' is on in 'subdir' and the files are writeable, so I can delete them. But in 'dir', there's a list of subdir's that are *not* writeable, so I can't move *them*. That much makes sense now.
Thanks - I appreciate the help, both of you.
-- Wait. But I did that. ls -l above a dir list and ls -dl in the directory are the same thing. I think. I had write permission all the way through doing 'ls -l' - only 'ls -dl' showed anything different. And now when I relist them as 'ls -l' from above, they show as *not* writeable. And *now* chmod works...
Okay, I'm just going to go drool in a corner for awhile. But thanks - whatever it is, it works now.