It's still obscene how GPU prices rival mortgage payments but here we are lol
It's still obscene how GPU prices rival mortgage payments but here we are lol
Por a whole used car, for nv 
DOr like one car payments on a new one with zero down
DMy Volvo payments are like 1 GPU a month... I never thought about it that way before.
EI'm relieved I can't drive. Cars are expensive
DIt's great that you can avoid driving. I'm not sure if you're American or not, but where I live it's basically a necessity to get anywhere
DWe need way better public transport and more walkable cities
EIt's a near necessity in most of America and actually very inconvenient where I live now
EI use public transit and Uber and that works out... So long as I don't need to be anywhere on the mark
EI also have family that helps out
DI guess stuff like Uber Eats/Doordash/Instacart helps a bunch too
EIt actually does. I always hear about how expensive it is and then go shopping in person only to realize it's just as expensive minus the tip and small delivery fee I would have paid otherwise :/
ENow... Uber can be a hit or miss depending on the time of day
EI've seen crazy prices
EBut I digress. Don't want to get too far off topic here
FI like that yafti can be configurable from being a informational pop-up, selection prompt, 1st time installer or OS configurator
FWe plan to use yafti as an selection prompt or informational pop-up where notifications are not enough for BlueBuild's
Specifically, when maintainer decides to automatically remove the flatpak, so that users can get a pop-up with info on why it's removed & get a prompt if they want it removed or not
default-flatpaksSpecifically, when maintainer decides to automatically remove the flatpak, so that users can get a pop-up with info on why it's removed & get a prompt if they want it removed or not
Fwe considered Zenity also, but why reinvent the wheel with it when yafti exists
FThat's one aspect where I find yafti amazing
FThe scope of powerwash is not well defined in the issue imo.
https://github.com/ublue-os/main/issues/95
As can be noticed by latest comments.
It's either a full proper reset like Androids or it's just reset of some configs.
I prefer to go all in, as partial config reset is already possible to some extent.
https://github.com/ublue-os/main/issues/95
As can be noticed by latest comments.
It's either a full proper reset like Androids or it's just reset of some configs.
I prefer to go all in, as partial config reset is already possible to some extent.
GitHub
We should look at a functional equivalent of a ChromeOS "powerwash": https://support.google.com/chromebook/answer/183084?hl=en
FBut I'm looking forward to see that presentation, it's gonna be spicy heh
NI am storing state in gsettings make this type of functionality possible. Though, unless the python bindings get some love it might be a good idea to talk about rust... I would have went this direction if I knew how bad they have gotten ahead of time 
VFile location for flatpak:
Hkinda implemented this at work but i did it by just having a service remake the users homefolder at boot if it didnt exist, although our environment is a lot more predictable and 
/etc
KThats a Monster!
Hey Kyle, how are your temps on your 6900 XT Noctua Mod under full load? :D
Hey Kyle, how are your temps on your 6900 XT Noctua Mod under full load? :D
Jyeah someone needs to drive concensus
JI agree it's important but I have other things on my plate, maybe someone else can drive
EI'm thinking two features here, but let's start with one:
Powerwash would mimic the behavior of ChromeOS and rinse would just reset any dangling configuration in the home directory
Personally, I'm significantly more interested in a
As for
just powerwashjust rinsePowerwash would mimic the behavior of ChromeOS and rinse would just reset any dangling configuration in the home directory
Personally, I'm significantly more interested in a
powerwssh- We can wipe the contents of /home without ramification. All necessary configs will just be pulled from /etc. so that handles resetting home
- In an ideal world, we could just wipe /etc and /usr/etc would pick up the pieces, but that's far from the case. We need to determine what, following s fresh installation, is changed (and whether or not it's automated), pin those files, reset /etc, and restore the pinned files
As for
rinse.config
Bi wish if we could powerwash/factory reset without being able to boot into OS
Bkinda like windows can
Bwell in theory you could just remov whole /etc and replace it with one from image
EI still think a generic Ublue image with restoration utilities could be helpful. Either install it on a flash drive or a separate partition, boot into it, run
just powerwash
DuRestore
Band it woild be hard to achieve currently at least with seperate partition
DuFixit yourself
J
Jcolin sent me this
Jif someone has time to go dig in and see what you can find that'd be awesome, context:
JBTW on the build system side...I did a spike on this: https://gitlab.com/bootc-org/fedora-bootc/fedora-bootc-base
- it significantly reduces the "rpm-ostree/ostree stuff" for the "base image from scratch" flow and is way more "container native". It's just a rough draft so far, I haven't tried using it "in anger" like to build a desktop with or anything, but I'm much happer with this as a landing spot than what we have with the existing rpm-ostree YAML bits.
Dhttps://gitlab.com/bootc-org/fedora-bootc/fedora-bootc-base#adding-arbitrary-content-making-arbitrary-changes
this is interesting, so DNF is being used instead of rpm-ostree?
this is interesting, so DNF is being used instead of rpm-ostree?
RDNF being used in the "builder" container, which is regular Fedora
This is then packaged as an OCI archive somehow and copied to the scratch image
This is then packaged as an OCI archive somehow and copied to the scratch image
Bi can look into this but yea as far as i know he want to achieve the end in which you deploy oci image without any ostree bits at all
Bwhat im sitll waiting for is bootupd to be able to do any distro
Bi really want to be able to make some other distros not just fedora
EThe build rationale is really comprehensive: https://gitlab.com/bootc-org/fedora-bootc/fedora-bootc-base/-/blob/main/README-build-rationale.md?ref_type=heads
FResetting gsetting is also useful & something I do in my image
Blooking at the containerfile its quite genious and works based on fedora:40 image not some special rpm-ostree image
ELooking at the build scripts and it's brilliant
EThis reminds me of how we handle 
-base packages in Wolfi E(but obviously not as clean, but it can't be given they have to work with specs)
