Dont hold your breath. It’s just initial support. It’s still opt-in and I can’t see Valve using it with Proton by default unless they start supporting native Wayland clients in Gamescope
Remarkable eink tablets. Buried deep in the settings they actually give you the root password so you can SSH in. Also, it comes with an epic .vimrc file.
Kindles too. You can jailbreak them and get a shell. They’re so much more useful when they’re jailbroken. They can read multiple other formats, they can get books from a fileserver on your local network, the jailbroken reader app is better, etc.
Only in the licensing space in particular there is really no good reason to hide the exact rules what is acceptable and what isn’t. Nobody is going to circumvent your defences if they know exactly which licenses you allow.
i think they are already mentioning it: MS has a help webpage on how to install linux, both WSL2 on Windows machine, or how to burn iso and install linux on bare metal. learn.microsoft.com/en-us/linux/install
Microsoft have quite a bit of software that runs on Linux (PowerShell, VS Code, .NET, Azure tools, Intune / Endpoint Manager, even SQL Server) so it’s understandable that they’d have documentation to explain it to their customers.
Yep, they run it themselves even. Previously their motto was “Linux is a Cancer” now they have embraced it and developed their own distro (CBL). With how everything is going WebApp these days, I can see a day when Windows will be linux based kernel.
They already have a Windows version for a handheld. The Xbox runs a modified version of Windows 11. All they’d need to do to bring it in line with PC handhelds is allow the install of third party launchers (they probably wouldn’t do this though).
Opening the connections is one thing but resends and stream ordering can also cause issues since they might delay the latest information reaching the user space application even if the packet for them has actually arrived just because some earlier packet has not. There can also be issues with implementations waiting for enough data to be available before sending a packet.
If your connection is stable, the latency will more or less be the same, but TCP will consume more bandwidth because of acknowledgement packets, making it harder to keep your connection stable.
On an unstable connection, TCP latency will skyrocket as it resends packets, while UDP will just drop those packets unless the game engine has its own way of resending them. Most engines have that, but they only do it for data that is marked as “important”. For example using an item is important, but the position of your character probably isn’t, because it’ll be updated on the next tick anyway.
OpenSUSE Tumbleweed has been my desktop home for the last year. It’s very up to date, yet it’s somehow solid and reliable despite sometimes receiving hundreds of updates per week. And if anything goes wrong with an update you can easily roll back to a BTRFS snapshot. It has a good repository supplemented by Flatpaks, and I haven’t had any problems finding software, yet it’s not a hassle like some other cutting-edge distros. It uses KDE Plasma by default, which I consider a plus. I came to it from Mint, which was my go-to distro for a long time, but I enjoy Tumbleweed more for its up-to-dateness and configurability, and I have (surprisingly) encountered more software gaps on Mint.
I have spent 3 days trying to install 64bit Linux on a mini PC which has 32bit UEFI. The funny thing is that this device is so slow probably I will not use it, but I still want to make it work.
It is a ViewSonic, but I don’t know the model. I have it’s PCB and power supply only. CPU is Intel Atom x5-Z8350. Btw I have already installed Linux on it, was a really good feeling, now it is collecting dust on the shelf :D
That KDE Plasma 5 is finally usable and stable, after having decided to stop pushing the ridiculous plasmoids on the user […] is like having an old whore finally becoming a respectable woman.
Initial benchmarks show better performance than btrfs (at least for some workloads), but more importanty, I like that it offers tiered/cache storage - so you can use a fast and small drive (NVMe) to speed up a slow and bigger drive (HDD). You can do that with ZFS as well of course, but it doesn’t have the massive RAM requirements. Also it’s much more easier to set up and configure in comparison.
BTRFS is honestly really great and has been for the last few years. Dont take the word of random people on the interwebs, check out some modern sources of info on the subject. Some people love to complain about RAID5/6 but if you use BTRFS the BTRFS way then it is solid.
With that said, if you dont need snapshots, drive mirroring, sub volumes, bit rot protection etc then EXT4 is hard to beat for reliability.
If you want to game, stick to regular Fedora. A project that is actually secure is ublue with dedicated NVIDIA images that should just work and never break, and they even have Bazzite, an Image specifically for the Steamdeck but also for Desktop.
These images are only ½ day behind upstream, apply minimal additions and patches (like drivers, codecs, packages, udev rules for controllers) and Nick from the video above found out that the Nobara patches with their weird less supported Kernel arent really worth the hassle.
I 100% agree, its best to just stick to upstream Fedora imo. Glad you made this comment. The security issues of Nobara always put me off, especially since basically everything it does can just be applied to regular Fedora. I think Nobara would much better serve as a script or toolkit, similar to Brace, or something along those lines instead of an entire separate OS with the security issues it brings.
Proprietary UEFI BIOS is, but for a secure system with local manipulation prevention it can be needed. Also secureboot is a security measurement against malware so no, its simply the best we have.
Look at Coreboot if you want a secure modern system
The vulnerability actually isn’t in Windows Boot Manager, it’s a flaw in the image-parsing code of the UEFI itself. That’s why it’s able to bypass SecureBoot.
It just happens that for whatever reason you can easily update the image file from within Windows/Linux itself. The fact they don’t show a logo currently does not mean you’re immune, as the system might just be showing a black screen at that point. Code can be injected into an image file without perceptibly affecting the image output, so you’d likely be able to use a “black screen” logo. If your computer has a UEFI instead of a BIOS, which is pretty much everything from the last 10yrs, then you are more than likely at risk.
My computer likely isn’t susceptible, and that’s because it’s a Dell workstation. While the bug still exists in the image parser, Dell has locked things down so it’s pretty much impossible to change the boot logo from userspace.
In my freshman year of computer science our main computer lab was filled with Sage IV machines. Basically a Motorola 68k series with 4 or 5 serial terminals. Most people were writing Pascal code or using a simple word processor. But god forbid you were on there with someone taking assembly language. Because they could write really stupid code with super tight loops that never allowed any other code to run, and the only thing you could do was reboot. So if you hadn’t saved your code you were fucked.
So I never purposely wrote really bad code that would overwrite unprotected shared memory with random quotes from Marvin from HHGTG to mess with other people. I would never do that. That would have been unethical and shit… 🤔
I did learn a lot of basic hardware and operating systems though so there’s that.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.