Speaking of!! I wanted to ask, what's the preferred way to make btrfs snapshots on bazzite?
Speaking of!! I wanted to ask, what's the preferred way to make btrfs snapshots on bazzite?
AAnd also wanted to ask what the limits of those snapshots are; like, say I totally fuck up everything about my install - WM and DE are fucked, errors everywhere, home folder is destroyed or some shit - would a btrfs snapshots be able to roll everything back to a previously working state?
AI asked a day or so ago and got no response :o
Gif I'm not mistaken they should be at around 3 partitions?
Pseparation of concerns
AAll I've got for bazzite is just the default handling of partitions on its drive, so
AA 990GB btrfs partition mounted at filesystem root
Pyour home folder probably isn't so critical, back that up however you please - you don't need to worry about backing the actual OS up with a btrfs snapshot to recover from an update because of ostree pinning
Ayou dont
Ayou use ostree to manage your deployments
Aand you can have as many as you want
ASay I try installing something myself that could lead to issues, what would be a good way to make a "backup" to roll back to with ostree, just in case I need to?
Acan you give an example of something you'd install
A/usr is locked
AI know a reinstallation is recommended for it, but say plasma-desktop using layering
Pyou can just pin your current deployment
ASay I try it out and attempt to debug it myself - or idk, say instead of layering I rebase into bazzite-plasma:stable - and try to fix the issues that arise myself. If I find that I can't fix them, I'd want to "roll back" to before I attempted the whole thing
SIf anyone else asks about 1Password and Firefox native messaging, I'd just link them to this and say it's coming soon
... I'm going to give up and just keep using the flatpak Firefox for now
... I'm going to give up and just keep using the flatpak Firefox for nowGitHub
This is an implementation of a slightly modified version of the interface proposed in #655 for starting WebExtensions native messaging servers on behalf of a confined web browser.
The main change ...
The main change ...
Ji have changed my computer resolution and it's now blackscreen in desktop mode, any idea how to change resolution
AId.. pin my current deployment, backup my home folder to another drive or something.. right? And if it totally fails or whatever, I'd rebase back to my pinned deployment and restore my home folder backup?
Pdon't even sweat your home folder
Pback it up if there's super important shit
Plike
Pi think you need a baseline understanding of how this works
AWell, switching from gnome to plasma can end up having issues within the home folder due to configs, iirc
AI've done this before on arch and nobara (and clear Linux but that's a diff story), but this time around Id like to be able to say "nah fuck this, this ain't working" and roll back
Pthe whole OS is booted from an image. if you change anything that would alter its immutable state, you need to rebuild this image. that leaves you with an old image and a new one. by default the OS is going to hold onto both in case your new image can't boot etc.
ASo that's kinda why I'm asking about btrfs snapshots and whatnot
Ji changed the resolution from the desktop mode setting app
Pyour home folder is basically just a wart on top of this step
Pwhether or not it exists is :shrug:
AFair enough, I get that; a lot of DE config files live there though, which is why I'd back it up, personally. That way I can roll back to how it was on gnome if I fuck it up
Pyeah you can also try making a new user if your old one fails to login etc.
Pbut your home folder is only gonna be touched after the OS already booted
Anod
Pif you're going from gnome>plasma that should probably not be too borked
Pi think worst case scenario there is rebase to plasma > potentially can't login > make new user
Ahmm.. sched_ext repo says
scx.servicescx_lavdcachyos devs: this service is shipped always you can rely on it
Ame (avg soystemd resistor): im not sure about that
Aso i guess bazzite doesn't have a systemd service for it yet?
Akyle did the packaging for it
Aand it took him multiple days
Aso maybe he ommitted it?
Aor is it just not there because im on stable?
Preddit to my ears
Akinda confused
AI just wanted to enable lavd without having to run
sudo scx_lavdWhat's the speed limiter of rpm-ostree changes and whatnot? like, what makes adding layers, topgrade, etc take so long? Is it CPU intensive? RW intensive? not sure how the underlying mechanisms work so dont really understand what's going on to make it take longer than something like arch or whatever
Ai know its loosely based on docker or git repos, but that's about all i understand
Anot that im trying to speed it up, im just curious is all
