@nahkhiirmees: you might rather want to use the reject statement in the client host's /etc/dhcp/dhclient.conf. See man dhclient.conf for details.

Thank you for noticing. Yes, they are all perfect again

Afaik, when you installed lvm2 it should have added itself to initrd. Though my conjecture from your other notes is that you have the lvm2 software installed some other way. Perhaps a package reinstallation would be an option?

@Grumpy, with all respect, it's kind of like contacting your bike manufacturer when you, on your way to the shop, find that there is a temporary road closure.

More precisely, the Temporary failure in resolving 'deb.devuan.org' notice is from the initial phase in the networking when the apt software (on your computer) attempts to find an IP address for that service. The service itself is not involved in that phase.

I don't know much of this either, but fwiw I agree with your observations.

You might be able to use amixer to toggle that 'HDMI/DP,pcm=3 Jack' control.
First you'd do

amixer contents

to see what is possible and the "names" of things, and then something like

amixer cset iface=CARD,name='HDMI/DP,pcm=3 Jack' toggle

to toggle that control.

The daedalus preview ISOs are currently only those that provide packages. Each is set up as a "repository" which most easily is used as a "file://" source in sources.list. I suppose some "cdrom:" line might work as well but I haven't had luck with those. So, my suggested hands-on is:

• mount the ISO at some file path /X

• add a line to sources.list (note the plethora of slashes):

  deb [trusted=yes] file::///X daedalus main contrib non-free

• then run apt-get update and so on

Those ISOs don't include any installer and are not bootable.

quick note: I think your IV and V are in wrong order: init executes /etc/init.d/rcS because that's what /etc/inittab says. That file is the configuration for init.

Please continue

EDIT: Actually, you skipped over the pre-pivot stage, which is the initial bootup (adding .1 to your III) using the initrd filesystem.

The kernel begins by running its /init which is a shell script, and that script will eventually pivot the root to the "real" filesystem and exec /sbin/init. The initrd scripting is held in /usr/share/initramfs-tools which is a configuration place for building an initrd, since the actual, running initrd is the cpio package loaded from /boot into RAM by the kernel (using the initrd= parameter).

afaik most linux systems have that 2-stage boot, to allow the bootup to be programmed generically even though every actual bootup is a specific host. It's quite possible to set up the bootup for the specific host without using an initrd stage but then typically it needs a specific kernel with the right modules compiled in.

Isn't it called mariadb in chimaera?

Respectfully, these "works for me" anecdotes seem rather small-minded and useless, pretty much  like the whole idea itself.

Personally I'm in no way confused by having multiple directories with programs and libraries, and I imagine that the likelihood of confusing something or someone is larger with making this kind of change than not changing.

The idea is a matter of choice, and the main stigma is in the question of who should make the choice.

In many ways it's similar to that choice of excluding /sbin and /usr/sbin from non-root user's default setup; a choice which in my view is equally stupid.

But I don't make these choices. I merely learn to live with them.

Use jitsi

@Altoid, quite possibly the MemAvailable measure has lost its most significant digit (it's rather unusual to have more free than available memory), and maybe you should consider replacing

with something else, like e.g.

_memavail=$(sed '/memavailable/I!d;s/[^0-9]*//;q' /proc/meminfo)    # OK no cats or cuts
_memfree=$(sed '/memfree/I!d;s/[^0-9]*//;q' /proc/meminfo)          # OK no cats or cuts

EDIT: (though maybe I'm wrong about what memfree and memavailable means?)

Usually "install linux beowulf" would mean to use an installer ISO which then kicks in already on the boot-up of the machine.

Presumably you think of doing something else and you may then need to explain in some more detail what you mean.

In particular "installation through the command line" implies you are running an OS. which?