Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Embedded Linux Programming

You're reading from   Mastering Embedded Linux Programming Unleash the full potential of Embedded Linux with Linux 4.9 and Yocto Project 2.2 (Morty) Updates

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781787283282
Length 478 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Mr. Chris Simmonds Mr. Chris Simmonds
Author Profile Icon Mr. Chris Simmonds
Mr. Chris Simmonds
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Starting Out FREE CHAPTER 2. Learning About Toolchains 3. All About Bootloaders 4. Configuring and Building the Kernel 5. Building a Root Filesystem 6. Selecting a Build System 7. Creating a Storage Strategy 8. Updating Software in the Field 9. Interfacing with Device Drivers 10. Starting Up – The init Program 11. Managing Power 12. Learning About Processes and Threads 13. Managing Memory 14. Debugging with GDB 15. Profiling and Tracing 16. Real-Time Programming

Temporary filesystems

There are always some files that have a short lifetime or have no significance after a reboot. Many such files are put into /tmp, and so it makes sense to keep these files from reaching permanent storage.

The temporary filesystem, tmpfs, is ideal for this purpose. You can create a temporary RAM-based filesystem by simply mounting tmpfs:

# mount -t tmpfs tmp_files /tmp

As with procfs and sysfs, there is no device node associated with tmpfs, so you have to supply a place-keeper string, tmp_files in the preceding example.

The amount of memory used will grow and shrink as files are created and deleted. The default maximum size is half the physical RAM. In most cases, it would be a disaster if tmpfs grew to be that large, so it is a very good idea to cap it with a -o size parameter. The parameter can be given in bytes, KiB (k), MiB (m), or GiB (g), like this...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image