Screwed up fonts in GTK software, even though the xdg-portal app for KDE is installed. At some point I just gave up. I see no reason to install any Flatpak if the software in question is already in the distro's repository and current enough anyway. Maybe except OBS, because the Flatpak version comes with Youtube integration which, to my understanding, needs to remain closed source and won't make it into a FOSS repository.
I take it you’re on Wayland? The fonts issue is a bug that’s being fixed IIRC in KDE’s portal, but as a workaround for now you can install the GTK desktop portal, which should make the fonts render correctly.
(That is, if you end up needing to use other Flatpaks that have an OBS-like situation)
Once x86 macOS became stable around snow leopard I switched from Linux to macOS full time on my mobile machines. For years home brew was a shining light to get a decent tool chain installed to be able to do development. But somewhere around the time they changed to naming macOS releases after places in California, both home brew and macOS started changing in ways that made it harder to maintain a stable development environment. Why and when did it start deciding to upgrade every package I have installed when I try to install a new package? It regularly broke both mine and our developers’ machines and I finally had enough of both. Stay away from home brew if you want your working development environment to continue working 6 months later. It WILL break when you need it most and cost you hours if not days of work to fix. I’ve never ran home brew on Linux but it’s honestly not anything I would ever consider even when it worked well.
Thanks for the insights! Do you know if these issues continue to persist?
Why and when did it start deciding to upgrade every package I have installed when I try to install a new package?
Is this perhaps related to how for most non-LTS distros (but especially on something like Arch) one is recommended to update all packages before installing a new package in hopes of preventing issues related to dependency hell? I don’t know if Homebrew’s model of packaging is similar enough to Linux’ to make sensible comparisons between the two, but this was just something that came up to me as a thought.
fpm is not a complete solution. It just creates a package from your files, however you need to build them in the environment of the distribution where it is supposed to work, with the same versions of dependencies. OBS is the best solution I know, but with it you need to write packaging scripts compatible with each distro you are targeting. It is quite time consuming and requires a good knowledge of native packaging tools.
You can also use any CI system that is able to execute builds in containers with your target distros. This requires a bit more scripting (just a bit), but modern CIs are easier to setup than OBS in case you need your own instance. This also allows you to use your favorite VCS and workflow you are comfortable with.
I like Netdata because it’s web based, has a large number of metrics, you can pan/zoom the graphs, and it doesn’t use much CPU power. Console UIs are nice but they’re more limiting than something web-based.
As a few have already mentioned, a Debian based distro is a good choice, and you Mentioned vanilla Ubuntu isn’t ideal do to prioritizing snaps, I would then suggest Pop!_OS or Mint. I like what System76 (Pop) is doing with their scheduler and the upcoming Cosmic DE (written in Rust and should see an alpha early next year).
Yeah think so but with extra privacy hardening features and especially useful Screensharing on Wayland! I don’t know if there is an alternative to it for Screensharing on wayland
From what I understand it’s basically like a “thin client” type of thing where the client loads the Kernel from local storage up to a certain point and then boots into a rootfs that is somewhere else on a remote server.
Basically, your system, if asked to, will boot into a limited mode where it exposes its drives over NVMe-TCP. It’s like taking the hard drive out and putting it into a different PC, but over the network.
Similar but in this case the Linux Kernel/Init System act as the PXE firmware so you don’t need a TFTP Server to load initramfs and a Kernel image. And you don’t need a NFS or Samba server because the Server has the drive with the rootfs already exposed to the network.
“target disk mode”, which this claims to be taking a lot of inspiration from, pretty much turns your computer into an external harddrive - so you can connect another machine to it for direct access. This appears to be trying to accomplish the same, but over the network.
If you’ve ever stuffed up a machine so badly that the best idea you could come up with, was to take the harddrive out and work on it from another machine - this pretty much allows you to do that. But instead of taking the drive out and putting it an external drive enclosure, you just ask the stuffed up machine to act as the external drive enclosure.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.