Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I could not really understand the use of tmpfs. Yes, tmpfs is stored in memory instead of hard disk, then what now? What is the use of it
One more thing, devtmpfs. Correct me if I'm wrong. Is it now the one who maps the devices on my machine? I red on internet that even without udev it can map your devices.
I could not really understand the use of tmpfs. Yes, tmpfs is stored in memory instead of hard disk, then what now? What is the use of it
It's extremely fast for a file system and is non-persistent between reboots. I've made use of the first for when I've wanted to compress large files, and the second where a process downloads decryption keys from another source and stores them in tmpfs, as this is stored in memory and not on a hard disk it is considered secure and not "at rest" for many audit processes.
tmpfs is like a traditional ramdisk but with two great advances:
1) A ramdisk has a fixed size. For safety reasons, you usually make it larger than you really need, but that extra space gets subtracted from available memory whether you use it or not. A tmpfs system grows and shrinks as required by the content.
2) A ramdisk is always in ram. So that block of ram is sterilised; you can't use it for anything else. A tmpfs can be swapped out like a program image when it isn't being used.
As for devtmpfs, that's just a filesystem that combines the properties of a devices filesystem with tmpfs.
yes, it was already well explained. Another example: programs usually create temporary files during their life. Using tmpfs (ramdisk) may allow to run those programs faster (this is especially true for compiling, where there will be a lot of intermediate files). tmpfs is (can be) at about 1000 times faster than an ssd.
Wow, thanks for the explanations. I get it now. I might use it when I'm extracting/compressing large files for it to become faster. Know I know tmpfs is awesome as it can automatically increase and decrease its space.
Quote:
Originally Posted by hazel
As for devtmpfs, that's just a filesystem that combines the properties of a devices filesystem with tmpfs.
So the devices lookup will become fast? My devtmpfs is mounted on /dev/shm
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.