5 ms·
The Arch Linux team is now working directly with Valve
- exar0815 2y ago"In the long-term, the funding touted should, at minimum, allow Arch Linux to improve the security of its distribution and provide more structured releases compared to its current near-continuous update cycle." Isn't rolling release one of the core ideas behind arch? Sounds like the usual gaming journalism...
- deleted 2y ago[deleted]
- alias_neo 2y agoYes, and it's also one of the features Steam likely wants, given all of the work they're doing upstream, they'll want those changes ASAP.
- daghamm 2y agoDid gentoo have any similar collaborations with Google? (Chromeos is based on gentoo)
- dijit 2y agoYeah, and chromeos is more than just the chromeos used on chromebooks, it's also the Container-Runtime Optimised OS (CROS) and used for some other things too, it's "the google Linux". I'd be speculating but I think inside google there's two Linux's, one which is the immutable OS built via blaze, more like an appliance, and the other is the "dynamic" user environment stuff based on Debian, that is intended largely to be throwaway in most circumstances. [0]: https://cloud.google.com/container-optimized-os/docs https://cloud.google.com/container-optimized-os/docs
- teruakohatu 2y ago> While Valve's specific reasons for picking Arch Linux for Steam Deck remain unknown, it's pretty easy to guess why it was picked. Mainly, it's a particularly lightweight distribution maintained since March 2002, which lends itself well to gaming with minimal performance overhead. A more intensive Linux distribution may not have been the ideal base for SteamOS 3, which is targeted at handhelds like Steam Deck first. I am not sure Arch is going to be faster for gaming than any other distro, but I can see why Valve picked it for a minimalist base. Another reason I am sure they picked it is that it is smaller and less commercial than others (such as Debain or Ubuntu) and they would have more ability to influence the project. > In the long-term, the funding touted should, at minimum, allow Arch Linux to improve the security of its distribution and provide more structured releases compared to its current near-continuous update cycle. This was literally the stated reason they moved from Debian in 2021, because they preferred rolling releases. [1] [1] https://www.rockpapershotgun.com/heres-why-steamos-switched-from-debian-to-arch-linux https://www.rockpapershotgun.com/heres-why-steamos-switched-...
- night862 2y agoAbout releases: They typically refer to the OS version or base in these rolling distros such as Fedora. Rolling releases aren't all like Sid. In Fedora, there is a base OS version with a sort of configuration, specif directory structure, major architectural versions of software (like Gnome or KDE), sometimes cryptographic policy, or other system backends such as logging or DNS resolution. Fedora used its release cycle to migrate to systemd-resolved, to pick an example, because this change introduced structural changes to the way the system operated. In the release in question, system services leverage the D-Bus API to get DNS lookups, systemd binds to the local port. By segregating this behavior by release, it makes the dependency tree much simpler to manage at the cost of possibly needing to backport patches, but Distributions are doing much more than shipping mostly upstream packages like Arch is. I always thought arch would be well suited to this sort of thing. Arch Build System is very good, and since packages are very close to upstream, it would be very easy to make your own ABS repo as it stands. It is very similar to the ports tree, arch linux has very little flavor in many respects.
- 2y ago
- guerrilla 2y agoI'm glad I started looking at other distributions like Alpine recently. This could just as well have negative effects as positive ones. Time for me to diversify.
- wao0uuno 2y agoWhat negative effects are you afraid of? I really can not see any downsides to this partnership.
- guerrilla 2y agoIn the long-run, a project can become dependent on such donations and this can give donors power over the project and those donors may want to steer the project in ways that we don't want to see it go. That may not happen and may even be unlikely but it's important to be prepared for that possibility and have contingencies available. There is already a comment here which discusses one such scenario: https://news.ycombinator.com/reply?id=41695062&goto=item%3Fid%3D41694283%2341695062 https://news.ycombinator.com/reply?id=41695062&goto=item%3Fi...
- wao0uuno 2y agoMaybe I’m being naive but I trust Valve to not fuck this up. They already make their money selling games so they will not try to turn Linux into a product. What they actually want is to make Linux better for everyone so they can reduce their dependency on Microsoft. I guess we’ll see what happens next.
- ribcage 2y agoSteam sells software and prevents you from copying it and using it easily. Not something you want to happen to a Linux distribution.
- tambre 2y agoUsage of Steam's DRM is actually optional. There are plenty of games that you can copy the files of and run on another system without Steam present. [0] [0] https://www.pcgamingwiki.com/wiki/The_big_list_of_DRM-free_games_on_Steam https://www.pcgamingwiki.com/wiki/The_big_list_of_DRM-free_g...
- NoboruWataya 2y ago> In the long-term, the funding touted should, at minimum, allow Arch Linux to improve the security of its distribution and provide more structured releases compared to its current near-continuous update cycle. This is a weird point, and concerning if it is true, because it seems to assume Arch's rolling release model is a bad model that the Arch team are forced into due to lack of funds, whereas for most of us it is in fact one of the main reasons to use Arch. As another commenter mentioned, the rolling release model is one of the reasons why Valve chose Arch, so hopefully this comment in the article is just misinformed. But there is a concern IMO that once Arch starts to look how Valve want it to look, they will try and influence the project to move to a more Debian-like release model (so that they have to worry less about breaking changes). Of course whether they can successfully influence the project in that way is another thing.
- westpfelia 2y agoI thought one of the big things Valve wants to implement is a more sound CI/CD pipeline. And I assume at some point maybe have some sort of more unified app (store). I know people love AUR. But one thing that plagues linux is the flatpak/snap/app-get/dnf/aur dance. Getting something more unified (at least for 'casuals') would be good.
- Foxboron 2y ago> This is a weird point, and concerning if it is true, because it seems to assume Arch's rolling release model is a bad model that the Arch team are forced into due to lack of funds, whereas for most of us it is in fact one of the main reasons to use Arch. This is reading too much into it. The issue is that things like proper build infrastructure and signing enclaves is hard work that is not easy to work out and provide on a volunteer basis. We (Arch) do not support multiple architectures for the simple reason that it would imply I'd need to watch N number of builds of one package pr architecture. This is what we did for the 32bit version and 64bit version. That's a lot of wasted time, and doesn't help you sell architecture support. Signing enclave is hard to do right as it requires the technical know-how to do securely and the supported tooling to move the package signing from a pr developer basis to a central signing key. In the long run this would also enable Arch to support Secure Boot.
- marcodiego 2y agoNo other OS is as configurable, adaptable and versatile as Linux. It runs on the biggest super-computers, on the helicopter that flew on Mars, on the server that is hosting this service and on the device I'm typing just now. Now, just imagine... just imagine how much performance could be gained if game vendors didn't ignore it.
- preisschild 2y agoAnd now Real-Time support is getting mainlined, which means we might see even more stuff like Mars Rovers running Linux.
- squarefoot 2y agoWhat did mainlining it change from the industry point of view? I recall installing in minutes the -rt fork from official Debian repositories ages ago, mainly to have lower/more consistent latency with music apps, and never had a problem.
- fermuch 2y agoOfficial support, and more eyes seeing it. Maybe better integration since they'll need to make it integrate fully to reach mainstream kernel.
- dietr1ch 2y agoAnd the RT patches are making it to upstream, which together with the userland sched can make a huge difference in frame rates and latency when gaming.
- BlarfMcFlarf 2y agoI doubt they wanna run an RT kernel in SteamOS. There are severe costs to doing so.
- the8472 2y ago
- moomin 2y agoSeen from a certain angle, the real question is: why don’t more companies do this? This isn’t charity, this is enlightened self interest paired with understanding that pissing off your free supplier is a bad idea.
- high_na_euv 2y ago>why don’t more companies do this? What exactly? Whole big tech contributes to linux. MSFT is probably biggest of them
- josefx 2y agoWasn't Microsofts biggest Linux contribution the code to make it run on Microsofts Hyper-V ? From what I understand their only other major contribution is the Rust project that ran head long into a wall.
- BSDobelix 2y agoJup it's crazy that people still think Microsoft (the "We Love Linux initiative") did anything big apart from let Linux run good on their Hypervisor, Oracle for example did 100x more then MS (yes oracle...).
- OliveMate 2y agoI'd say half of it comes down to Valve having the staff with the key knowledge and skills to provide support, and the other half comes down to not being public. I'm sure many devs and publishers are filled with people who know that acts like this can garner trust and future support for their company, but will have efforts cut short because someone above complained that the line didn't immediately go up.
- StableAlkyne 2y ago> the other half comes down to not being public In every service or product I've bought, going public (and prep to go public) has preceeded a decline in quality. The day Valve goes public will be the day its downward trend starts, because its customers become the shareholders.
- sph 2y agoI'm still hoping to see an official immutable version of Arch Linux. SteamOS is immutable, and I'm "stuck" using Fedora Silverblue [1] because immutable is the future and I won't go back to installing stuff manually while cruft accumulates in system directories. I don't interact often with rpm, but I hate them with a passion, while I used to maintain multiple Archlinux packages as it was so easy to do. 1: Silverblue host, but working within an Arch Linux container with Emacs, of course. Imagine having to maintain all the five dozen LSP servers and dev tools without access to the AUR.
- StableAlkyne 2y agoI'm still curious about why they picked Arch over Debian or a BSD. The article claims it's because Arch is "lightweight," but then why not pick a smaller distro? My best guess would be familiarity (Valve can afford to buy the best developers, and lots of great folks enjoy the fiddlyness of Arch), hackability, and insanely fantastic documentation of Arch
- kkfx 2y agoI wonder why Arch as well, because it's a rolling distro so a terrible model for a commercial/production product/service, but why no *BSD is easy: bad modern hw support, Debian because of a rock solid base but extremely old distro with many issues especially in customizing it (I'm serious D/I and preseed are HORRIFIC). So I wonder why not NixOS since it's safe updates (an update essentially can't break anything, not necessarily true for database etc outside Nix but still much saver than any other non-declarative distro) and effortless rollbacks, customization etc. It's community is problematic right now, but it's still the most complete modern distro we have, with Guix due to the GNU design a bit behind and all the others FAR behind.
- mmis1000 2y agoSteam does a lot of upstream graphic/proton works. A distro like debian that update once a year is going to be a bad idea. It means a fix in graphic stack or proton will either, 1. deliver after a whole year, and get actually feedback after two years. 2. require a lot of backport so steam can actually use it. Rolling update in the other end, suits well with the changing nature of graphic stacks.
- kbolino 2y agoBSDs are off the table because Proton, the set of extensions to Wine for playing video games, uses Linux-specific system calls. Also, the major graphics hardware vendors don't release their first-party drivers for anything other than Windows and Linux. While open source drivers exist, they are not good enough for the latest games or the latest hardware.
- 2y ago
- kkfx 2y agoWell... Arch community is very kind and very active, but Arch is a rolling distro, a paradigm essentially incompatible with stable production systems. I wonder why not choosing NixOS or a custom Guix System (due to the non-free stuff) instead since their model offer effortless rollbacks and safe updates.
- alias_neo 2y agoValve could offer their own device snapshotting/versioning, and frankly it may not even be a real issue since the device can just be reinstalled with the "factory image" at worst. They have been putting a lot of work into upstream packages to provide the Proton compatibility, and they'll likely want to keep getting those packages into users hands as quickly as possible. For fast moving development in this space, it makes sense to have a base of packages that aren't outdated right out of the gate.
- kkfx 2y agoReinstalling from images is resource intensive and take time and bandwidth than a simple "reboot into the old verision", while with NixOS all they need is provide their own channel. On Arch they could provide their own repos as well, of course, but a thing is keeping some derivations in sync, testing them etc, another is keeping a classic distro "de-facto semi-fork", it's again an order of magnitude more complex, resource intensive and time consuming. It's much simpler and faster a declarative ecosystem and developing with it then the classic model, astonishingly faster and simpler. I know many have never tried so do not know, but the IT at Valve I expect should be a bit beyond "the many who have never tried", so well, just curious why.
- alias_neo 2y agoI understand where you're coming from, I love NixOS and it seems like it could be well suited in a way, but it is extremely complex to learn Nix, and it doesn't have the scale or support Arch does, on top of being a massive departure from the typical distro and I think Valve want the Steam Deck to be a straight up portable PC. Being pragmatic about it, I just don't think NixOS was ever a contender.
- deleted 2y ago[deleted]
- frankjr 2y ago> Valve is now providing a build service infrastructure Fingers crossed this means Arch will support the ARM architecture* in the official repositories. There's a related RFC which has been accepted but but I'm not sure where things stand right now. https://rfc.archlinux.page/0032-arch-linux-ports/ https://rfc.archlinux.page/0032-arch-linux-ports/ * I'm well aware of Arch Linux ARM but that's a separate project with even less resources (missing packages, some broken). Asahi used to use it before moving to Fedora due to similar problems.
- Foxboron 2y ago> Fingers crossed this means Arch will support the ARM architecture* in the official repositories. There's a related RFC which has been accepted but but I'm not sure where things stand right now. That is the goal with the work they are sponsoring, yes.
- shkhuz 2y agoIf I'm not mistaken, Arch Linux only supports x64 (excluding the unofficial ARM port), so I wonder why they've chosen to go with it rather than Fedora or Debian.
- alias_neo 2y agoMy guess: Fedora is in the tight grasp of RedHat, and Debian perpetually ships old packages. Steam/Valve are doing lots of work on various parts of the stack upstream, that they'll want to get hold of as quick as possible and not be limited by outdated dependencies.