doing a new temp install to nuke to double check because i was impatient, but thanks
doing a new temp install to nuke to double check because i was impatient, but thanks
WThat sounds like a good choice. regardless 
Vaaaand... fstab shows fedora atomic's defaults are / named "root", /home named "home", and /var named "var". that answers my question then. it doesn't have to be /var/home which seems weird to me. but i guess that's because /home just links to /var/home automatically?
Vwhen i did this last time i followed this, which tells you to make it /var/home
https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/WIt still says that you should use /var/home in the docs. Under Manual Partitioning. Maybe you can use both? Not sure
KDo I need to rebase to a signed image of Bazzite after rebasing to the unsigned image, just like all the other images?
KThe home page rebase command points out to an unsigned image
WI suspect that when you rebasing from Fedora you need the unsigned part because Bazzite isn't part of the official Fedora ecosystem. Once you are on Bazzite though you don't need the unsigned image anymore. I think that's why.... but I might be wrong
KI'm on ublue-os/kinoite so I'm on Ublue ecosystem
WKinoite is part of official Fedora atomic desktops, do you mean ublue-os/Aurora?
Kno, ublue-os/kinoite
WI didn't know that that was a thing 
. Then you should be good to leave unsigned part off and see if it works. If it's a problem it will fail quickly
. Then you should be good to leave unsigned part off and see if it works. If it's a problem it will fail quicklyKKand also this #
kinoite
kinoiteVrpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
Vi also believe they just added a ujust command to setup flatpacks after rebasing
Kyes, it is on the home page
Kso basically replace the
unverified-registryimage-signed:dockeryeah. rebase to an unsigned image. reboot. then rebase again to a signed image.
Kok, got it
FDoes bazzite choose the ssd automatically or hdd
Vyou manually select the drive in the installation like any fedora install
FI choose 2 drives which one will it install on?
Vdon't choose two drives
FWhy?
FDid it choose the hdd instead of ssd?
FCause of bigger storage on hdd?
Vchoosing multiple drives in the installer is for if you know what you're doing with manual partitioning with either advanced option
FAll i know installed the os on my hdd twice and it gave me blank screen on the second boot after installing apps
Then I'm uninstalled everything reinstalled the os and the proplem is still there nothing appears
Then I'm uninstalled everything reinstalled the os and the proplem is still there nothing appears
FI want to do auto partitioning
FThis is my build
Vwhat are your partitions on your drives?
Vare you running windows on your current ssd? are you trying to keep it if yes?
Vpeople don't have enough information to help you
Vif this is a desktop you can also just get another sata ssd, plop it in, and install bazzite on that
Vor m.2 if you have the open slots
FSo i had Linux mint on my ssd but i wanted to try bazzite installed it on hdd it worked but after i chose the apps i wanted and clicked reboot but then nothing appeared just this
FI have reinstalled it twice on the hdd
Then now i reinstalled it on the ssd where mint is after completely formating the disk
Then now i reinstalled it on the ssd where mint is after completely formating the disk
FBut then it happened again
FSecure boot is off tpm 2.0 is on
Vfirst setup of gaming mode in a -deck image takes a bit which happens after your first reboot
FHow much time does it take?
Valso depends on your internet connection speed
FWhat internet all i see is black screen how could it be using internet
FAfter it said welcome to bazzite i installed it then it said reboot i clicked open then it rebooted and then no output was on screen
RThree for three, I'd say this is reproducible. CPU and GPU load is basically zero. Any sort of logging I can do while my PC is in slideshow mode?
SLinuxiac
Lennart Poettering reveals run0 in systemd v256, a fresh take on secure privilege escalation, aiming to phase out traditional SUID binaries.
SSeems like Sudo is going away soon
NTbh, writing sudo is a lot more fun than writing run0...
NIdk why
Syou can always make an alias sudo to run run0 or have a symlink linking runo to sudo
