grml / grml-autoconfig

main bootup process of a Grml system

grml-autoconfig

This repository contains the grml-autoconfig framework of the Grml project. The config framework is for the main bootup process of a grml system.

Further information is available from http://grml.org/config/grml-autoconfig.1.html

grml-autoconfig's Issues

Bootoption `lvm` tries to enable deprecated lvm2-lvmetad.service

When booting with lvm boot option, you'll notice the following error message:

Failed to start lvm2-lvmetad.service: Unit lvm2-lvmetad.service not found.

The LVM devices are active though as expected, so it's just a cosmetic issue, should be fixed anyway.

Reload systemd after modifying fstab

On grml64-full 2022.11-rc1, mount(1) shows a warning about systemd using old data for /etc/fstab:

mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use `systemctl daemon-reload` to reload.

I think (but am not sure) this is "caused" by grml-autoconfig updating /etc/fstab, but not reloading systemd.

Broken unicode console

While c820a66 was supposed to improve the situation it's not fully resolved yet.

STR, boot current daily ISO with defaults, press "d" to enable german keyboard, then press "ä", or just invoke systemctl status:

The ECDSA host key for grml has changed

I need to access the grml64-full live system over and over. However, on each of its fresh start, I'm getting:

The ECDSA host key for grml has changed

when I tried to ssh into the freshly started grml live system. I presume that's because the sshd is being initialized each time for a fresh boot.

Now that the grml64-full live system will always be called grml in my local network and it will always have the same IP for each fresh boot, I'd really hope that the ECDSA host key for grml remains the same as well, so that I won't need to deal with the following situation each time:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for grml has changed,
...
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
...

Thoughts?

Even it will not be officially supported, will there be any existing mechanism that will allow me to achieve so myself?

Ah, maybe a new command, aside from ssh=xxx, which will be in form of sshc=xxx, which stands for "ssh consistent"?