Steam for Linux is the key app that blocked this recent Fedora change - https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.phoronix.com%2Fnews%2F...

Any of their OSes I can see on their https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fstore.steampowered.com... are using 64-bit.

I get old games makes it more difficult, but we need a 64-bit version of Steam to start making progress. They can still maintain old libs for those games in Steam itself (as they already do...)

You can actually get a Linux laptop from Lenovo for $553.70. That is the cheapest I've ever seen (with not totally horrible specs):
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.lenovo.com%2Fus%2Fen%2Fc...

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fairlied.blogspot.com%2F2...

"With the National Electric Vehicle Infrastructure (NEVI) Standards requiring that EV chargers conform to Open Charge Point Protocol (OCPP) 2.0.1 no later than February 28, 2024, it is urgent that charger manufacturers consider a standardized reference implementation that is OCPP 2.0.1 compatible such as EVerest. "

It's a shared implementation so everyone doesn't need to write their own.

Standards do help solve problems, but I've certainly had plenty of compatibility issues between different implementations of the same standard.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fbryanquigley.com%2Fposts...

tldr. Neither can take over the ecosystem in their current iterations.

Is having preinstalled keys at all. (I'm explicitly not basing MSFT for being the keysigner... that makes sense given the current design)

The assumption is captured in "It is further assumed that key material used for signing code by the OS vendor can reasonably be kept secure (via use of HSM, and similar, where secret key information never leaves the signing hardware) and does not require frequent roll-over."

I'd actually prefer the default be:
1. No Keys included in hardware by default
2. User or OEM manually does something to put device in Setup mode which allows them to install an OS. (It can just be going into BIOS and clicking a setup new OS boot option..).
3. That OS installs the keys it plans to use forever. (these could be from OS vendor or locally generated)
4. Setup mode is automatically disabled at next reboot/shutdown.

The idea that you can set one key in hardware and it shouldn't need to be updated just doesn't make sense to me.

There are a few more privacy options these days (but alas neither open source..) including:
  * https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fyou.com%2F
  * https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsearch.brave.com%2F

Systemd made Linux system administration much easier and nicer. Is it perfect? No. Is it 1000 times better than sysv scripts. Yes.

Avahi is awesome too!

PulseAudio I was never thrilled about, has some cool bits, but I'm not sad to see it slowly replaced by PipeWire.

I was curious to see how Ubuntu was going to approach a more rolling release strategy with *some* stability. Most approaches I've seen are just like what this project does - you are on dev always -that doesn't count as a "release" to me.

Currently Ubuntu has:
LTS releases - what most people use, cloud images are this, etc. Every 2 years.
"RR" regular releases - every 6 months, supported for 9 and generally thoughts of as a stepping stone to the next LTS.
Development, what will become the next release.

5 years ago I proposed moving Ubuntu RRs to a monthly cadence with a limit on what major updates should land each month (for example don't do a major kernel upgrade and mesa in the same month). The goal was to make a rolling release that set expectations for how much could break every month - giving a kind of stability. I still think it would be more useful then the current RRs - but it never went anywhere.

I always viewed "Year of the Linux desktop" as when Linux overtook Mac OS (or others) and become the 2nd most popular desktop/laptop OS. (Specifically to the point where we end up breaking out different distros)

In rough percentages - that's going from 1% to 10%. That would be a huge deal by itself.. it could:

  * Developers target Desktop Linux more
  * Those who provide services consider Linux (in airplane media, ISPs, etc)
  * Create more competition between distros.
  * More Linux pre-installed options.

on the wiki - https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwiki.pine64.org%2Fwiki%2FP...

IMU In the US we aren't even allowed to do research on how much energy/silicon is wasted on it.

  * It doesn't actually stop privacy.
  * It reduced consumer control of their devices.
  * It makes it harder to support devices longer term.

What distro?
What kernel version?
What init?

General bugs they ran into?
What could Linux/FOSS do better to be used for more space missions?

but I find docker itself overrated. I have also seen a lot of interest in many other container techs. Podman is open source - if it's awesome, I'm sure someone will bring it to other distros.

I prefer LXD*, but then again I work for Canonical. We actually just added VM support to LXD because people wanted one system to manage both (feel free to insert another conspiracy theory here) - https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fdiscuss.linuxcontainer....

Systemd has one of the best command line UIs of any software I've ever used. If anything replaces systemd in the future, it will be building on units in some way - definitely not be going back to shell scripts.

*I am aware it's targeted for a different kind of container user.

Someone was working on it... https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fgithub.com%2Falkhimey%2FAd...

If people try it with Ada or Rust or whatever and it's shown to be demonstrably better than C for some use case, more power to them.