Even having no pre-boot PIN with SB on is nice, then you only need your user space login where you could even use fingerprint reader if you like. For servers they can already start serving without anyone having to intervene manually (which is nice after power outage, for example).
So yeah, SB, TPM and FDE are a very nice bundle that heavily secures against the most relevant attack vectors.
For the user they come with the OS
That’s my point, though. Plasma isn’t an OS. You can can have a OS that ships Plasma with Calligra instead of LibreOffice and Falkon instead of Firefox. Or neither, and instead they give you a greeter with the choice to pick your browser. Or the OS is minimal and doesn’t bundle any of them. In Arch for example you normally don’t even get Konsole or Dolphin unless you install them (or you pick the nuclear option and install _all _ KDE packages which also includes a ton of stuff you likely never need).
AUR is the place for unverified submissions. The verified stuff typically ends up in the main repos.
The preinstalled apps are not a feature of KDE (or Gnome, XFCE, etc.). Actually they all are structured in a very modular way where you can use or omit individual components. Firefox and LibreOffice are completely independent of it even; they merely add compatibility layers to make the integration more seamless.
What you experienced was something to attribute to the distribution you chose. They are the ones to decide which components to bundle and preinstall. That is also the reason why so many distributions exist in the first place, because different teams/devs have different visions about what the desktop should look and feel like after install.
I think you won’t regret it. If the container startup installs stuff, you might lock yourself out when the remote server has issues, your network has issues, or if the package you install changes due to an update.
With it baked into an image, you have reproducible results. If you build a new image and it doesn’t work anymore, you can immediately switch back to the old one and figure out the issue without pressure.
So you would expect the devs to include a filterlist for known bad packages in different potential source stores that they have no influence over? How would you distribute that? Bundled with Discover, in which case the package maintainers of the different distributions have to roll out new versions with the updated list? Or as a list maintained on some server the KDE team has to provide, which gets updated by Discover automatically on startup? What if you don’t condone their decision to block something? What if the list gets abused? What should companies do that want that list customized?
The idiomatic way would be to build your own image. That’s exactly the strength of the layering of container images.
The thread is about snap and why it’s worse than flatpak.
Nvidia rightfully earned their bad reputation on linux,
Really? IMO not with GPUs. They have released linux drivers for decades, and always in time for new kernel versions. ATI was typically way behind and buggy as hell. I would likely not have switched to Linux on the desktop in 2006 if it wasn’t for my GPU “just working”, without any fiddling. Performance was always equal to Windows and stuff like multimonitoring just worked. They even had their nice setup utility to configure Xorg for you.
Could they have handled the transition to Wayland better? Maybe. But claiming they earned a bad reputation in regards to GPU when they are the one big vendor that had extremely active linux support for ages is dishonest and unwarranted, IMO.
Which is completely reasonable. Insanity is trying the same thing over and over and expecting different outcomes.
It’s not like they tried nothing and are all out of ideas; they tried a lot and nothing stuck so far.
We recently had a funny problem. Our service ran fine, but a postgres upgrade failed because some pg internals were broken (broken ref ids). Dumping the DB also failed for the same error. Reading and writing was still fine, though. So we restored backup after backup… no dice. They all had the same issue: it was working for the service but we couldn’t perform any maintenance. Ultimately we had to “manually” dump the data of the service and replay it into a fresh db. That took quite long. But that was interesting, since even the verification of the backups didn’t help us notice that kind of corruption.
I am also a former TeX addict, but I was always more in favor or ConTeXt over LaTeX. And Typst is basically ConTeXt, but a lot faster (as in you get real time preview as you type).
Huh? What’s wrong with Overleaf?
If you “only” need beautiful PDF and it doesn’t have to be online, you can also use Typst with vscode and tinymist as editor locally. Not as powerful as TeX, but I know few people for use TeX even remotely to its fullest. The upside of Typst is, that the “core” syntax for content writing is very markdown-like, so you can focus on writing instead of the underlying language.
Backblaze B2 using Kopia
The linked ticket also references a merge request that went stale. So I would assume this is a good starting point (I haven’t looked at the MR though, so I don’t know how far off from the potentially accepted solution it is).
I don’t think there is a technical reason. Simply no one was interested in implementing it yet. See Nate’s answer over at reddit and the associated ticket.
So once someone is motivated enough it will happen. But without contribution or extreme boredom by the core mainteners (haha) it won’t happen.
Yeah but it also shows the weird naming of WSL. It’s Windows (32) on Windows 64, but Windows Subsystem for Linux instead of Linux on Windows 64 (which would at least have fit the pattern).
The main advantage of SB is TPM. At runtime the key isn’t available and unlocking your disk works automatically as long as nothing has been tampered with (which is then also a nice canary: if you suddenly have to enter your password during boot, something’s off).