Calibre is one of the great pieces of FOSS software, and demonstrates everything good about FOSS: it has regular updates; it’s been around for simply ages; it works really, really well; it gets updates and new features and yet has never in my memory had a breaking, non-backwards-compatible release… it’s stable; and it resists - in its way - the attempt by publishers to steal our rights and ownerships of our media.

I contribute donate to Calibre. I hope that Goyal has a successor lined up to take the helm who can continue such an outstanding contribution when he finally retires from the project.

Edit: clarification

I know logind can’t easily be, because I ran Artix for a while and they were using a decoupled version of it, and there was a big discussion about swapping it for something else because it was so hard to maintain.

I also have the prompt set to the host name. I’ve never understood why people included their usernames; I don’t log in to more than one account on each machine.

It is not modular. This is a lie Poettering keeps pushing to defend building a huge edifice of interdependent systems.

Look at the effort required to factor out logind. It can’t just be used in it’s own; it has a hard dependency on systemd and needs code changes to decouple.

I will repeat that journald is really bad at what it does, and further assert that you can not run systemd without journald, or vice versa. That you can not run systemd without getting timed job control. Even if you chose not to use it, it’s in there. And you can not get time job control without the init part. In most unix systems, init and cron are utterly decoupled and can be individually swapped with other systems.

Systemd is not modular if you can’t swap parts out for other software. Systemd’s modularity is a bald-faced lie.

The one exceptions are homed and resolvd, which are relatively new and were addedlong after systemd came under fire for being monolithic. And, ironically, they’re the components most distributions don’t use by default.

It absolutely is. The typesetting is beautiful, and it’s far easier to work with than (LA)TeX. It also doesn’t take up 2GB of disk space.

I’ve been using systemd on most of my systems since it was released; I was an early jumper to upstart as well.

The thing I don’t like about systemd is how pervasive in the OS it is. It violates the “do one thing, do it well” Unix philosophy, and when systemd went from an init system to starting to take everything over, I started liking it less.

My issues with systemd is that it isn’t an unmitigated success, for me. journald is horrible: it’s slow and doesn’t seem to catch everything (the latter is extremely rare, but that it happens occasionally makes me nervous). There are several gotchas in running user services, such as getting in-session services working correctly (so that user services can access the user session kernel keyring).

Recently I’ve been using dinit on a system, and I’m pretty happy with it. I may switch all of my systems over to it; I’m running Arch everywhere, and while migrating Arch to Artix was scary the first time, in the end it went fairly smoothly.

Fundamentally, systemd is a monolithic OS system. It make Linux into more of a Windows or MacOS, where a bunch of different systems are consolidated under a single piece of software. While it violates the Unix philosophy, it has been successful because monolithic systems tend to be easier to use: users really only have to learn two command-line tools, vs a dozen. Is it categorically better, just because the user interface is easier for new Linux users?

dinit also has the ability to run user services, FWIW.

As long as it isn’t github.

Publish that puppy. It can’t hurt.

Don’t do it in github, though. Sourcehut is better; or if you crave that cluttered, JS-heavy feel, Gitlab.

Maybe! How is it better than keeping a README?

If it’s just a command, I put it in a readme. If it’s a series of commands, I put it in a shell script. What would your tool bring to the party, and if I’m going to turn to a third party solution, why shouldn’t I use Salt or Puppet instead?

Except that one is automatically versioned and would have saved you this pain, and the other relies on you actively remembering to reflexively commit, and then do extra work to clean up your history before sharing, and once you push, it’s harder to change history and make a clean version to share.

These days, there’s little excuse to not use COW with automated snapshots in addition to your normal, manual, VCS activities.

// Increment i
i++;

Very info. Much useful.

The most popular Linux distros are binary based. Gentoo upgrades build all new software from source. If you don’t want long install times, don’t usr one of these compile-everything-from-source distros.

There’s no option to install Windows from source, and it doesn’t really come with anything more than the OS, anyway, so it’s apples yto oranges. Windows might not even be compilable on consumer hardware.

Yeah, I wasn’t saying it was bad; I meant only that Linux didn’t have to worry about device drivers for it, because the fob handles reading the fingerprint chip.

I dunno. I have a fair number of packages installed from AUR, and the Rust ones take forever to compile. CPUs may have gotten faster, but some popular languages have gotten much slower to compile.

Yup! It’s very much like mpd, except streaming without an additional component.

They use the SoundCloud API. You only need either gonic or Navidrome, plus a client (like ostui).

If you do, use the -k option - it locks access to the rook service to only the user session. Rook works without it, but is more secure with it.

It’s not, really. All of those programs are Go, and single executables. There’s no “install” for either gonic or ostui (IIRC, also Navidrome): you download or compile the executable and run it, and you’re off and running.

Someone mentioned Docker; in this case it’s unnecessary unless you’re doing it for security. They’re just each a single binary. You’ll have to either create a config for gonic or Navidrome, or run them with commands telling them where your music lives, but that’s it. Running on the same machine, you don’t even have to open the ports on your firewall. However, if you do, Tempo for Android lets you stream the music to your phone from gonic or Navidrome, too.

These are very, very simple programs to run. ostui is a TUI, so if you prefer GUIs you’ll want a different client, but both of the servers are easy to run and nothing to install - just run them as you, not even root.

I think that’s because Yubikey handles the fingerprint reader part, not Linux, right? As far as Linux goes, it’s a black box security fob - but I might be wrong about that.

CUPs is simply ancient. It’s due for an overhaul; I keep expecting someone to come along and Poettering it, only I’d hope without also making it take over cron jobs and logging.