Главная
Study mode:
on
1
Introduction
2
Readonly rootfs
3
Why readonly
4
Image updates
5
Mount rootfs
6
Memory areas
7
Stateless
8
Enlightenment
9
Example
10
Blockdump
11
Journaling
12
Verta
13
Path names
14
Problems on first boot
15
Log files
16
Random seed
17
Dropout
18
First boot
19
Android
20
Conclusion
21
QA
22
Advantages and Disadvantages
23
symlinks
24
mount
25
systemd
26
volatilepast
Description:
Explore the theory and practice of implementing a read-only rootfs in embedded Linux systems through this informative conference talk. Discover how configuring a read-only rootfs enhances system robustness, reduces flash storage wear, and simplifies system image updates and factory resets. Learn to identify components requiring state storage, distinguish between volatile and non-volatile states, and implement various techniques for mapping writes onto appropriate storage types. Follow along with a live demonstration using a standard Yocto Project build to understand the necessary changes for achieving a real-world embedded system with read-only rootfs. Delve into the implications for software image updates and gain insights from Chris Simmonds, an experienced embedded Linux consultant and trainer. Cover topics such as mount points, memory areas, stateless systems, journaling, path names, first boot challenges, log files, random seed generation, and Android implementations. Conclude with a Q&A session addressing advantages, disadvantages, symlinks, mounts, systemd, and volatile storage in the context of read-only rootfs systems. Read more

Read-only Rootfs: Theory and Practice for Embedded Systems

Linux Foundation
Add to list
0:00 / 0:00