ostree pinning
While an ostree is pinned, such as 0, will 1 still be updated, when a new version is released or will 0 be updated since it’s pinned?
If something breaks while on 0, I can rollback to 1. If I do, is it correct that home directory is untouched?
12 Replies
the pinned one will be frozen in time. it'll be kept separate from the usual current and previous deployments
0 is the default
if you pin 0 and update it will become 2
if you update without pinning, the image you update from will become 1. So if you boot 0 and update 0 will become 1 and 1 will be thrown away
if you boot 1 and update it will remain as 1 and 0 will be replaced
home directory is common. /etc is copied from the image you update from
Home directory is common. I’m not sure I understand the meaning of it being common. /etc is copied from the image, means everything in /etc gets overwritten or changed up image version changes?
In /etc, only files that differ (you modified) won't be overwritten
Ah that’s nice to know! And what does “home directory is common” mean?
Its outside the ostree system
All pins share the same home
You've only got one
Oh! Thank you!!! That makes sense! So that’s why Pika Backup is the solution, restoring your home directory from backup, would back up your settings!
If you make a mistake in a directory within home, that you can’t figure out, restore from pika backup would resolve the issue!
That also makes sense why I changed to a different ostree, but the issue remained, because the issue was somewhere inside the /home directory!
@Kyle Gospo @Zeglius @antheas @termdisc (Deck+PC) thank you so much for the assist! I’m really loving Bazzite! It’s so foreign to a windows user, and yet so beautiful somehow! It’s hard to describe!
So I'm gonna put it in simple terms.
/usr is read only part of the image /etc is the writable part of the image. /var is writable and not managed by the imageThank you! So last question, what is best practice for keeping an ostree pinned? How long would you keep one pinned and when would you unpin it and pin a new one?
you only need to pin if you need a specific image
pinning nothing means you're on latest
and the last one (presumably a good one should an update break something) is always available as ostree 1
which you can pin should you confirm it works
Ah, so if you unpin you’re always on the latest, which is 0, and if the latest update breaks, you go to the last working instance, 1, and pin it so you don’t keep going back to 0, until the most recent update gets fixed?
pin it so it's not lost
because updates will still ratchet up, with a new update becoming ostree 0 and ostree 0 becoming ostree 1
if the new update is also broken and you didn't pin the previous 1, you now have no working images
it's a lot of ifs, basically pin when something breaks
and don't worry about it if it's working
not really different from windows restore points