Systemd

Systemd journal corruption on Fedora

I always keep a terminal window open to monitor system logs in real-time when I’m in front of my computer. Therefore, it immediately caught my attention when the systemd journal offered zero new lines of output. The most recent entry simply contained information about the previous shutdown.

A start job is running for /dev/disk/by-uuid

As I was booting up my Arch Linux box, systemd informed me of a start job running for /dev/disk/by-uuid. 90 seconds later, the job timed-out and some fashionable colored messages flashed by with the speed of light.

Slackware Linux is moving to eudev

Some big news was revealed through the Slackware Current (pre-release) changelog today as the switch from udev to eudev was finally announced.

And this is a big deal because?

udev, which is a device manager for the Linux kernel was absorbed into systemd back in 2012 with a notion of fully supporting systems not running systemd.

As a response to the merging of udev into systemd, the Gentoo eudev project (an udev fork) officially launched a few months later. Their goal was to provide better compatibility with existing software, older kernels, various toolchains and anything else required by users.

Arch Linux - Failed to start Verify integrity of password and group files

The shadow.service unit reported that it had failed and threw the following error message: “user ‘colord’: directory ‘/var/lib/colord’ does not exist”. I had no recollection of housing such a user, but by issuing the command below there was hard proof (image to the right) that colord was indeed a homeless user on my system, and her home was supposed to have been /var/lib/colord.