On Tuesday, 18 July 2017 at 21:43, Colin Walters wrote:
On Tue, Jul 18, 2017, at 02:58 PM, Chris Murphy wrote:
> > But if I've understood correctly, any changes to the base will be
> > when you update the base image. right?
No; `rpm-ostree install` is persistent, and so are other changes like
`rpm-ostree initramfs --enable` and so is the recently added `ex override`:
A bit more information about layering and live changes:
What Chris is talking about is `ostree admin unlock` which is *designed*
to go away after reboot:
> I'm not sure what the long term plan is. Right now changes to /usr
> (normally read only)
It's more that rpm-ostree is the *sole* tool that mutates /usr; every
change is an atomic, interrupt-able transaction queued for the next boot
by default (unless one invokes `ex livefs`): Even local RPM installation:
(How did it work if /usr stays read-only the entire time? It's
because rpm-ostree knows how to go
"underneath" the mount, which really comes from /sysroot)
Big picture, as it says on github, rpm-ostree aims to be a full
hybrid image/package system, also supporting both offline updates
*and* online updates if you want that - anything that is "you can't do
is a bug.
This is very cool! Is this documented somewhere public? If not, it'd
make a great Fedora Magazine article. Please write one!
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"