Jump to content

Fstab: Difference between revisions

From postmarketOS Wiki
describe why /etc/fstab won't have / and /boot entries
 
No edit summary
Line 7: Line 7:


The initramfs accepts paths to the boot and root partitions as kernel parameters and falls back to searching by label, therefore it covers all use cases we have. Nowadays, we [[Boot_process#postmarketOS_initramfs|let the initramfs mount root and boot]], and do not have any entries for them in <code>/etc/fstab</code>.
The initramfs accepts paths to the boot and root partitions as kernel parameters and falls back to searching by label, therefore it covers all use cases we have. Nowadays, we [[Boot_process#postmarketOS_initramfs|let the initramfs mount root and boot]], and do not have any entries for them in <code>/etc/fstab</code>.
[[Category:Technical Reference]]

Revision as of 22:08, 6 July 2020

This article is about /etc/fstab in postmarketOS.

Usage in the boot process

Note It will look like this, once pmaports#664 is resolved.

We used to rely on /etc/fstab to find the postmarketOS boot and root partitions by their label. We had to find partitions by their label, because we did not always know the exact location or UUID of the partition in advance. However, by just relying on the label, we get unpredictable behavior if installing postmarketOS on both the eMMC and the SD card (pmaports#664).

The initramfs accepts paths to the boot and root partitions as kernel parameters and falls back to searching by label, therefore it covers all use cases we have. Nowadays, we let the initramfs mount root and boot, and do not have any entries for them in /etc/fstab.