37
as a GUI pleb i just doubleclick the file, which opens kate.
i edit the file and click save, get asked for my password
and all is fine.
that's way too simple, the linux gods demand more esoteric suffering
How dare you use computers to do stuff the way they were invented for?
Had an idiot "fix" a permission problem by running "sudo chmod -R 777 /"
And that is why sudo privileges were removed for the vast majority of people.
Oh... That sounds like a nightmare. How do you even fix that? There's no "revert the entire filesystem's permissions to default" button that I'm aware of
You restore the system from backup
If you are lucky your system is atomic or has other roll back feature. Otherwise it's reinstall time.
I guess you could set up a fresh system, run a script that goes through each folder checking the permission and setting it on the target system.
Shared this before, but someone I know did a chmod on /bin which nuked all the SUID/GUID bits which borked the system lol.
Surpsingly easy enough to undo by getting a list of the correct perms from a working system, but hilarious nonetheless
seems reasonable to me, root is just a made up concept and the human owns the machine.
A fellow nano user! There are dozens of us!
Hell yeah gotta embrace the pain of using archaic key bindings that you'll forget until the next time you need to edit a file in the terminal, you must suffer like man. Modem and sane terminal editors are for pussies! If it doesn't load in 0.01 ms it's bloated.. Whatever you do don't install anything like micro, just keep suffering!
One of us! One of us!
Yeah, there is only one of you.
Its lighter weight than vim
ed
pico gang rise up!
G T F O !
-nano4lifegang
Yikes it was just a joke guys
sudo chmod -R 777 /
It's safe because it's sudo! Like sudo rm -rf /*
At one of my prior positions they outsourced all the junior engineers to this firm that only had windows desktop support experience.
Actual escalation I got:
contractor: I am trying to remove this file that is filling the drive but it won't let me
me: show me what you are doing.
contractor (screenshot): # rm -f /dev/hdc
another one did rm -rf /var to clear a stuck log file, which at least did solve the problem he was having.
After that I sent out an email stating that I would not help anyone who used he rm command unless they consulted with a senior first. I was later reprimanded for saying I wouldn't help people.
I was later reprimanded for saying I wouldn't help people.
I've heard that before. "No. I won't close the circuit breaker while you're holding the wires." "Boss!..."
Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran "rm -rf /" instead of "./".
After I realized that it was taking too long, i realized my error.
Now for the fun part. In those days nfs passed root privileges to the remote file system. I took out 2.5 machines before I killed it.
Anyone remember that nvidia fix where a space slipped in like: rm -rf / nvidia ?
Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran "rm -rf /" instead of "./".
I still do. With NFS4 even more than ever. Won't let it go unless for a SAN.
Now for the fun part. In those days nfs passed root privileges to the remote file system.
no_root_squash
much?
Like I said, olden days.
Holy smokes. That must have been before 1989 (that's when RFC1094 was released, explicitely prohibiting to map the root user to UID 0). I thought, I was old...
You won’t be able to do certain things. Either .ssh or ~ expects certain exact permissions and pukes if it’s different, IIRC
Yep. I fucked up once when I meant to type chmod for something but with "./" but I missed the ".". It was not good.
Getting flashbacks of me trying to explain to a mac user why using sudo "to make it work" is why he had a growing problem of needing to use sudo... (more and more files owned by root in his home folder).
:w !sudo tee %
sudo = shut up dammit, obey!
obligatory... (well, you know the rest)
personally, I prefer the good ol double bang (!!), but whatever floats yer boat, and all that.
You mean sudoedit right? Right?
edit:
While there's a little bit of attention on this I also want to beg you to stop doing sudo su - and start doing sudo -i you know who you are <3
Why memorize a different command? I assume sudoedit just looks up the system's EDITOR environment variable and uses that. Is there any other benefit?
Why memorize a different command? I assume sudoedit just looks up the system’s EDITOR environment variable and uses that. Is there any other benefit?
I don't use it, but, sudoedit is a little more complicated than that.
details
from man sudo:
When invoked as sudoedit, the -e option (described below), is implied.
-e, --edit
Edit one or more files instead of running a command. In lieu
of a path name, the string "sudoedit" is used when consulting
the security policy. If the user is authorized by the policy,
the following steps are taken:
1. Temporary copies are made of the files to be edited with
the owner set to the invoking user.
2. The editor specified by the policy is run to edit the tem‐
porary files. The sudoers policy uses the SUDO_EDITOR,
VISUAL and EDITOR environment variables (in that order).
If none of SUDO_EDITOR, VISUAL or EDITOR are set, the
first program listed in the editor sudoers(5) option is
used.
3. If they have been modified, the temporary files are copied
back to their original location and the temporary versions
are removed.
To help prevent the editing of unauthorized files, the follow‐
ing restrictions are enforced unless explicitly allowed by the
security policy:
• Symbolic links may not be edited (version 1.8.15 and
higher).
• Symbolic links along the path to be edited are not followed
when the parent directory is writable by the invoking user
unless that user is root (version 1.8.16 and higher).
• Files located in a directory that is writable by the invok‐
ing user may not be edited unless that user is root (ver‐
sion 1.8.16 and higher).
Users are never allowed to edit device special files.
If the specified file does not exist, it will be created. Un‐
like most commands run by sudo, the editor is run with the in‐
voking user's environment unmodified. If the temporary file
becomes empty after editing, the user will be prompted before
it is installed. If, for some reason, sudo is unable to update
a file with its edited version, the user will receive a warning
and the edited copy will remain in a temporary file.
tldr: it makes a copy of the file-to-be-edited in a temp directory, owned by you, and then runs your $EDITOR as your normal user (so, with your normal editor config)
note that sudo also includes a similar command which is specifically for editing /etc/sudoers, called visudo 🤪
If your file is not in your home directory, you shouldn't do chmod or chown in any other file
What if I make my home /
sudo dolphin
Then I act like a Windows user and go there via the GUI because I didn't feel like learning how to use nano.
If you're running dolphin as sudo and open like a text file in an editor, does it edit the file with sudo?
When you run a process under sudo, it will be running as the root user. Processes that that process launches will also be running as the root user; new processes run as the same user as their parent process.
So internally, no, it won't result in another invocation of sudo. But those processes a dolphin process running as root starts will be running as the root user, same as if you had individually invoked them via sudo.
But in my experience Dolphin refuses to run via sudo anyway.
You meant sudo vim, ok?
(disclaimer: joke. Let the unholy war start)
why tho?
If it's a file I have to modify once why would I run:
sudo chmod 774 file.conf
sudo chown myuser:myuser file.conf
vi file.conf
sudo chown root:root file.conf
sudo chmod 644 file.conf
instead of:
sudo vi file.conf
Inane. Intentionally convoluted, or someone following the absolute worst tutorials without bothering to understand anything about what they're reading.
I have questions:
- Why are your configurations world readable?
- Why are you setting the executable bit on a .conf file?
- Why change the files group alongside the owner when you've just given the owner rxw and you're going to set it back?
- If it was 644 before, why 774?
- Why even change the mode if you're going to change the ownership?
- Why do you want roots vimrc instead of your users
- Why do you hate sudoedit
- Why go out of your way to make this appear more convoluted than it actually is?
Even jokey comments can lead to people copying bad habits if it's not clear they're jokes.
This was a joke right? I was baited by your trolling?
I felt kinda bad doing that at first. then your absolute rage made my doubt's melt away.
doubt’s
I see what you did there
this post was submitted on 25 Apr 2025
37 points (100.0% liked)
linuxmemes
24868 readers
784 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS