this post was submitted on 11 Jun 2025
138 points (96.0% liked)

linuxmemes

25706 readers
121 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 13 points 1 week ago (5 children)

    The ingenuity of this command is that /dev/nul does not exist, the correct path is /dev/null, however the command executes without error and creates a symlink to a non-existing path.
    The only thing missing is sudo.

    [–] [email protected] 0 points 1 week ago (1 children)

    there are a million cases where sudo is not required.

    [–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (2 children)

    My dumbass can only come up with three:

    1. You are already root (ok, fine)
    2. You have made /dev/ writable by non-privileged users
    3. Your non-privileged user already owns the symlink /dev/nul. Which "ok, fine", but also the point of command would have to be to functionally do nothing other than print out the error ln: failed to create symbolic link '/dev/nul': File exists

    I would love to understand the use case behind #2. I am also curious to see even 7 more cases, let alone your figurative million.

    In regards to #3 even if the behaviour of ln was to replace a symlink if it already existed, it'll probably have to unlink() the existing symlink, which I'm pretty sure is gonna get you a permission denied error on any /dev filesystem with sane permissions.

    [–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

    Follow up, tested and confirmed #3:

    [korthrun@host]$ ls -l /dev/korth
    .rw-r--r-- korthrun wheel 0 B Wed Jun 11 17:11:03 2025 /dev/korth
    [korthrun@host]$ rm /dev/korth
    rm: cannot remove '/dev/korth': Permission denied
    
    [–] [email protected] 1 points 1 week ago

    ln could be +s

    the kernel could have been modified

    I'm sure there is some way if using capabilities

    you don't need to be 'root', uid 0 is enough :)

    load more comments (3 replies)