I'd be okay with that but there are some implications ...
I'd be okay with that but there are some implications ...
Abut I would like it if does not destroy the system
Aconceptually that should reset the system to default state
PYeah, in a future where things are more image based "native" I could see something along those lines being the case
PI do see a /usr/etc/passwd and /usr/etc/shadow etc, but there's no passwords for any accounts, so a little hard to log in if things got reset to that 
(unless there's something that goes through the first boot setup again or something?)
(unless there's something that goes through the first boot setup again or something?)Apretty sure your system is bricked
Aif you remove them
Ryeah those files under /usr are probably only there to fix file not found errors
Athere are actual defaults for these files, wonder why those aren't used
ARI could see a future state where /etc/shadow /etc/group /etc/passwd actually become directories which get -d
Athat cannot happen, it breaks POSIX
Asystemd has some sysusers thing tho
Rnot everything sticks to POSIX
Athe last 45 years or so of tooling assume that all your users are in /etc/passwd
Athis convention probably even predates POSIX
Athere's realistically no way we're going to change that imo
Athat's why even /etc/fstab doesn't change even though now it is used by systemd to generate mount units
Rand they write things like SSSD that tells it to find users in places that are not /etc/passwd etc
R¯\_(ツ)_/¯
Athat's for networked authentication and SSSD has an option to keep /etc/passwd in sync
RI believe one of the changes that RHEL was considering for their Identity Management was actually removing reference to so it doesn't even look locally for user auth
APff everyone's passwords are 
Back in my day, all passwords were stored plaintext, with the only protection being the root read permissions on the file.
Back in my day, all passwords were stored plaintext, with the only protection being the root read permissions on the file.
AIt definitely helped people who forgot their passwords.
J@hermmm heya I noticed the PR permission thing you mentioned here: https://github.com/ublue-os/startingpoint/pull/74 and looked to see if there was a setting but couldn't find one
Jalso noticed the github settings on startingpoint were still different from the others so I turned on needing approval for all PRs but also turned on the option for people to automerge when the approver says yes. Theoretically that should remove one round trip timezone wise.
JBut also noticed we weren't enforcing tests to pass so I turned those on, so we'll have to see what explodes but probably nothing.
N@j0rge where would i put an issue for this: https://discord.com/channels/232740312194351106/625653468262039563/1107168355993002025
NI just put it in startingpoint since that is what i was using
RI think I want to make an image with wezterm built in to it haha
Rit's a pity helix editor isn't packaged in an official rpm
AHere is the link to your ticket, for anyone reading:
https://github.com/ublue-os/startingpoint/issues/75
https://github.com/ublue-os/startingpoint/issues/75
GitHub
$ rpm-ostree upgrade note: automatic updates (stage) are enabled Pulling manifest: ostree-unverified-image:docker://ghcr.io/noahdotpy/myublue-gnome:latest Staging deployment... done error: Cleaning...
AThis doesn't appear to be any issue caused by uBlue. Have you tried googling that error message? Other ostree users may have encountered it.
AMaking custom images is very easy. I could guide you through it. But I thought wezterm was already on Flathub...
The link is https://flathub.org/apps/org.wezfurlong.wezterm
The link is https://flathub.org/apps/org.wezfurlong.wezterm
Flathub
A GPU-accelerated cross-platform terminal emulator and multiplexer
A@hermmm Were you watching Eurovision yesterday in the tub? I heard Sweden beat Finland. 
AFinland's song was really funny though. It should have won.
AYou can make a distrobox with Arch, install it from AUR and then export it to the host.
XYeah. I read on reddit that we got 84% of the popular vote though, so I'm just sayin fuck the jury and we won.
XIt's a shame Loreen got a win a second time with a much worse song.
XIg they want Eurovision in Sweden next year as it's also Abba's 50 year anniversary.
RI think I saw @j0rge do that in one of his videos 
Rit's on there, but the website will tell you it's only intended for people to have a first loo, because it doesn't allow some of the configuration
R
RSee the note on that section
RThe flatpak is provided primarily for ease of trying out wezterm with low commitment, and you are encouraged to use native packages for your system once you're ready to get the most out of wezterm.
AI agree, Loreen's song is the typical bland modern pop stuff. Your song was hilarious. And it won the people's vote. 
AOh okay, but perhaps they're talking about some rare functionality that you aren't using. Try it and see if it works. 
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call to spawn a shell that runs entirely unsandboxed. While the terminal GUI itself is sandboxed. So most terminals work perfectly in Flathub. If you really need it natively then I can help you get started with making a custom uBlue OS.
Terminals on Flathub are no big problem; they just need to be aware of Flatpak env and call to spawn a shell that runs entirely unsandboxed. While the terminal GUI itself is sandboxed. So most terminals work perfectly in Flathub. If you really need it natively then I can help you get started with making a custom uBlue OS.RWez does build rpms for each release hosted on GitHub, so I could just cheat by layering it. But since I am considering a build for work focused use with some other things, it wouldn't hurt to include Wezterm
RI asked about the packages on Matrix and a few minutes later he'd replaced Fedora35 with Fedora38 
AIf you're interested, GitHub (Microsoft) will build your OS images daily according to your specification and host it for free on the same container registry that uBlue uses. It involves forking https://github.com/ublue-os/startingpoint on GitHub, then set https://github.com/Arcitec/os/tree/firstboot-refactor as an extra remote and pull all of its changes (they'll be in the main repo later but for now you gotta do it manually). Edit: Those changes are merged so you only need the main repo now.
After you have that, I suggest creating a new branch called something unique, like , set that as your main branch in GitHub's repo settings.
Now just start editing to list the packages you want to include/exclude, and editing to configure your own "on-login package installer".
After you have that, I suggest creating a new branch called something unique, like , set that as your main branch in GitHub's repo settings.
Now just start editing to list the packages you want to include/exclude, and editing to configure your own "on-login package installer".
ROh, one thing I haven't tested on my uBlue install on my laptop earlier was the YubiKeys and U2F working for things like GDM and sudo. Does anyone use that?