-----Original Message----- From: Thorsten Kukuk <kukuk@suse.de> Sent: 15 September 2020 21:40 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] ReadOnly OS

On Mon, Sep 14, Bernd Nachtigall wrote:

...

Hi,

is there an image for an read-only openSUSE for a RasPi?

It's called MicroOS ;)

And you can download the image from https://en.opensuse.org/Portal:MicroOS#Based_on_Tumbleweed Cheers, Guillaume

Thorsten

-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG N�rnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi, On Wed, Sep 16, Bernd Nachtigall wrote:

Nearly perfect, but ...

a short look I found that this has to reinstall after a session to get 'read-only'.

Is this correct or is there a (simple) way to have a 'real' R/O System with overlayFS?

Maybe you should define/explain at first what you understand under a R/O System? Thorsten

Bernd

Am 16.09.20 um 08:07 schrieb Guillaume Gardet:

...

...

-----Original Message----- From: Thorsten Kukuk <kukuk@suse.de> Sent: 15 September 2020 21:40 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] ReadOnly OS

On Mon, Sep 14, Bernd Nachtigall wrote:

...

Hi,

is there an image for an read-only openSUSE for a RasPi?

It's called MicroOS ;)

And you can download the image from https://en.opensuse.org/Portal:MicroOS#Based_on_Tumbleweed

Cheers, Guillaume

...

Thorsten

-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG N�rnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

-- Es sprach der Fürst zum Herrn Kaplan: "Halt' Du sie dumm, ich halt sie arm!" -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org