Timeline for Extracted files to /usr, system seems broken now
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2015 at 12:55 | comment | added | Mark Plotnick |
You can do ls -ld /mnt /mnt/usr /mnt/usr/bin
|
|
| Feb 10, 2015 at 12:44 | comment | added | HalosGhost |
This is a great lesson to learn: probably don't ever manually extract anything to /usr and expect things to go okay (except /usr/local). *nix has package management; use it. Also, -1 for a screenshot of terminal output.
|
|
| Feb 9, 2015 at 21:22 | vote | accept | ric | ||
| Feb 9, 2015 at 20:26 | comment | added | ric |
It could be that the permissions of / have changed. Is there any way I can change them when the concerning disk is mounted as /mnt?
|
|
| Feb 9, 2015 at 19:49 | comment | added | Mark Plotnick |
permission denied often means some directory has permissions that are too restrictive. As root, what does ls -ld / /usr /usr/bin /bin show?
|
|
| Feb 9, 2015 at 19:47 | answer | added | Faheem Mitha | timeline score: 0 | |
| Feb 9, 2015 at 19:45 | comment | added | Faheem Mitha |
I think /usr/local/bin is wrong, at least. I have drwxrwsr-x 2 root staff 4096 Aug 4 2014 bin Note the s. Also, for /usr/local, the group is staff, not root.
|
|
| Feb 9, 2015 at 19:38 | comment | added | Faheem Mitha | The permissions might have changed. Are you sure they haven't? I'm talking specifically about the directory permissions, not so much the file permissions. | |
| Feb 9, 2015 at 19:35 | comment | added | ric | The old files haven't changed as far as I can see. There have been extracted some new ones, but I've already deleted them. The second screenshot I've attached shows that the permissions are intact. Could this have something to do with the file system in general or with mounting? | |
| Feb 9, 2015 at 19:30 | comment | added | Faheem Mitha | Well, a simple way would be to look at all those files you have extracted, and then compare those to the permissions of all those files on a non-broken system. If that doesn't work, you'll have to extend things to a larger set of files. There might be better approaches. Another approach is to look at the programs that are not working and try to determine if their permissions looks reasonable. Bear in mind that if the directory permissions as screwed up, it may affect the permissions of the files in them. | |
| Feb 9, 2015 at 19:13 | comment | added | ric | @FaheemMitha I'd really prefer solving this without a reinstallation, just need a hint where to start. | |
| Feb 9, 2015 at 19:04 | history | edited | muru | CC BY-SA 3.0 |
added 18 characters in body
|
| Feb 9, 2015 at 19:04 | comment | added | Faheem Mitha | I think this falls into the category of "don't do that then". "I really don't have an idea what to do now". A reinstallation is probably your best bet. The alternative is to spend a lot of time messing with your system. You'll probably learn quite a lot about Unix-like systems and Debian in particular, but that may not be what you want to be doing... Oh, and avoid screenshots of text. Just paste in the text. | |
| Feb 9, 2015 at 18:57 | review | First posts | |||
| Feb 9, 2015 at 19:17 | |||||
| Feb 9, 2015 at 18:54 | history | asked | ric | CC BY-SA 3.0 |