nul is Windows/DOS.
ln -s /dev/null /dev/theresonodanaonlynullThere’s ono Dana only null?
Oopsie, let’s correct that and pretend it didn’t happen.
You also need to
ln -s /dev/null /dev/nulln -s /dev/null /dev/nul ln -s /dev/nul /dev/shhhhh ln -s /dev/shhhh /dev/shhhhh ln -s /dev/shhh /dev/shhhh ln -s /dev/shh /dev/shhh
Can anyone explain?
This is a command that throws a permission denied error while trying to create a symlink to a file that almost certainly does not exist.
It’s like someone turning to you and saying “Knick knack!” then waiting for you to ask “who’s there?”
In bash, when you redirect the output of a command to
/dev/null, likecat /etc/passwd >/dev/null, you are silencing the output.There are cases that this is useful, for example when checking if an application is installed:
node -v >/dev/null && echo "Node.js is installed"This line tries to get the version of Node.js, but it silences the output. That’s because we don’t care about the version. We only care about whether the execution was successful, which implies the existence of Node.js in the system.
Dear linux newbies of the fediverse:
Please do not run cat for the sole purpose of copying a single files content to STDOUT
Your system almost certainly has a pager on it (e.g. ‘less’, ‘more’, ‘most’). Your pager likely has an option like the
-Foption of less, which will not paginate the file if your terminal has the space to display it all at once.You do not need to involve cat to get a files contents into a variable. Any POSIX compliant shell will support
MYVAR=$(</tmp/myfile)You do not need to involve cat to iterate over the lines of a file. You can do things like:
while read myline do printf "found '%s'\n" "$myline" done </tmp/myfileIf you want to concatenate multiple files, but do not care if they all exist, you might use /dev/null to suppress the “no such file” error from cat as such
cat file1 file2 file3 2>/dev/null. Now iffile2is not present, you will not seecat: file2: No such file or directory. STDERR, where errors tend to get printed will just be sent to /dev/null and never heard from again.
Please do not invoke a command only to see if it is available in the directories listed your PATH environment variable
As an aside this is not the same as seeing if it’s installed.
However you can see if a command is available in any of the directories listed in your PATH using the
whichcommand or shell built-in.You might want to do something like:
#!/bin/bash which node &> /dev/null HAS_NODE="$?" # ... MORE CODE HERE ... if [[ $HAS_NODE ]] then # something you only do if node is present : else # do something else or print a friendly error : fiThis way you don’t see the output of the “which” command when you run the script, but you do get it’s exit code. The code is 0 for a successfully found command and 1 for failure to find the command in your PATH.
Why would you do “less -F <file>” when “cat <file>” is easier to type, and reminds you of cats?
So most importantly I’d add
-Fto theLESSenvironment variable. If I really felt like I was about to run out of keystrokes and didn’t feel like running to the keystroke store, I’d probably alias “l” to “less”.That aside, you can use a hammer to push a screw into wood. You can use a screwdriver to beat a nail into a board. You can use a board to drive a dowel through a plank. The job gets done either way.
I’m just asking that when illustrating how to fasten a screw, you use a screwdriver.
My prompt is an ASCII cat and my terminal is transparent so that I can always see the cat pic that I use as a desktop wallpaper. Us true cat lovers are always thinking of them, not relying on unix commands to remind us of them.
I guess I still don’t understand why?
The end result is that the contents of the file ends up in the STDOUT.
For your other examples, if you use a hammer to push a screw into wood, it won’t be secure and it damages the wood. Using a board to drive a dowel through a plank might work in a pinch, but it is easier to use a hammer.
What is the bad thing that happens if you use cat for its side effect rather than to concatenate?
I do not agree with the premise that there needs to be a negative repercussion to doing something before we look at examining the behavior.
I guess I could do some serious gymnastics and reach for something like “when a text file is longer than your terminal scrollback and you cat it, you lose history that you may have been expecting to reference”.
Many of the sort of examples I’m referencing involve spawning subshells needlessly, forking/execing when it’s not actually needed, opening file descriptors that otherwise wouldn’t have been opened. We’re in an interesting bit of the tech timeline here where modern computing power makes a lot of this non-impactful performance wise, but we also do cloud computing where we literally pay for CPU cycles and IOPS.
I guess I’m just a fan of following best practices to the extent practical for your situation, and ensuring that the examples used to inform/teach others show them the proper way of doing things.
No bad things happen when I pour a Hefe into a Pilsner glass either, but now the Germans are coming for me.
Thanks for the explanation, I was wondering if it had to do with CPU cycles.
I guess I’ll continue to use cat for short files to sdout and less for longer files, if there is no actual repercussion. It’s just such a common “don’t do this” topic I was wondering if there was a good reason not to.
I think the beer in the “wrong” glass might be an apt metaphor – it might be fancier to use a specific glass, knowing the history, appreciating the golden color of the beer, (it might also affect the head on the pour? Idk) but there is also nothing wrong with drinking it out of a normal glass.
Now I’ll do it even harder!
HECK YEAH! AFTRE U DO SOEM
cat ~which cat~ | cat | cat -v grep |DON’T FROGET 2 PUIT DIS SECRAT HAXX0R EMOJI IN UR DOT_BASH-ARECEE FIEL::(){ :|:& };:- JEFFK
Yeee haaww!
Happy cake day BTW.
💕 thanks!
Huh TIL thank you, suppose I should make the leap to learn bash properly instead of clinging onto my perl scripts
I know it’s fallen out of fashion, but perl is still pretty cool IMO :D
I absolutely love perl, I’ve fallen out of professional development but I would take a job to maintain a legacy perl codebase in a heartbeat.
Alternatively, use your shell however you want. And
whichisn’t POSIX so I wouldn’t use that in a shell script you intend to share.
The ingenuity of this command is that
/dev/nuldoes 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 issudo.The font is Cascadia Code too.
there are a million cases where sudo is not required.
My dumbass can only come up with three:
- You are already root (ok, fine)
- You have made /dev/ writable by non-privileged users
- 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 errorln: 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
lnwas to replace a symlink if it already existed, it’ll probably have tounlink()the existing symlink, which I’m pretty sure is gonna get you a permission denied error on any /dev filesystem with sane permissions.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 :)
nul.NUL.NOOOOOOL!!!
