Timeline for Problem with permissions - propably after using "sudo chown -R me ./"
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2023 at 21:08 | answer | added | tink | timeline score: 1 | |
| Jun 9, 2023 at 11:52 | comment | added | Olivier Dulac | (almost) always singlequote or doublequote arguments: chown -R yourname '/path/to/thedirectory' # would be much safer, even if you by mistake add a space somewhere in the path. | |
| Jun 9, 2023 at 9:09 | comment | added | Chris Davies | What does the screenshot show? If it doesn't already, please remember to include the command as text that generated whatever permissions it shows - don't post pictures of text. | |
| Jun 9, 2023 at 9:06 | comment | added | Giacomo Catenazzi | Now you can learn the backup skills. And next time do not do that. Add yourself to the group of other files (e.g. httpd/www-data), but keep for safety and security most administrative users/groups for themselves. As you see: we make error, so we do not want to wrongly edit/override files without huge warnigns -- see also: unix.stackexchange.com/questions/79125/… | |
| Jun 9, 2023 at 9:05 | comment | added | muru | You might have accidentally included a space and ran sudo chown -R me . /. Reinstalling is the simplest option. | |
| Jun 9, 2023 at 8:58 | history | edited | Robert Juszczyński | CC BY-SA 4.0 | edited body |
| S Jun 9, 2023 at 8:53 | review | First questions | |||
| Jun 9, 2023 at 19:34 | |||||
| S Jun 9, 2023 at 8:53 | history | asked | Robert Juszczyński | CC BY-SA 4.0 |