3 ms·
After getting used to systemd, I decided to put my toes in the water and try guix. From a user's perspective you never really don't have to care much. Even comp
by bjoli 1y ago
After getting used to systemd, I decided to put my toes in the water and try guix. From a user's perspective you never really don't have to care much. Even complex services are pretty simple, and it is really not like you are doing anything different.
The downside is, of course, that more and more of the linux userland depends on systemd. That is bound to become a problem sooner or later.
My biggest gripe is that I would like to have a simpler way to install it onto my computer. I need nonguix to even boot on one of my computers, but I really really hate doing that because doing a system install from nonguix has a tendency to break things for me later on.
- hardwaresofton 1y ago> The downside is, of course, that more and more of the linux userland depends on systemd. That is bound to become a problem sooner or later. This is the main problem. Systemd has the most eyes, and the most active development, and I just don't want to spend innovation tokens on that as well. > My biggest gripe is that I would like to have a simpler way to install it onto my computer. I need nonguix to even boot on one of my computers, but I really really hate doing that because doing a system install from nonguix has a tendency to break things for me later on. That's a huge issue. Which also reminds me, this kind of requirement is dead in the water for the GPU era, at least until there are sufficiently F/OSS high quality drivers (which may be never). Maybe the answer here is to just use only guix the package manager