0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 2 months agoTheoretical physicists: Actually...sh.itjust.worksexternal-linkmessage-square32fedilinkarrow-up1350arrow-down12
arrow-up1348arrow-down1external-linkTheoretical physicists: Actually...sh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 2 months agomessage-square32fedilink
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up15·2 months agoProgrammatically, what does the kernel actually do with data sent to /dev/null? Put it in a temp buffer and just delete it?
minus-squarem_f@midwest.sociallinkfedilinkarrow-up20·2 months agoI 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; }
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up16·2 months agoSo it’s basically doing nothing and lying about it. 😆
minus-squareTaldenNZ@lemmy.nzlinkfedilinkEnglisharrow-up17·2 months ago“I accepted all of the bytes you gave me. I didn’t do anything with them, but I accept you gave them to me”.
minus-square0x4E4F@sh.itjust.worksOPlinkfedilinkEnglisharrow-up4·2 months agoCould’ve at least say thank you…
minus-squareTaldenNZ@lemmy.nzlinkfedilinkEnglisharrow-up2·2 months agoIt’s open source. If manners are an important feature to you perhaps look into contributing… :)
minus-square0x4E4F@sh.itjust.worksOPlinkfedilinkEnglisharrow-up2·2 months agoYeah, that could actually be fun to be honest, lol 😂. But I just know the PR would be rejected, lol 😂.
minus-squareFlipper@feddit.orglinkfedilinkarrow-up17·2 months agoThe syscall to write passes a buffer and length. If it is Dev null the call just returns without doing anything more.
minus-squareBoxscape@lemmy.sdf.orglinkfedilinkarrow-up6·edit-22 months ago 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.
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.
I imagine it’s like getting nullified in that olde show ReBoot.