how the fuck does rm -rf / work when it removes itself
>>54433900
Real answer: It resides in RAM, retard.
Fake answer: AYY LMAO U RIGHT SON HIT DAT LIKE BUTTON
>>54433900
RAM
>>54433913
>>54433915
Fuck off niggers I know what RAM is
>>54434195
Even if the program is removed off disk it still is being run in RAM. In fact, all programs are loaded into RAM! Who knew?!
On Linux, program can still run even if you delete the executable.
Also, you can delete any running executable without locking problem, unlike Windows.
>>54434260
>On Linux, program can still run even if you delete the executable.
>Also, you can delete any running executable without locking problem, unlike Windows.
I never understood why this is not possible on Winblows
>>54434613
Because it's actually a really fucking stupid idea to be able to delete running executeables.
You aren't actually deleting the file, you're deleting the reference to the file. The file can still run because the OS knows where it is until it's execution is complete.
Shame on /g/.
>>54434260
No wonder linux is so insecure. On Windows you could never execute that. It's just a much smarter OS. That's the difference between a commercial OS made by professionals and a free OS made by amateurs in their free time.
btw you can't rm -rf / in Linux for a very long time now. Not without a special option.
And how do you think auto updates of a program work on Windows? It overwrites itself. What are you? A bunch of tech illiterate morons?
>>54435106
Also, nice b8 m8.
>>54435106
rmdir /S C:
>>54434761
It's your OS you do what you want that's all
>>54434613
>>54435106
It also one of the reason why windows need reboot after updates.
>>54435234
lol no.
>>54435234
lol maybe
>>54434761
But it's the reason why Linux can run updates without having to reboot the fucking machine.
ITT: people who have no idea what they're saying
>>54435304
>Windows offers an API that application developers can use to move, rename, or delete a file that’s in use. The application asks Windows to rename or move a file when the computer next reboots, and the request is written to the HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations value in the registry. When Windows boots up, it checks this registry key and performs any file operations programs have asked for.
>The application asks Windows to rename or move a file when the computer next reboots
>next reboots
>>54435385
This.
Also rm -rf doesn't even work.
>>54435030
And what happens when that data gets overwritten? Oops.
>>54435423
The executable is actually completely loaded into RAM, after it's opened there's no longer any need to read from disk, at least for the binary itself. So even if you deleted the executable and overwrote it, it's still in RAM.
The rm process loads itself into ram entirely and then deletes its own executable, because it doesn't have to access any resources from it.
