Shootout: 'rm -Rf /' vs. 'Format C:' 513
skyshock21 writes "There's an article over at hohle.net about what actually happens when you type the commands Format C: in windows versus rm -Rf / in Linux. Very interesting results indeed. Myths are busted, and hilarity ensues."
An interesting topic, at last!! (Score:2, Interesting)
Yes I rta (Score:2, Interesting)
To remove this comment press F4 on windows...
And FP btw
slow? (Score:3, Interesting)
Re:Yes I rta (Score:2, Interesting)
Go away, you don't exist (Score:4, Interesting)
rm -rf / protection in Solaris (Score:3, Interesting)
Re:An interesting topic, at last!! (Score:4, Interesting)
Re:Try it with NFS... (Score:5, Interesting)
1. He left the root of the storage array mounted
2. He left it mounted under
3. He left the tmp-cleaning cron job enabled
When we started to see user file go away (but directories left intact) we thought we were under some kind of attack... we were right in a way
Re:openbsd rm (Score:3, Interesting)
Re:Ok (Score:2, Interesting)
the beautifulness of this article (which i haven't read) is that it (probably) frames the difference between two OS's on the basis of 'stupidest luser thing to type', and thus is interesting to
Re:...vs Magnet vs Tossage (Score:5, Interesting)
Unfortunatly a Taxi driver took the PC with him and managed to boot the machine and found an enormous ammount of very confidentinial information on the HDD. Information about some top crime and fraude cases. The Taxi driver then sold this HDD to a dutch TV crime fighter.
In the end this got the prosecutor fired. Which I think is sort of unreasonable, since the major issue is the justice departments lack of descent security procedure.
Re:Slashdotted, mirror: (Score:1, Interesting)
http://hohle.net.nyud.net:8090/scrap_post
Re:openbsd rm (Score:3, Interesting)
This is quite true, which is why shred is generally more effective when used on an entire device (/dev/hdb, /dev/fd0, etc.) rather than on a single file on a filesystem. Even then, however, it may not be completely effective if the drive's firmware has moved your data around behind-the-scenes. But it's probably good enough for a lot of people depending on just how valuable the deleted data is.
Re:rm -Rf / (Score:2, Interesting)
So, there I was, late at night, getting tired of all those #%!&/#!%# backup-files.
Since I wanted to keep my
That was a loooong week
Re:The most beautiful of all solutions (Score:3, Interesting)
A couple months ago I bought a new system and after I got done transferring my files I gave my room mate my old drives. One of them worked OK on her Windows system for all of about 3 days, then she tells me that her friends who provide her Windows support though I was some sort of IT God because I'd set Windows up so that they couldn't delete the files on that drive, even with admin support. I disclaimed all responsibility, saying that I'd just gone through the install normally.
Well after another few days her friends had thrown their hands up saying they couldn't do anything with the system. At this point we decided that something they'd done probably hosed the system up, so we decided to reinstall Windows. Only the windows install fdisk and format didn't seem to want to touch the drive either.
Still not trusting Microsoft, I fired up a knoppix CD and went after it with the linux fdisk. No dice. Finally I did a dd if=/dev/zero of=/dev/hda. And THAT didn't work.
"Inconceiveable," I said to myself but I had one weapon left in my arsenal. I popped out to Maxtor's web site and downloaded the low level format utility for that type of drive. Now this was the first time I'd ever low level format an IDE drive, so I was quite excited. I fired it up and let it go. And THAT didn't work. So I decided that the drive was no longer capable of being written and removed it from the system.
The funny thing about this while mess (Other than me wasting about a week on the system) was that no one ever indicated that there was any error writing to the drive, and it actually looked like data on the drive was changing up until the system was rebooted. All I can think is that the data was being changed on an on-disk RAM buffer on the drive, but that the drive's physical ability to be written no longer existed. Even my attempt to low-level format the drive looked like it was working right up until I rebooted the system.
... or errant symlinks (Score:4, Interesting)
Along the same lines, I had at one point a link "~achurch" in my public_html directory, for compatibility after my homepage changed URLs. So (you can guess what comes next, I'm sure) I decided one day, several years later, to clean up my web stuff:
$ rm -r tmp/ x.html [...] ~achurch/ /home/achurch/.xcdroast? _
rm: override permissions 000 for
I have no idea why mny .xcdroast was 000, but it saved me a huge amount of frustration. I now place a file "..norm-r", mode 000, in important directories and rename things around to make sure it's always first in the directory file. And I never, ever use -f.
Re:text (Score:1, Interesting)
D:\>format c:
Invalid parameter -
Re:...vs Magnet vs Tossage (Score:5, Interesting)
On my base, we sometimes took the drives over to EOD (Explosive Ordinance Disposal). They reportably had a great time.
Re:A more appropriate shootout (Score:2, Interesting)
where losepart.src is:
F 200 L1000 0
A 100
MOV AX,301
MOV BX,200
MOV CX,1
MOV DX,80
INT 13
INT 20
G
q
Re:sudo password (Score:4, Interesting)
Re:...vs Magnet vs Tossage (Score:4, Interesting)
Re:...vs Magnet vs Tossage (Score:4, Interesting)
Also, if you don't do a bad block scan {which wipes out any pre-existing data good and proper} on a used hard drive when you create the file system{s} on it, you're just asking for trouble.
I recommend dd if=/dev/audio of=/dev/hda1 {or whatever; but basically you want to get the raw data coming in from the sound card and write it straight to the disk partition} before passing on a used drive. Crank up the input gains to the max, but don't actually plug anything in
Re:openbsd rm and journalled filesystems (Score:3, Interesting)
And I'm not so sure about the viability of recovering overwritten data anyway, even with electron microscopes and whatnot. Let's face it, if it was at all practical, someone, somewhere would have used the techniques to build a high-capacity drive that worked by storing new data "over the top of" old data, and there'd be a fanfare of press releases about it -- and no end of debate on Slashdot over whether the patent was enforcible.
Microscopic techniques might have worked once with low density devices, but today's drives can easily pack 2000x as much information into the same amount of space as was common just 10 years ago. It's my assertion that all claims regarding the recoverability of overwritten data are hopelessly exaggerated if not absolute bullshit. I'd like to see a proper scientific study, but I have a feeling there are more compelling reasons not to do one
Re:...vs Magnet vs Tossage (Score:3, Interesting)