

If you can get their servers to connect to that IP under your control, you’ve earned it
If you can get their servers to connect to that IP under your control, you’ve earned it
Also codecs… even with the right repositories enabled, you’ll tend to install a media application that manages to be utterly incapable of actually processing most media.
They’ve made strides on this front but it’s still messed up.
Also sometimes they are too aggressive on one front. Some of the applications you can install from their repository that have some python based features are broken because they can’t handle python 3.13. There’s some ability to install python 3.12 but without much beyond the core making it less useful.
From what I’ve seen if an online store provides a 16 bit classic without a reimplementation, it’s bundled with dosbox.
Of course, I’m pretty much blanking on any classic Win16 titles of note. As far as I recall the significant games just kept being DOS games with at most launch from icon. I suppose original Myst because QuickTime, but they released a Win32 build. But this 16 bit stuff was a speculation, this is about the 32 bit stuff that isn’t reasonably accommodated without a 32 bit runtime and certain bits being at odds with Flatpak isolation architecture.
I’m not sure exactly what you expect of him?
It’s not a tantrum, just a statement of limitation. The primary reason for Bazzite to exist is to have a SteamOS-like Fedora. He mentions, in depth, how the ‘simple’ answer about using flatpak doesn’t work, because flatpak imposes isolation in ways that are incompatible with the use case.
His options seem to be to be “polite” and quiet right up until the change gets approved and implemented and only then yank the rug out from his community, or make the broader community know the implications of removed 32-bit userspace support.
This seems to be the whole point of soliciting feedback, to know what you are likely to break. It would be supremely odd if you make a proposal, solicit feedback, and call any mention of a bad consequence a ‘tantrum’ when that was the whole point of framing it as a proposal.
Seems like he needs either Steam to go 64-bit or for Fedora to keep 32-bit since flatpak can’t help and, presumably, he doesn’t want to try to take on the maintenance burden of trying to carry forward Fedora’s 32-bit rpms for the same reason Fedora is trying to get out of carrying them forward. Assuming the broad community decides Fedora 32-bit userspace is still needed, then it’s far less incremental work for Fedora to maintain along 64-bit than it is to independently add it back.
This sounds like a whole lot of convoluted bullshit to use Plex locally and “looking local” through VPN solutions when you could just roll a Jellyfin instance and do things a more straightforward way…
can’t even do video playback on VLC.
I remember back in the day when I downloaded the first divx file my K6-400 couldn’t smoothly play… I had been so used to thinking of that as a powerhouse coming from my Pentium 60, which was the first one I ran Linux on.
You can use one of a few ways to use the TPM to auto decrypt on boot without passphrase. Systemd cryptenroll is my favorite.
Because it says to do so?
Proxmox uses Debian as the OS and for several scenarios it says do Debian to get that done and just add the proxmox software. It’s managing qemu kvm on a deb managed kernel
Funny part is I’m responsible for some software which needs just a little privilege.
The direct install option runs as a broadly unprivileged user, thanks to systemd service for imparting one, surgical ambient capability to the process.
A team that wraps it in a container however demands it be run privileged, because they say the container runtimes dont support the same granularity, so the container users end up with unreasonable privileges while the direct install users are almost completely running unprivileged.
Maybe I could see that for Windows server. As more of that market moves to azure, the os matters less.
I’ve heard rumors that the dom0 equivalent in their azure virtualization platform is now Linux based. They still use an in house hypervisor, but may have moved to Linux as the management stack.
It’s a long shot, but if Microsoft were moving anything at all, it would be the server product given it actually struggles in market share.
On the desktop, they just don’t have much reason. They barely evolve the NT kernel so it doesn’t cost them a huge amount. The Linux approach to drivers would completely mess up their driver ecosystem. With the world of modern standby, windows pretty much gave up on long term suspend and instead hibernates, Linux refuses to even try to hibernate with secure boot. The features a Linux kernel brings to the table just do not matter to the windows desktop market. It would be a giant migration expense for no benefit compared to their current strategy of just hosting a Linux kernel as a virtualization guest.
I mean I would love to use a Linux oriented desktop management instead of Windows shell, but it’s abundantly clear that would be non negotiable for Microsoft, so I’d end up still stuck with my least favorite part of the windows experience even if the kernel were Linux
It depends on what you want to self host.
As an example, a family member self hosted home assistant. They didn’t have to know anything really. That was all they were doing and they bought the canned implementation.
If you have multiple services, you may need to know nginx configuration with virtual hosting.
You may want to use podman or docker or kubernetes.
It all depends …
Yep, and then have to opt out all over again the next week when an update decides you need to verify you really mean to opt out again…
And if you managed to not have an MS account when you installed, interrupt your login and say “you cannot proceed like you have been doing for the past year without adding an MS account now”, and then look up how to get out of that dialog without doing the MS account…
Basically when I open up an MSOffice file, if there’s anything vaguely complicated it will not look like the way the office user intended.
Yeah, but the O365 crowd is pretty much 99% tied to the cloud anyway they slice it (MS really wants you to work exclusively in OneDrive).
LibreOffice may be able to handle it’s own documents fine, but interoperate with an MS Office user and it frequently is unable to be consistent.
The main hiccup for hardware support is GPU support, and as a side effect of the bigger business being in messing with LLMs and that use case preferring Linux, GPUs are getting more Linux attention.
For example, nVidia drivers went years and years with a status quo of “screw open source, compile our driver and deal with the limitations”. Only after they got big in the datacenter did they finally start working towards being fully open in the kernel space (though firmware and user space still closed source, but that’s a bit more managable)
Yes, it’s only a fraction, but most of the rest is going to SaaS through web browsers or mobile apps, because companies get to control and force subscriptions that way, but has a side effect of targeting a browser as a platform rather than an OS. Gaming in browser is more in the pain point of browsers, so it’s a use case that demands OS.
Sadly, LibreOffice isn’t up to the task.
However, more and more this stuff is done in browser anyway.
It’s funny because while some of it has to do with work to make Linux desktops better, a non-trivial amount of it is how worse Microsoft has made it to deal with Windows.
Yeah, but it is hard to separate that, and it’s easy to get a bit resentful particularly when a projects quality declines in large part because they got lazy by duct taping in container registries instead of more carefully managing their project.
They will require the requester to prove they control the standard http(s) ports, which isn’t possible with any nat.
It won’t work for such users, but also wouldn’t enable any sort of false claims over a shared IP.