cm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前Software Terminologylemmy.mlimagemessage-square200linkfedilinkarrow-up11.22Karrow-down150cross-posted to: programmerhumor@lemmy.ml
arrow-up11.17Karrow-down1imageSoftware Terminologylemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前message-square200linkfedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarewhatwhatwhatwhat@lemmy.worldlinkfedilinkarrow-up33·1 年前I’d call that a file loaded to memory
minus-squarejaybone@lemmy.ziplinkfedilinkEnglisharrow-up5·1 年前Most 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 年前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.
minus-squarejaybone@lemmy.ziplinkfedilinkEnglisharrow-up3·1 年前Why 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?