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.
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.
Yes, they do.
The reason for this is that the Catholic church is one of the most powerful (if not the most powerful) religious movement on Earth.
Its interests may conflict with many countries interests (USA, Russia, China, Israel, etc) and its influence can be enormous in the countries where it is present. Think about the Church position on Gaza or Ukraine, for instance.
Many intelligence services therefore spy on the Vatican. The NSA, for instance, is on the record as saying they never cracked its codes (which is a debate for some other day), it was mentioned in the Puzzle Palace if I remember correctly.
I would say, like many others, Remmina.
Putty also has a Linux version, so you can use that as well. Its session management is a bit clunky, but it works and it offers some fairly good functionalities.
But ssh is first and foremost a command line tool. As others have said, invest some time to learn its commands and configuration files.
C'est déjà fait depuis longtemps : les Allemands (BMW, Mercedes, etc.) et les Japonais ont des usines dans le sud des États-Unis. Et des vraies usines, pas juste des vissages de dernière ampoule.
Par contre, les taxes décidées par Trump portent aussi sur les pièces détachées provenant d'Europe...
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.
Educate yourself and leave US providers. We have plenty of European services:
Homepage | European Alternatives
You have to define 'we' and you also have to define 'WW3'.
Possible scenarios:
-
USA decides to get actively involved in Ukraine's conflict. Yes, that could spell WW3. Low probability, though, since Trump does not care about Ukraine.
-
Russia decides to attack Western Europe. Probably only a regional conflict, since Trump would probably pull out of NATO. This is the scenario a lot of European nations are gaming today.
-
China attacks Taiwan and/or North Korea attacks South Korea. Probably a regional conflict, but with a high probability of escalation. Trump would drop both South Korea and Taiwan at the drop of a hat.
-
Iran attacks Israel, probably through proxy. Regional conflict. This is already going on, so low risk of escalation.
What's App : Signal.
Instagram: Pixelfed
TikTok: loops
YouTube: peertube
Xitter: Mastodon (pleroma, akkoma, etc ...)
Google maps: open street map
Reddit: Lemmy 😉
Google search: duck duck go, startpage
I'll let you Google the names of the different apps.
That submarine imploding near the Titanic will never be not funny. Especially since the guy who designed it believed in the "move fast and break things" nonsense.
Every person on board paid a pretty penny to be on that sub, so no pity from me either (except perhaps for the teenager who was reportedly terrified to go on, but did it to please his rich prick father).
It used to be BRIC (Brazil, India, China, Russia) or BRICS (same + South Africa). In the article, it has been extended again to other nations, therefore "so-called" because its membership is not the same anymore. Also, the membership seems very informal, it's just a bunch of countries maintaining ties and having discussions, not a real group of countries, with its own set of rules and institutions.
Once you understand Slackware, you realize it is really simple and stable. It comes with an excellent selection of software in the base install, and does not contain any "surprises". I have had uptime in the 200-300+ days range on my home server, updates and security patches are quick and painless, etc.
In other words, it is a Linux optimized for usability and Unix compatibility, not necessarily user friendliness. It assumes you know what you are doing and gets out of your way.
