Dev1 Galaxy Forum / Installation failure (Excalibur)

Re: Installation failure (Excalibur)

dummy@example.com (fsmithred) — Tue, 18 Nov 2025 22:34:39 +0000

systemd has /etc/machine-id in addition to /var/lib/dbus/machine-id. We have the latter and if you don't want it to change on every boot, edit /etc/default/dbus.

I'm not sure, but I think PeppermintOS uses Calamares. Talk to Grafiksinc, one of their devs who also happens to post here occasionally. You probably need to go over there to get his attention. There might be a way to remove the systemd dependency.

Re: Installation failure (Excalibur)

dummy@example.com (greenjeans) — Tue, 18 Nov 2025 21:49:10 +0000

Dunno, that's a weird one, something's trying to use that systemd command, don't know why. Maybe something in Excalibur is different from Daedalus, I haven't dug into it enough to know. Something in Calamares maybe?

Just FYI on Devuan there is no /etc/machine-id, Devuan changes the machine-id on every boot. Don't know if that has any bearing on your issue.

Installation failure (Excalibur)

dummy@example.com (fredbird67) — Tue, 18 Nov 2025 21:14:03 +0000

I was just doing a test installation of my distribution, F3OS, now based on Devuan, using Calamares, and I just got the following error message in a popup:

Command systemd-machine-id-setup --root=/tmp/calamares-root-kqvis5j_ finished with exit code 127.
Output: env: 'systemd-machine-id-setup': No such file or directory

Any ideas?

In the meantime, I will retry the test installation with Refracta. But I would, of course, prefer to get it to install correctly with Calamares for the sake of those who have never used Linux before, especially when you consider what a fiasco Windows 11 is.

BTW, I did do a test installation on my computer of Debian Trixie with Calamares, and it worked just fine, so this error is specific to Devuan.

Thanks in advance,
Fred in West Plains, MO