The query actually shows a lack of confidence. He should have googled "How to recover a file from /dev/null?" instead.
this post was submitted on 21 Oct 2024
345 points (99.4% liked)
linuxmemes
21197 readers
62 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
- Stack Overflow
Top voted answer
"Why would you want to?"
"... 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/random
You 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?
I was also curious, here's a good answer:
https://unix.stackexchange.com/questions/670199/how-is-dev-null-implemented
The implementation is:
static ssize_t write_null(struct file *file, const char __user *buf,
size_t count, loff_t *ppos)
{
return count;
}
So it's basically doing nothing and lying about it. 😆
"I accepted all of the bytes you gave me. I didn't do anything with them, but I accept you gave them to me".
Could've at least say thank you...
It's open source. If manners are an important feature to you perhaps look into contributing... :)
Yeah, that could actually be fun to be honest, lol 😂. But I just know the PR would be rejected, lol 😂.
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?
Because apparently, he moved it there... and doesn't know what /dev/null is...
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...
It is still on the disk though
Do people not understand how files work? Actually never mind that makes sense.
Yes.