Yast had the search and nameservers information in, and it even loaded them back when reopening yast (which surprised me, I expected it to read/store from resolv.conf itself). I work with SAP HANA, SUSE is also the supported OS for it (I’ve a SUSE sysadmin certification).
I commented about yast being a gui that failed (silently) doing something simple that shouldn’t need a gui; I didn’t say SUSE isn’t reliable.
It had all networking up and running. It just didn’t have resolv.conf entries, so no dns.
No, the SUSE demo license had expired before he configured it for the first time, so there was no repo access.
He did everything right in yast, but according to the yast log, it was trying and failing to get wpa-supplicant, although this is a VM with no wifi whatsoever. Yast “finished” the configuration with no errors, but failed to place the required entries in resolv.conf and hosts.
It’s just one example of a useless gui trying to make simple things complicated.
Linux is not a company fighting for profits and market share, with software developers paid to work according to the company’s strategy.
You want something in Linux that nobody cares to develop? Decelop it yourself or gtfo.
A few hours ago I was helping a GUI-oriented colleague to get network working in a SUSE test installation. He had configured it in yast (a GUI admin interface), but he couldn’t get to the internets.
I logged in, got me a command line:
ip a s (it had an inteface with an IP, and it was up).
ip r s (it had a default route to the world)
ping 8.8.8.8 (it worked)
host google.com (didn’t work, it’s always dns)
vi /etc/resolv.conf (added search and nameservers, there were none).
problem fixed (also suggested him to check his /etc/host, as domainame wasn’t set either).
Why on earth do I want a gui to make simple things complicated - and silently fail while trying to do it? (yast couldn’t find wpa-supplicant, although this is a VM with no wifi).
IMO, administering Linux through GUI tools is dangerous, because you probably don’t know, or don’t want to know, exactly what the tool is doing. It makes Linux as “inexplicable” as Windows.
For now. 40 years ago, what it does now was impossible science fiction.
Well, the opressed and enslaved usually has no say about changing the law.
On one hand, great; will that extent to software development, architecture and other fields?
On the other hand, sounds like the first step to, when AI and androids reach self awareness and conscience, legally keep them enslaved.
Linux has a graphical file manager? How bizarre.
When you can pay to win, to always have the last word… He’ll let them know.
He’s going to be able to harass everyone that had blocked him.
Why do you have two default routes?
The last line in your table also doesn’t look right.
See the first red box in the documentation text? The underline dashes don’t go up to the last letter (s).
4 year old girl said the “s” was sad because of that, uncle submitted a patch to fix that, and it was accepted.
You’re missing the share name, //192.168.50.1/sharename
It doesn’t do “only” that; I was comparing it with other init systems and described their main, basic init functionality. Sorry if I didn’t do it well.
What does exactly systemd do?
It mostly causes heated discussions and a feeling of nostalgia for simpler times.
When your computer finishes loading the kernel, you have to tell it what to do next. There are dozens of systems and services that have to run (once or keep running) for everything to work. Mounting your disk partitions, bringing the networking up, starting the GUI, initializing all kinds of services, etc.
Once upon a time most (all?) distros used sysVinit, adapted from Unix’s System V to do that. It was simple and very easy to understand and setup: Very basically the init program would call scripts by alphanumerical order (passing “start” to scripts starting with S and “stop” to ones starting with K). You’d place these scripts in /etc/rcX.d, X being a number, the runlevel (and you had just a handful of runlevels, like halt, reboot, single user, gui, etc). Want to run something between starting the network and bringing up sshd? Just create a script in /etc/init.d and link it to /etc/rcX.d naming it SNNmyscript, with NN being a number between the ones in SNNnetwork and SNNsshd. Want to disable a service? Change its script name from S… to K… Change startup sequences? Just change the NN.
Beautiful. But although it worked perfectly for most of us, it did have deficiencies. An obvious one is that it ran these scripts sequentially. Even if your computer was using 0.1% of its power to run each of them, you’d be waiting for each one to run in a single queue.
So a very nice and polite guy came up with systemd. Instead of simple scripts running sequentially, you could now create “unit files”, describing each “thing to do”, for what “targets” (similar to runlevels) that thing is needed, which scripts to run to make that thing happen, and which previous things should have been done before this thing (dependencies). With this, your computer can fire up multiple startup scripts (and stopping scripts) at the same time, only making sure to queue stuff so dependencies are met. For example, you don’t need to wait for sshd to start your database server, but you do need networking before you mount shared disks.
That made boot times much better, but at the cost of complexity and maintainability (and here come heated discussions…).
The problem is that not everyone wanted that tradeoff, but systemd was shoved down everyone’s throat as most (all?) distros adopted it.
So init freedom is a reaction to that, offering you the option of multiple init systems (there are more than just sysVinit and systemd).
No offense to all the other init systems, but I’d stick with sysV if you’re really after simplicity and backwards compatibility with most older systems (and the old ways), or systemd, because it became the de facto standard, it’s faster and more modern.
Should you care? If you have to ask this, then no.
If you had to craft your own init scripts and configurations, and had a ton of legacy scripts, or maybe were building very simple barebones systems, or very complex, always changing startup scenarios and targets or runlevels, or want to exercise your “freedom” just for the heck of it, then you could care.
If you’re a distro hopper (i.e. are more dedicated to “use Linux” than to use applications which run on Linux), having tried 5 different init systems may be one more thing to brag about in distro hopper meetings.
If you’re getting into Linux to learn Linux administration for career purposes, systemd is what you’ll find in commercial systems.
If you’re after an OS to just be an OS (i.e. just run your programs), just pick a well supported (community) and mainstream one, it will most likely come with systemd, and you’ll probably never need to touch systemd. My wife (not technical) has been using exclusively Linux for 15+ years, and I can assure you with 100% certainty that she doesn’t know which init system is there, or what is systemd or sysV.
If you’re new to Linux, curious and want to learn all you can about it, I’d say there are many other interesting and useful things in Linux to learn and care about before you go down this rabbit hole, summoning some nice nostalgic but outdated tech from the dead.
When you say “login screen” is it graphical or the console?
If it’s graphical, can you drop to the console (ctrl+alt+F1 ?) and try to login there? And with a brand new user (create one without the ssd) or root? Just to check if it’s something triggered by a user config pointing to the drive.
Also, is your fstab using UUIDs or /dev/sdXn?
After the hang, if you boot without the ssd, can you then find any errors in the message log from the previous boot?
Haha, I guess many dog owners just can’t see it how it is; probably an addiction to the lopsided unconditional “love”. I used to comment something similar back in Reddit, just to see the flood of downvotes and outraged dog owners.
Same reaction to supporting the idea that some breeds are generally more dangerous and/or more aggressive. “Oh, my MY pitbull is a sweetie!!” (adding this here just to test :D )
Yes, and I heard as a response “but he LOVES the cage”. Really? Why does it need a door with a latch then?
Yes, I’m pretty sure they were still dogs. No crippling deformities.
(edit: but if you need to filter “anecdotal” evidence, just add “in the western world, in modern history”?)
I have used yast to configure the network before (not on this host), and it works.
I quickly looked at the yast log, and there were errors looking for wpa-supplicant. I -think- it’s because my colleague installed this VM months ago, did not configure it, then went on vacation. Now the SUSE “no license” grace period expired, and the host has no access to the repositories.
If that’s the cause, there are two issues: 1. why does it want to install wpa-supplicant if there’s no wifi (maybe it’s a wicked dependency), and 2. why does it fail silently, concluding the config operation as if it ran ok