tmpfs is a RAM-based filesystem. Files saved to a folder mounted using tmpfs will be saved directly to system RAM.
In Slackware tmpfs is mounted on /dev/shm by default. The fstab line is as follows. tmpfs /dev/shm tmpfs defaults 0 0 Default permissions in the /dev/ folder. bash-4.3$ ls -l /dev |grep shm drwxrwxrwt 2 root root 340 Jul 25 20:13 shm You say on your system you have it set to tmpfs /tmp tmpfs defaults,mode=1777 0 0 This means that YOU manually moved the /tmp folder, which normally is part of your root partition to an isolated storage device. In this case, your storage device is a virtual space in RAM, not a gpt or mbr partition. It's not uncommon for people to move /home, /var, or /tmp to isolated spaces such as a dedicated SSD or ramdisk for speed and security. Two Months ago you rebooted your computer and every file in /tmp vaporized. All thanks to a change you made in /etc/fstab. On Wed, Jul 25, 2018 at 5:37 PM, Rich Shepard <[email protected]> wrote: > On Wed, 25 Jul 2018, wes wrote: > > You're still referring to tmpfs as if it were a device. It isn't. >> > > Wes, > > But a bind mount would work, yes? > > If there's a known issue with chromium and opera relating to something not >> being mounted using tmpfs, do you have a link to a description? I tried >> googling a little, but didn't find the right thing quickly. >> > > What is the console output you get? >> > > See this web page: > > https://bugs.chromium.org/p/chromium/issues/detail?id=571394 > > This is what /etc/fstab should have: > tmpfs /dev/shm tmpfs defaults 0 0 > > Rich > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
