i was kinda thinking of tossing the steamdeck os on it but that might not be good idea?
i was kinda thinking of tossing the steamdeck os on it but that might not be good idea?
Si'm not gonna use it as a desktop os
Sthat's mac os for
Si mean the deck/HTPC image
KSteamOS is very tailored to the Steam Deck
Kbazzite-deck will do the same thing with more hardware support
Kyou can use that on your macbook
Kif you want KDE like SteamOS, install kinoite and then rebase to bazzite-deck
Sah ye
Si'm not too experienced with linux environments so it's alot of googling XD
Si like how the deck has summoned alot more user friendly guides
Sshould i uh.. install bazzite with the egpu connected or can i do the connection later? @KyleGospo
Sit is a thunderbolt connection
Sso a uncommon setup
K@sebaskitten doesn't matter when, i'd do after
Sah yeah
Sbefore apple upgraded the firmware on older macbooks if you booted a non mac os with a egpu selected
Sit would not only disable the igpu but also the dgpu and thus no display
K@EyeCantCU update, it's not plymouth
Kand it works fine in a TTY
EThat's interesting. I wonder what's causing issues though. Can experiment in a little bit
TNobara 39 is out today https://nobaraproject.org/category/changelog/
TInteresting changes implemented
MKyle helped out with a lot of the OLED Deck support components 
as well as with transitioning to some of the packages that Bazzite uses
as well as with transitioning to some of the packages that Bazzite usesELots of exciting stuff with session select over there. Will definitely have a look. GDM on the Deck GNOME image would be nice
Mits been working great now that GE got it all figured out. ChimeraOS will most likely start using that method as well
Mlots of trial and error to get there lol
Mits my first time having a package included in an OS which is pretty cool, it was a good way to learn the RPM packaging process as a total noob
SApparently BCM43602 does not work on Linux
S
_so I have a question. do you guys create a new container for every app you install? or just one for each distro you need?
Kreally depends, usually i'll have one box per distro for stuff I plan on keeping long-term
Kif it's a one-off thing like dependencies to compile something I'll spin up a new box
_that's what I figured, but I wanted to be sure there wasn't a good reason to do seperate containers for each app
_thanks!
Pschizoid-level paranoia? 
DIDK why bazzite is not known to a wider audience
_behold! my collection of containers that must absolutely not touch each other
Pnext step is separate physical machines for every application
Pthen when you're truly anonymous you start paying for hundreds of internet connections because you can't trust the vpn providers
J@_cryptagion if you were using a lot of untrusted code, then maybe it'd be a good idea to separate out those. A lot of it depends on whether you trust the app and its dependencies. Things would also be different were sandboxing a more "core" feature to apps on linux. I'd probably care less than I do currently if it were. I'm not really paranoid, but there sure is a lot of code developed by tons of people that could cause problems either on purpose on on accident. An accidental one woudl be an parameterized rm -rf that say evaluated to
rm -rf /home/user/ when it should have evaluated to rm -rf /home/user/path/to/app/fileintendedtoberemoved, but an untested combination of options led it to be that way.
Jthe container setup is more about logical seperation, not running untrusted code
Jif you really want that barrier then you'd use a vm
KIt's only like 6 months old from a user perspective
KStill lots of room to grow hopefully
KSpeaking of which we might actually hit 1K stars before new years
Jyour pulls
Joh that was wrong, sec
J
DI just wish these immutable distros don't grow to be PIA
Jpia?
