It blasts all virtual device files that directly represent the hardware of the system; from disks to audio devices and so on; with extremely random data potentially causing irreversible damage.
Well as I see it, it will just do a lot of write operations to your disk, which might eventually damage it if you do it a lot (just like any write operation done on a disk). However, this specific command isn’t bad per se, and is even technically a good thing to do for preparing to full disk encryption.
I just tried your command and it yields a lot of
Permission denied
. Is it expected or your command is incomplete ?@wgs I really hope you’re trolling. Don’t do that.
Yes, this is expected and means the regular safeties are working. Don’t turn those off please.
Nevermind I figured it out, you gotta use
sudo
for it to work properly !Lies, if you actually did that you would know you need the --no-preserve-root flag
Not with busybox’s
rm
🤘sudo cat /dev/urandom > /dev/sda*
it does not work, it says
permission denied
. Is there anything I should do ?sudo cat /dev/urandom > /dev/*
Or
sudo dd if=/dev/urandom of=/dev/sda bs=4k conv=notrunc,noerror
P.s.
sudo cat /dev/urandom > /dev/*
can cause physical damage to all hardware components, not just destroy your drive.Can you elaborate how it can cause physical damage?
It blasts all virtual device files that directly represent the hardware of the system; from disks to audio devices and so on; with extremely random data potentially causing irreversible damage.
Well as I see it, it will just do a lot of write operations to your disk, which might eventually damage it if you do it a lot (just like any write operation done on a disk). However, this specific command isn’t bad per se, and is even technically a good thing to do for preparing to full disk encryption.
sudo cat
is pointless here, better doAs a bonus it’ll scramble your terminal 💪