That looks like a normal kernel to me. The mention of the surface is the hostname which comes from /etc/hostname.
Exactly how does it not work? Does the kernel even try to boot? Tried verbose mode?
You might need to regenerate your initramfs for the new hardware, I think on Fedora that's Dracut? That usually does include machine specific drivers that needs to be available during early boot, but just regenerating it should fix that.
Essentially, you won’t have to constantly switch between the Spotify app and your game to adjust volume, skip tracks, or pause your music.
Except literally none of these requires to even switch apps at all? That's what the notification tray is for. Swipe down hit pause swipe back up, easy.
No, the majority of the energy consumption is in the backlight.
If they want them unintrusive they could just bring back the good ol' notification ticker in the status bar. Zero space wasted by annoying notifications 99% of the time.
Having the web server be able to overwrite its own app code is such a good feature for security. Very safe. Only need a path traversal exploit to backdoor config.php!
IPv6 or IPv4?
A /3 of IPv4 for that price is impossible, that'd be 10% of the entire IPv4 space. A /29 (32-3) would be more reasonable but 1k for a block of 8 IPs would be a massive ripoff.
Doesn't make sense for IPv6 either, as that'd be exactly the global unicast range (2::/3), but makes sense they'd give you like a huge block in there, maybe a /32 as that's what they assign to an ISP. As an end user you usually get a /48.
The official open-source definition expects more freedoms that just being able to see the source: the whole point of having the source isn't transparency, it's freedom. Freedom to fork and modify. Freedom to adapt the code to fix it and make it work for your use case, and share those modifications.
This doesn't let you modify the code or share your modifications at all.
nothing that anybody outside of people selling dodgy romsets online are going to need to worry about
And Linux distro maintainers, Flatpak, and libretro and a lot of other projects that rely on repackaging or integrating the code in a bigger project.
Even NVIDIA has a more flexible license that at least lets distros bundle it in the repositories.
I want to love IPv6 but it's unfortunately still basically impossible to get good proper IPv6 in the first place.
At home I'm stuck with fairly broken 6rd that can't be hardware accelerated by my router and the MTU is like 1200 which is like 20% bandwidth overhead just for headers on the packets.
On the server side, OVH does have IPv6 but it's not routed, so the host have to pretend to have all the IPv6 addresses and the OVH routers will only accept like 8 of them in use before its NDP table is full, so assigning an IPv6 to every Docker container fails miserably.
IPv6's main problem is ISPs are so invested in NAT and IPv4 infrastructure they just won't support IPv6. Microsoft, Google and Apple need to team together and start requiring functional IPv6 to create user demand, because otherwise most users don't know about CGNAT and don't care. Everything needs to complain about bad IPv6 connectivity so users complain to ISPs and pressure them into fixing it.
Yep, and I'd guess there's probably a huge component of "it must be as easy as possible" because the primary target is selfhosters that don't really even want to learn how to set up Docker containers properly.
The AIO Docker image is an abomination. The other ones are slightly more sane but they still fundamentally mix code and data in the same folder so it's not trivial to just replace the app.
In Docker, the auto updater should be completely neutered, it's the wrong way to update the app.
The packages in the Arch repo are legit saner than the Docker version.
I would avoid AppImages and use Flatpak instead. They're pretty notorious for their lack of integration, and the author of AppImage is severely against progress and is actively sabotaging Wayland support in them which leads to other bad experiences on Wayland desktops. The shortcuts is merely the surface of the problems with AppImage.
I wouldn't give up so easily, just come back to it every now and then even if you spend most of your time on the Windows partition.
I would literally donate money directly to Valve if I could for all the good selfless work they're doing.
Their work on sponsoring DXVK, and Proton's development, their contributions to make the AMD drivers even more awesome, gamescope, they've been driving all the HDR and VR work on Linux, and now they're also getting even more hands on with Wayland through frog-protocols.
Meanwhile the others are either doing nothing at all except selling the games, or actively sabotaging Linux gaming and furthering Microsoft's monopoly like Epic Games is doing with their intrusive anti-cheat.
Being on Steam is being strongly pro-consumer and the first thing a developer not publishing on Steam does to me is make sure I'm very unlikely to buy their games because at least on Steam I know I won't get ripped off.
Couldn't care less about whiny developers complaining they make slightly less millions in sales for overpriced AAA games, and still impose their own launcher and shit because they only treat Steam like a store and nothing else. I pick what's good for the players not the developers. If they're unhappy there's dozens of indie developers in line to pick up the slack willing to make games I'm willing to pay for.
EDIT: And a couple hours later, Valve delivers once again: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/RIZSKIBDSLY4S5J2E2STNP5DH4XZGJMR/?sort=date