Change Details

This patch adds to makefs a new -r [read-only] command line switch. This option allows to manage the ffs superblock int8_t 'ronly' flag during fs creation. At the moment a mount / mount -o ro actively manages (toggle) the *on-disk-state* (!?) of the attribute, but ignores the existing state. And sys/ufs seems to mange a rdonly but not ronly to figure out the existing state. * Can we fix/switch this or is this a feature I don't get? * Who can help to untagle/understand the ufs rdonly <-> ronly situation? Having a real working os based immutable (not r/w re-mountable) ROM ufs/ffs protection for rootfs/bootfs partitions would be nice.

This patch adds to makefs a new -r [read-only] command line switch. This option allows to manage the ffs superblock int8_t 'ronly' flag during fs creation. At the moment a mount / mount -o ro actively manages (toggle) the *on-disk-state* (!?) of the attribute, but ignores the existing state. And sys/ufs seems to mange a rdonly but not ronly to figure out the existing state. * Can we fix/switch this or is this a feature I don't get? * Who can help me to untagle/understand the ufs rdonly <-> ronly situation? (mjg?) Having a real working os based immutable (not r/w re-mountable) ROM ufs/ffs protection for rootfs/bootfs partitions would be nice.

This patch adds to makefs a new -r [read-only] command line switch. This option allows to manage the ffs superblock int8_t 'ronly' flag during fs creation. At the moment a mount / mount -o ro actively manages (toggle) the *on-disk-state* (!?) of the attribute, but ignores the existing state. And sys/ufs seems to mange a rdonly but not ronly to figure out the existing state. * Can we fix/switch this or is this a feature I don't get? * Who can help me to untagle/understand the ufs rdonly <-> ronly situation? (mjg?) Having a real working os based immutable (not r/w re-mountable) ROM ufs/ffs protection for rootfs/bootfs partitions would be nice.