0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 1 month agoTheoretical physicists: Actually...sh.itjust.worksexternal-linkmessage-square8fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkTheoretical physicists: Actually...sh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 1 month agomessage-square8fedilink
minus-squareTimeSquirrel@kbin.melroy.orglinkfedilinkarrow-up0·1 month 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-up0·1 month 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-up0·1 month agoSo it’s basically doing nothing and lying about it. 😆
minus-squareTaldenNZ@lemmy.nzlinkfedilinkEnglisharrow-up0·1 month 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”.
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”.