You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently debos uses UUIDs for the /etc/fstab entries. However, in some cases when using an A/B system upgrade machanism this can lead to the problem that partitions can't be mounted on boot. See related issue for RAUC: rauc/rauc#1149
The image partition action should have an option to use either the label (LABEL=...) or the device name for the specific entry in the /etc/fstab.
The text was updated successfully, but these errors were encountered:
We could extend the filesystem-deploy action somewhat to add addtional properties. This could be something like fstab-mount-by: label with uuid as the default (current case).
But if "filesystem-deploy" is already executed, how can then the fstab file be created in ${ROOTDIR}?
Maybe you mean the other way round?
I would suggest to add the property to the image-partition action. The mountpoints are defined in image-partition and should be customized using other than UUID, e.g.
Currently debos uses UUIDs for the
/etc/fstab
entries. However, in some cases when using an A/B system upgrade machanism this can lead to the problem that partitions can't be mounted on boot. See related issue for RAUC: rauc/rauc#1149The image partition action should have an option to use either the label (
LABEL=...
) or the device name for the specific entry in the/etc/fstab
.The text was updated successfully, but these errors were encountered: