Fstab: Difference between revisions
Appearance
No edit summary |
issue is resolved, remove related note |
||
Line 2: | Line 2: | ||
=== Usage in the boot process === | === Usage in the boot process === | ||
We used to rely on <code>/etc/fstab</code> to find the postmarketOS [[Partition_Layout|boot and root partitions]] by their label. We have to find partitions by their label, because we do 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 ({{issue|664|pmaports}}). | We used to rely on <code>/etc/fstab</code> to find the postmarketOS [[Partition_Layout|boot and root partitions]] by their label. We have to find partitions by their label, because we do 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 ({{issue|664|pmaports}}). | ||
Revision as of 14:37, 10 November 2020
This article is about /etc/fstab
in postmarketOS.
Usage in the boot process
We used to rely on /etc/fstab
to find the postmarketOS boot and root partitions by their label. We have to find partitions by their label, because we do 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
.