ParadeDuGrotesque

In french "rape" means grater or shredder.

Rape à fromage = cheese grater

First of all, what makes you think he was killed by a government? It's all speculation at this point.

The only thing that is certain is that his death is very convenient, to a lot of very rich, very well connected people who may or may not have organized to allow him to be "suicided" in jail. Most of these people probably did not want him to reveal that they also were pedophiles, and that they had sex with very young children that Epstein procured for them.

But beyond that, there is the question of justice, and the fact that victims did not get it, and other guilty parties were not judged.

In other words, money and power can protect you from the law. This is what riles people off. Epstein is dead, but justice has not been served.

Corgi in a baggy

It's either Slackware (Linux, no systemd), OpenBSD or NetBSD.

True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month.

One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right?

Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period.

Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.

In Slackware, just do an "ls /var/log/packages/*" and your are done.

This is the only correct answer. 😂

If that's the case, my advice is to spend some time to understand the finer point of kernel configuration and compiling, and to compile a kernel as stripped down as possible. Hint : 'dmesg' and 'make menuconfig' are your friends.

Include only the drivers you know you need, and especially network, graphical card, and sound card, and make sure you target your CPU architecture. Then, and only then, can you start including fancy configurations like the ones you mentioned.

Finally, consider adding as much memory and SSDs in your configuration as possible, as these usually have a huge impact on performance.

The question is this: if your distribution already provides a working kernel, and the battery life and performance are acceptable, why waste your time recompiling a new kernel?

Compiling your Linux kernel used to be mandatory, precisely because Linux was so fast moving and because hardware management was poor. This is (mostly) not the case anymore.

Use the kernel provided by your distribution, and let them worry about updating testing and securing it.

I say this as someone who used to compile kernels, to support all the hardware in my servers. I don't do this anymore, and I haven't done this since 2010 or so.

If the interfaces are the same, and the first machine picks it up and configures it, but not the second, then the configuration might be slightly different.

Again, you should use dmesg on both machines, to make sure the interfaces are the same. I suspect the 2nd machine may have a different card than the 1st.

Another possibility is that the 2nd machine has an additional, and different, network card that is picked up as the primary one by the system. But dmesg should be able to tell you what the issue is.

You mentioned the DVD drive and the network card, and I think that's the two major ones. If your machine uses wifi, you will definitely need to configure that as well.

Once booted, I would go through your system dmesg and try to figure which peripheral is different from the machine used to create the boot disk. These are the ones you want configured.

Not really at much risk... YET.

Give it another 6 months or so.

Posteo: reliable and very cheap.