sudo rm -rf /*

preview_player
Показать описание
what happens if we enter this command in a terminal ?
  1. Thomas Ergias
Рекомендации по теме
sudo rm -rf 0:01:00

sudo rm -rf /

sudo rm -rf 0:02:34

sudo rm -rf /* - What Happens? | 50 Sub Special

sudo rm -rf 0:00:13

sudo rm -rf /*

OK Google, sudo 0:00:16

OK Google, sudo rm -rf /

rm -rf / 0:00:36

rm -rf / (Don't try this at home...) #linux #programming

Here's what happens 0:02:36

Here's what happens when you run sudo rm -rf / in Linux?

What happens when 0:01:30

What happens when you sudo rm -rf / your machine?

MacOS Ventura vs. 0:03:21

MacOS Ventura vs. sudo rm -rf

INSTALL PSQL MAC 0:09:49

INSTALL PSQL MAC NO HOMBREW | UNINSTALL PSQL | PG_ADMIN NOT WORKING

Looks like 'sudo 0:00:23

Looks like 'sudo rm -rf /' is not as dangerous as people sound! #linux

When they say 0:02:04

When they say 'Run rm -rf /*'

This is for 0:00:29

This is for those who know 'sudo rm rf no-preserve-root' #linux #memes

When You Ask 0:00:10

When You Ask ChatGPT to Honor Your Grandma with sudo rm -rf #chatgpt #chatgptinsights #shorts

$ sudo rm 0:00:17

$ sudo rm -rf --no-preserve-root this command in Linux 💀❌ #cybersecurity #hacker #trending #viral...

POV: Me when 0:00:15

POV: Me when I tell the class to sudo rm -rf their computers #shorts #schoolmemes

What does sudo 0:06:42

What does sudo rm -rf /* do to modern Linux

sudo rm -rf 0:00:09

sudo rm -rf /*

How A Steam 0:11:49

How A Steam Bug Deleted Someone’s Entire PC

What if you 0:04:00

What if you Delete the System on EVERY OS?

sudo rm -rf 0:01:29

sudo rm -rf *

STOP using rm 0:00:54

STOP using rm -rf to delete files!

What happens when 0:01:00

What happens when you rm -rf your computer

☠️ sudo rm 0:00:41

☠️ sudo rm -rf / --no-preserve-root

sudo rm -rf 0:03:46

sudo rm -rf

Комментарии
Автор

This will affect the NVIDIA drivers I think

badpiggies
Автор

Every linux supercomputer if it was gone

ConclusiveLion
Автор

I actually had this happen on a real production IT system that I was working towards taking over the management of. I was working for an outsourcing company, and the system was in production and being operated and managed by the application vendor.

The reason we hadn't taken it over was because there was zero operational documentation and zero scripted operations. So the vendor was operating it manually based on instructions scribbled on a scrap of paper.

These instructions said: 1. "cd /tmp"; 2. "rm -yr *"; 3. "reboot".

Unfortunately, one evening having done step one, the operator received a telephone support call and as part of answering that he went root (presumably with "sudo -i" which put him back in the root directory). When he finished the call he executed steps 2 and 3 without exiting root thus doing EXACTLY what this video shows.

D'UH!!!

To cap it all, it then turned out that the system backups hadn't been working either and hadn't been tested and it took them 2 or 3 weeks to rebuild this production system. DOUBLE

I might add that this was one of two similar screw ups (the other resulting from deletion of the production SQL database) at the end of a disastrous fixed price application development where the system has already been rejected and redeveloped from scratch and where the initial go live was abandoned twice, once because an untested system timezone change caused it to fail, and once because the system has never been tested on a production sized database, and several missing indexes resulted in use response times on a linked production customer call healing system going from 1sec to over 30mins.

Put simply a fiasco from start to finish from a MAJOR MAJOR software house.

SodalisUK
Автор

Merci monsieur, je vais faire ça de suite

clemdeqqpart