this post was submitted on 25 Apr 2025
651 points (98.1% liked)

linuxmemes

25162 readers
220 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

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 sudo in 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 figuresWe 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
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] sanderium@lemmy.zip 116 points 1 month ago* (last edited 1 month ago) (5 children)
    [–] b_tr3e@feddit.org 34 points 1 month ago (3 children)

    It's safe because it's sudo! Like sudo rm -rf /*

    [–] bitchkat@lemmy.world 12 points 1 month ago (5 children)

    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.

    load more comments (5 replies)
    load more comments (2 replies)
    [–] hddsx@lemmy.ca 12 points 1 month ago (1 children)

    You won’t be able to do certain things. Either .ssh or ~ expects certain exact permissions and pukes if it’s different, IIRC

    [–] Cethin@lemmy.zip 9 points 1 month ago

    Yep. I fucked up once when I meant to type chmod for something but with "./" but I missed the ".". It was not good.

    [–] kayzeekayzee@lemmy.blahaj.zone 9 points 1 month ago (1 children)

    utter nonsense of the deranged

    [–] bishbosh@lemm.ee 14 points 1 month ago* (last edited 1 month ago)

    It's my computer, I'll read and write what I want

    [–] hactar42@lemmy.world 66 points 1 month ago (11 children)

    A fellow nano user! There are dozens of us!

    [–] Sarcasmo220@lemmy.ml 18 points 1 month ago (2 children)
    [–] Agosagror@lemmy.dbzer0.com 10 points 1 month ago

    Yeah, there is only one of you.

    load more comments (1 replies)
    [–] courval@lemmy.world 12 points 1 month ago

    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!

    [–] possiblylinux127@lemmy.zip 9 points 1 month ago (1 children)

    Its lighter weight than vim

    load more comments (1 replies)
    load more comments (8 replies)
    [–] CarbonatedPastaSauce@lemmy.world 58 points 1 month ago (1 children)

    sudo = shut up dammit, obey!

    [–] qprimed@lemmy.ml 40 points 1 month ago (2 children)

    obligatory... (well, you know the rest)

    https://xkcd.com/149/

    personally, I prefer the good ol double bang (!!), but whatever floats yer boat, and all that.

    There are many people who appreciate a double bang.

    load more comments (1 replies)
    [–] bitchkat@lemmy.world 57 points 1 month ago (3 children)

    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.

    [–] bigbuckalex@lemmy.zip 20 points 1 month ago (4 children)

    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

    [–] rabber@lemmy.ca 24 points 1 month ago

    You restore the system from backup

    [–] justme@lemmy.dbzer0.com 10 points 1 month ago

    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.

    load more comments (2 replies)
    [–] MTK@lemmy.world 10 points 1 month ago

    seems reasonable to me, root is just a made up concept and the human owns the machine.

    load more comments (1 replies)
    [–] GreenKnight23@lemmy.world 46 points 1 month ago* (last edited 1 month ago) (1 children)

    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

    1000001464

    [–] korthrun@lemmy.sdf.org 23 points 1 month ago* (last edited 1 month ago) (2 children)

    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?

    [–] GreenKnight23@lemmy.world 23 points 1 month ago (1 children)

    I felt kinda bad doing that at first. then your absolute rage made my doubt's melt away.

    lulz

    load more comments (1 replies)
    load more comments (1 replies)
    [–] xia@lemmy.sdf.org 42 points 1 month ago (3 children)

    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).

    load more comments (3 replies)
    [–] a_wild_mimic_appears@lemmy.dbzer0.com 34 points 1 month ago (2 children)

    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.

    [–] baines@lemmy.cafe 38 points 1 month ago

    that's way too simple, the linux gods demand more esoteric suffering

    [–] courval@lemmy.world 12 points 1 month ago

    How dare you use computers to do stuff the way they were invented for?

    [–] korthrun@lemmy.sdf.org 31 points 1 month ago* (last edited 1 month ago) (1 children)

    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

    [–] Albbi@lemmy.ca 12 points 1 month ago (7 children)

    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?

    [–] cypherpunks@lemmy.ml 33 points 1 month ago (1 children)

    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.

    detailsfrom 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 πŸ€ͺ

    [–] Flyswat@lemmy.dbzer0.com 19 points 1 month ago

    visudo is a life-saver since it adds some checks to prevent you from breaking your sudo configuration and locking you out of your system.

    [–] moonlight@fedia.io 13 points 1 month ago (5 children)

    It doesn't edit the file directly, it creates a temp file that replaces the file when saving. It means that the editor is run as the user, not as root.

    load more comments (5 replies)
    load more comments (5 replies)
    [–] hddsx@lemmy.ca 28 points 1 month ago (1 children)

    Sorry, user babe is not in the sudoers file. This incident will be reported

    [–] x00z@lemmy.world 8 points 1 month ago (2 children)

    All incidents are reported directly to Stallman.

    load more comments (2 replies)
    [–] Sixtyforce@sh.itjust.works 24 points 1 month ago (5 children)

    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.

    [–] bishbosh@lemm.ee 7 points 1 month ago* (last edited 1 month ago) (1 children)

    If you're running dolphin as sudo and open like a text file in an editor, does it edit the file with sudo?

    [–] tal@lemmy.today 13 points 1 month ago* (last edited 1 month ago) (1 children)

    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.

    load more comments (1 replies)
    load more comments (4 replies)
    [–] capuccino@lemmy.world 23 points 1 month ago (2 children)

    If your file is not in your home directory, you shouldn't do chmod or chown in any other file

    load more comments (2 replies)
    [–] Shanmugha@lemmy.world 22 points 1 month ago* (last edited 1 month ago) (6 children)

    You meant sudo vim, ok?

    (disclaimer: joke. Let the unholy war start)

    [–] jaybone@lemmy.zip 11 points 1 month ago (4 children)

    Do people really war over nano vs vi?

    I get the vi vs emacs war, but are people really willing to die on a hill over nano?

    load more comments (4 replies)
    load more comments (4 replies)
    [–] LainTrain@lemmy.dbzer0.com 13 points 1 month ago

    :w !sudo tee %

    [–] Katzimir@lemmy.dbzer0.com 11 points 1 month ago

    now i feel shame. I used to love breaking my xorg.conf in nano

    [–] jumponboard@lemmy.world 9 points 1 month ago (1 children)

    Why does it have to be transcribed into numbers anyway?

    [–] hemko@lemmy.dbzer0.com 42 points 1 month ago

    Doesn't have to. You can also do something like

    chmod +rw ./filename

    [–] daggermoon@lemmy.world 7 points 1 month ago (1 children)

    Total noob. Any experienced user knows it's

    run0 micro file.txt
    
    load more comments (1 replies)
    load more comments
    view more: next β€Ί