Theoretical physicists: Actually...
Theoretical physicists: Actually...
32 comments
-
-
"... 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.
-
-
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?
-
I was also curious, here's a good answer:
https://unix.stackexchange.com/questions/670199/how-is-dev-null-implemented
The implementation is:
c
static ssize_t write_null(struct file *file, const char __user *buf, size_t count, loff_t *ppos) { return count; } -
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.
-
-
This is the worst meme template, ever
-
Why would you be trying to recover something from a virtual device?
32 comments
The query actually shows a lack of confidence. He should have googled "How to recover a file from /dev/null?" instead.
Done
Can you not just try it with a dummy folder??
Stack Overflow
Top voted answer
"Why would you want to?"