373
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jan 2025
373 points (97.9% liked)
Linux
48878 readers
996 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
yesThe most positive command you'll ever use.
Run it normally and it just spams 'y' from the keyboard. But when one of the commands above is piped to it, then it will respond with 'y'. Not every command has a true -y to automate acceptance of prompts and that's what this is for.
Also, you can make
yesreturn anything:I.... did not know that. Thanks, TIL!
That's really neat but also seems like it could be quite dangerous in a lot of use-cases!
Absolutely, but when you do need it, it's brilliant.
What's the syntax here? Do I go
I'm not sure if I've had a use case for it, but it's interesting.
Also my favourite way to push a core to 100% CPU
how is that better than
cat /dev/zero > /dev/nullor
while true; do :; doneWho said it was better? It’s just my favourite.
Like my favourite shirt, it’s no better than the others, but it brings me a little joy :)
That will just wait for
commandto finish properly and then runyes.What you want to run is
yes | command, so it spams the command with confirmations.truedelivers error level 0,falseerror level 1.yes && echo True || echo Falsewill always be True.false && echo True || echo Falsewill always be False.Common usage is for tools that ask for permissions and similiar.
yes | cp -ihas the same effect ascp --force(-i: prompt before overwrites).Sorry, I should have explained that. it's ~~command | yes~~
yes|command- Eg,yes|apt-get update(Not a great example since apt-get has -y, but sometimes that fails when prompting for new keys to accept)Edit: I got it backwards, thanks @lengau@midwest.social for the correction.
You've got it backwards - you need to pipe the output of
yesinto the input of the command:So I did - thanks for the correction, edited.
For some cases I use “|| true”.
The idiom accepts that the preceding command might fail, and that’s OK.
For example, a script where mkdir creates a directory that might already exist.
mkdir -pwill not complain if the dir existsRight, it was an example of a pattern. In that case, -p could be used.
I figured as much. Just wanted to show another option.