cm0002@lemmy.world to Programmer Humor@programming.dev · 1 year agoSoftware Terminologylemmy.mlimagemessage-square200linkfedilinkarrow-up11.23Karrow-down150cross-posted to: [email protected]
arrow-up11.18Karrow-down1imageSoftware Terminologylemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 year agomessage-square200linkfedilinkcross-posted to: [email protected]
minus-squarewhatwhatwhatwhat@lemmy.worldlinkfedilinkarrow-up32·1 year agoI’d call that a file loaded to memory
minus-squarejaybone@lemmy.ziplinkfedilinkEnglisharrow-up5·1 year 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-up4·1 year 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·1 year 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?