we still need to figure out user creation on boot, @akdev do you have an idea on how that works?
we still need to figure out user creation on boot, @akdev do you have an idea on how that works?
Jyeah also like 95% of people don't have to use the windows installer, so they can cheat, we're not afforded such a luxury.
NI mean the windows installer mostly works
Aonly gnome supports that
AIt’s set in the anaconda configuration
Gso does every other installer, it's just not good UX
AIt’s easy to enable in anaconda but without DE support the system is broken at the end
GI'd argue it's just as bad if not worse than anaconda
NIdk, the windows installer scales correctly most of the time lol where anaconda does not lmao
GKDE get's support soon, is there any way I could support it in sway?
AI’m not really sure how the DE support works
AI imagine there’s some script or something that gets called and you can hook into
Gbecause I could probably hack something together
GG
Gok, so it seems GDM is set to auto login by default, and gnome runs the initial setup depending on the username?
Bat the moment not yet but in future 100%(there are few details in the backend that need to be solved but soon 
. been watching this and testing periodically for a while now
. been watching this and testing periodically for a while nowJyeah that for sure won't work
Bquestion is does it support ostree not just OCI
Jbootc won't rando switch you to any distro, it needs to be designed with ostree and OCI in mind
Bok to explain image needs to be made with Ostree (which is fairly simple) hard part is pointing to kernel and bootloader which bootc simplifies but those parts are the parts that dont have 100% coverage outside of RPM world
AWe will be able to support other distros but right now bootc itself depends on rpm
Bwindows installer is probably the closest thing to best i can think off(and people dont like my opinion) its simple everything but what is actually needed is outside of the installer
Bi cant wait for that to get sorted.
AThe current windows installer is kinda terrible
AUnless you only count the part before it reboots for the first time
Bthats the installer before reboot
Bafter reboot is out of box experiance
AI count that as the installer as the whole thing because it takes like 30 mins and a bunch of questions after reboot
AIn a way I would consider the gnome first boot setup part of the installer as well
Bi dont installer is what installs the OS. just like i dont consider gnome first boot part of installer
Bto me those are seperated from installer
NYeah it's easy enough to understand, partitioning tools are a bit basic but they obv include only what the user needs
Band OOBE from windows is just sad
Nmostly useless yea
Nit has fun animations though lol
Byou realy dont need much for windows drive partitioning, they could have an automatic one but this does the job just as well as its ment to be used by someone who knows what they are doing
AFor example if gnome first boot experience doesn’t run the system is unusable
Ahence at that point to me the OS is half installed
Bwell its still not part of installer it may be part of the experiance but not installer itself
BOS is installed whether you finish OOBE(or gnome first boot) but its not configured
AI mean you could say the system is installed after the rootfs is unpacked by that logic
Bto me they are 2 seperate parts and i treat them as such
Bthey are clearly 2 seperate components
AThey’re two separate components but parts of the same process
Acleaned up mkociso and made it an independent tool, two features I want to add:
supportboot_menu.yml- Custom boot params from boot_menu.yml
- Custom Lorax template support
WJust testing the OBS Studio container image again. Sadly I am still see this:
KHi, what command did you use to create the container?
Wdistrobox create --image ghcr.io/ublue-os/obs-studio-portable:latest --name obs-portable --pullAnd then ran
/opt/obs-portable/obs-portableAny objection to a pull-request that creates the required
/opt/obs-portable/config