www.omgubuntu.co.uk has some decent new and app update news here and there, and other generalized release news for various other distros aside from Ubuntu.
Looks like they have no idea how to get their software working using Nix. The following blurb is absurd to most GUIX or Nix users:
NOTE: In most cases, end users should never compile fwupd from scratch; it’s a complicated project with dozens of dependencies (and as many configuration options) and there’s just too many things that can go wrong.
Users should just have fwupd installed and updated by their distro, managed and tested by the package maintainer. The distribution will have also done some testing with how fwupd interacts with other software on your system, for instance using GNOME Software.
I’m not sure I see the problem here? It does say most cases and I’d definitely consider Nix/GUIX users to be in the minority for this (on top of users who would even compile software themselves in the first place).
Also from what I experienced during my (not so long) time with NixOS, usually things in Nixpkgs were contributed there by community members who ported applications over to be compatible with Nix. Sure, it’s a nice extra thing when the application developer does so out the gate, but given how special Nix and GUIX’s environment is, the onus has never really been on the app dev.
I’m not pointing to a problem per se. I’m just saying that this dev dismissed the act of building this from scratch as impossible when it is not actually impossible. Honestly, I’m just trying to spread the word about Nix and GUIX because they make things that were previously considered impossible (like this) possible.
I see, that’s plenty fair enough, although I don’t think they meant it quite so literally (but rather as a method of lightening their support requests - I don’t have any fwupd capable hardware AFAIK however I get the feeling fwupd is pretty popular).
I find it really cool what Nix/Guix are doing and I give major props to their communities for what they’ve pulled off, for what its worth.
most flatpaks are awesome, it’s my preferred way to get apps. except for steam and syncthing. for some reason no amount of fuckery in flatseal can get flatpak-steam to correctly recognize my game drive or flatpak-syncthing to actually sync files from certain locations. for everything else tho flatpaks rock
Flatpaks are sandboxed to user space. I use Flatseal which allows you to grant flatpaks additional permissions. I used it to allow the flatpak version of syncthing to sync files that it otherwise lacked read/write permissions for.
That solution has worked really well for me and resolved my main frustration with flatpaks.
yeah I mentioned I used flatseal lol. Ive tried giving it specific narrow permissions and I’ve tried just enabling everything and giving it full perms but nothing works great the way other versions of syncthing and steam just work
Syncthingy works great? Try either Flatseal or KDEs flatpak permission settings to add the directories you are missing. As long as all packages use Portals, either they are completely unisolated or they break in those ways. I prefer the second option and add the needed directories
I just had to switch my work computer from Arch to Ubuntu becusse they want MDM on all computers now, and flatpaks are litetally the only reason i can tolerate it.
I now prioritise getting stuff from flatpaks, then the repos, and if they dont exist i use Distrobox to export any app thats only on the AUR for example.
Great. Works on anything without any issues. I use it for pretty much everything (except web browser and only because I don’t wanna bother with permissions on that)… As for the size argument, I have also never had isssues with space, my laptop has 128GB of storage total and the /home partition on my desktop is ~100GB, both use fllatpaks for pretty much everything, I have no issues with space on either… And yes I use flatpaks on gentoo, cry about it.
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
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.