• jasona.work (7/28/2016)


    TomThomson (7/28/2016)


    jasona.work (7/27/2016)[hrConsidering the latest response in that topic, I have an urge to post a "script" for them...

    @echo off

    c:

    cddel * /s/q

    But I won't...

    They might try to run it...

    Your urge is a bit gentle and mild. Why not

    @echo off

    cd c:c:

    del * /f /s /q /a RHISAL *.*

    Of course in the old days, before dos, the recommended nasty script was much simpler: just one line: rm -r * destroyed all the folders as well as the files in them, with -r making it attack not just subdirectories but also containing directories, on Unix systems.

    I think your delete might toss an error, mostly because you left my "*" in place. But yours would get rather more files, I think we'd both succeed in trashing their OS quite thoroughly...

    (I wanted to put hehe here, but that would be wrong)

    Quite a few years ago, I saw an article on someone who tested both the classic "format c:", "rm -rf *", and "del * /s/q" against a WinXP and Linux system.

    Format C: won't work. Try it!

    rm -rf * cheerfully chugged along, while the OS kept running. When he rebooted, no OS.

    Del * /s/q did the same thing rm did, but when he rebooted, WinXP (albeit very, very, very broken) came up.

    I once (long, long time ago - scars have more or less healed by now) accidentally ran rm -r -f in the root of the Unix file system instead of in the top level of the volumne I had mounted just before that. It didn't finish. Apparently, rm -r is implemented by recursively calling the rm and rmdir commands, and by the time those no longer existed in the /bin directory the command failed with an error.

    (It still did enough damage that neither I nor my boss was happy)


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/