cm0002@lemmy.world to Programmer Humor@programming.dev · 1 day agoSoftware Terminologylemmy.mlimagemessage-square179fedilinkarrow-up11.07Karrow-down143cross-posted to: programmerhumor@lemmy.ml
arrow-up11.02Karrow-down1imageSoftware Terminologylemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 day agomessage-square179fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarewhatwhatwhatwhat@lemmy.worldlinkfedilinkarrow-up29·1 day agoI’d call that a file loaded to memory
minus-squarejaybone@lemmy.ziplinkfedilinkEnglisharrow-up4·23 hours agoMost files are loaded to memory in order to make any kind of use out of them. I.e. read/write operations.
minus-squarewhatwhatwhatwhat@lemmy.worldlinkfedilinkarrow-up3·20 hours agoThat’s true! I supposed it would be more precise to say that all processes are files loaded to memory, but not all files loaded to memory are processes. Sort of like the whole arachnids / spiders situation.
minus-squarejaybone@lemmy.ziplinkfedilinkEnglisharrow-up3·23 hours agoWhy not? Represented in /proc? exec() and fam? Read and write to it?
What about a process? File gone wild?
I’d call that a file loaded to memory
Most files are loaded to memory in order to make any kind of use out of them. I.e. read/write operations.
That’s true! I supposed it would be more precise to say that all processes are files loaded to memory, but not all files loaded to memory are processes. Sort of like the whole arachnids / spiders situation.
Why not? Represented in /proc? exec() and fam? Read and write to it?