Tried running #linux #tails operating system off a #bootable #usb .
#distro seems to work nicely. It entirely disappears on shutdown due to
being in RAM only. But then the OS needs all settings and configuration
set afresh on next restart.
What about if I run a #nixOS #container #vm #virtalmachine #virtualize
inside Tails then I could maybe use my #configurationdotnix after each
reboot to save manually reconfiguring after each reboot. What is the
best way of doing this? Tips welcome. Thanks!
Not to mention that OS/1337 should really excel with #transparency and #reproduceability in that the first #release should be completely possible to #DIY from scratch by running a single #bash script that yoinks said sourcecodes, .config files and in the end spits out a working & #bootable #1440kB 3,5" #FDD image.
Nothing fancy but something useable - even if it's just a #dropbear #SSH #Client (aka. #dbclient) and the basic #toybox tools to get #IPv4 connectivity.
And yes, #complexity is #cost. https://www.youtube.com/watch?v=SGmtP5Lg_t0&t=2882s
Ideally the OS/1337 distro sources is just a bunch of #bash #scripts and #config files that pull #sourcecode and compile binaries and shove stuff together...
https://github.com/OS-1337/OS1337
Because that's what maintaining that #distro is about:
Do the minimum amount of work necessary to make some #bootable #distribution that is useable.
Even if it's just to #SSH into stuff...
@britt that's because #EpicGames specifically went out of their way to more or les #ban the #SteamDeck's hardware so even if you force #Windows on it you'll get the middle finger by them to the point that you'll be forced to play a #Web version...
It's just blatant assholeism by #TimSweeney...
Nothing prevents him to literally sell a #bootable #MicroSD-#ROM with #fortnite on it,
I mean I've seen more absurd shit in the 7th console generation:
https://www.youtube.com/watch?v=ZvP2BOnZjGM
https://www.gamespot.com/articles/how-to-play-fortnite-on-steam-deck/1100-6503402/
