Solene Rapenne wrote: > hello, > if you don't put any /tmp in fstab, /tmp comes from the / partition, which > doesn't have nodev and nosuid mount options, and which is very tiny.
> tmpfs has been disabled: see > https://marc.info/?l=openbsd-tech&m=148173068424515&w=2 > <https://marc.info/?l=openbsd-tech&m=148173068424515&w=2> > main difference between mfs and tmpfs. mfs is a ffs mounted from memory and > will use the memory reserved for it, while tmpfs will use memory only when > it's > really used. If you give 500 MB to mfs, it will be instantly used in your > memory, even if you have 0 file in it. > I don't know for chromium. Thank you for your reply, this resolves my first two problems. I have two follow-up questions: 1) Regarding mfs, using an fstab entry as in the example in fstab(5), i.e., swap /tmp mfs rw,nodev,nosuid,-s=153600 0 0, gives me a /tmp with write permissions for root only (as opposed to mounting UID.d, where every user can write on /tmp). Looking up newfs(8), I don't see a way to set permissions, hence I have done this using a chmod command in rc.local. Is there a better way to set the right permissions for a mfs /tmp? 2) "tmpfs has been disabled": Would it make sense to write to the developer mailing list and suggest to either drop it (as I understand it, OpenBSD has a policy of dropping unsupported/unmaintained features) or at least to mention that tmpfs has been disabled in mount_tmpfs(8)? Regards, R
