You must log in or register to comment.
The query actually shows a lack of confidence. He should have googled “How to recover a file from /dev/null?” instead.
Can you not just try it with a dummy folder??
- Stack Overflow
“… you don’t. You recover it from /dev/random. Eventually.”
And if really want quality recovery,
/dev/urandom. Might take a bit longer, but it’s worth the wait 👌.
Duh, just read it back from
/dev/randomYou will recover the data, you just need to wait long enough.
Patience is key.
I mean, if the data was written to a HDD, then any forensic tool can read the magnetic residual patterns on the metal platters instead of looking for file headers?
That is true, though it would be pointless to look for it in
/dev/null.There is nothing in /dev/null, and no man needs nothing.
A hole would be something, this is NOTHING!
/dev/void🤔
That hack Torvalds keeps denying my pull request to implement /dev/aether which would immediately begin overwriting the entire disk and all other mounted storage with the repeating content of whatever is moved there.
That is… brilliant! I love it!
Programmatically, what does the kernel actually do with data sent to /dev/null? Put it in a temp buffer and just delete it?
The syscall to write passes a buffer and length. If it is Dev null the call just returns without doing anything more.
Programmatically, what does the kernel actually do with data sent to /dev/null?
I imagine it’s like getting nullified in that olde show ReBoot.
Why would you be trying to recover something from a virtual device?
Because apparently, he moved it there… and doesn’t know what
/dev/nullis…It is still on the disk though
Do people not understand how files work? Actually never mind that makes sense.
Yes.
It is still on the disk though
Do people not understand how files work? Actually never mind that makes sense.
Do people not understand how files work?
Oh honey, imagine trying to tech-support a family of rednecks. Threaten to charge them for services and they’ll stop pretty quick though…
