Hi,
Am Mittwoch, 16. September 2020, 16:01:45 CEST schrieb Bernd Nachtigall:
> Am 16.09.20 um 15:46 schrieb Thorsten Kukuk:
> (...)
> > Maybe you should define/explain at first what you understand under a
> > R/O System?
>
> Ah, sorry ...
>
> In my fluffy dreams a R/O (Read-Only) system is a host that acts like a
> normal one. But after a restart it has each time the same state. So you
> can save a file during the work but the system is like new after a restart.
>
> As a comfortable solution it could be possible to set a marker so that
> the next start is not R/O so is will be possible to updated the system
> (or do the basic configuration. Printer, proxy and so on). Afterwards
> the marker is removed.
>
> I had this years ago for the Rasbian-Distro.
>
> Is the read-only-root-fs @github useful for this?
MicroOS + read-only-root-fs-volatile might work for that, it redirects writes
into /etc and /var into tmpfs. There is no marker though, to write into /etc,
you can either do that in a transactional-update shell or umount -l /etc.
For /var, only umount -l.
I know that it's possible to have a overlay over the entire /, as that's what
kiwi uses for live cds and I've used that in some deployments some time ago,
but I don't think we have any package for that which would work on a regular
system.
Something like this instead of read-only-root-fs-volatile's mount-overlay.sh
might work:
#!/bin/sh
set -e
type getarg >/dev/null 2>&1 || . /lib/dracut-lib.sh
type det_fs >/dev/null 2>&1 || . /lib/fs-lib.sh
overlaydir="$(mktemp -d)"
mount -t tmpfs tmpfs "${overlaydir}"
mkdir "${overlaydir}"/{upper,work}
mount -t overlay overlay "${NEWROOT}" -o
"upperdir=${overlaydir}/upper,workdir=${overlaydir}/work,lowerdir=${NEWROOT}"
If it does, we could probably add something like that to read-only-root-fs.
Cheers,
Fabian
> Bernd
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
