←back to thread

Save your disk, write files directly into RAM with /dev/shm

(hiandrewquinn.github.io)
66 points hiAndrewQuinn | 1 comments | 26 Jun 25 23:04 UTC | HN request time: 0.254s | source
Show context
pizlonator ◴[27 Jun 25 00:01 UTC] No.44392636[source]▶
The reason why this might be a bad idea is that /dev/shm is used for shm_open(3).

So in theory some program might pass a name to shm_open that collides with whatever you put in /dev/shm.

Unlikely but possible

replies(1): >>44392672 #
layer8 ◴[27 Jun 25 00:07 UTC] No.44392672[source]▶
How is that different from two unrelated programs using shm_open with conflicting file names? Such programs need to ensure unique names anyway.
replies(1): >>44409640 #
1. pizlonator ◴[29 Jun 25 01:28 UTC] No.44409640[source]▶
Expecting a program to do that is one thing.

Expecting yourself to do that when you use /dev/sum is another