Slashdot Mirror
GNU Hurd 0.6 Released
jrepin writes It has been roughly a year and a half since the last release of the GNU Hurd operating system, so it may be of interest to some readers that GNU Hurd 0.6 has been released along with GNU Mach 1.5 (the microkernel that Hurd runs on) and GNU MIG 1.5 (the Mach Interface Generator, which generates code to handle remote procedure calls). New features include procfs and random translators; cleanups and stylistic fixes, some of which came from static analysis; message dispatching improvements; integer hashing performance improvements; a split of the init server into a startup server and an init program based on System V init; and more.
From the GNU Hurd Wiki page:
It's time [to] explain the meaning of "Hurd". "Hurd" stands for "Hird of Unix-Replacing Daemons". And, then, "Hird" stands for "Hurd of Interfaces Representing Depth". We have here, to my knowledge, the first software to be named by a pair of mutually recursive acronyms.
—Thomas (then Michael) Bushnell
If it weren't for deadlines, nothing would be late.
Because learning new software is haaaaarrrd! Much easier just to complain about it.
Actually I was pretty happy with the systemd learning curve. What I wasn't happy about was not being able to figure out why my network interface insisted on getting a DHCP address despite the fact I had explicitly disabled DHCP and assigned a static IP address to it via the unit files, because *there was no log of what unit/configuration files were being executed/read and when*, and - as far as I'm aware - there is no way to enable logging or figure out exactly what is going on.
And just think, with System V Init or RC scripts I could have just added a few "echo" statements to figure out what was going on instead of Googling for several hours until I found what the actual problem was.
THAT is what is stupid about systemd.
If your boner for microkernals lasts more than 25 years, you should probably consult a physician.
I recommend a look at Andrew S Tannenbaum's baby:
MINIX 3 is a free, open-source, operating system designed to be highly reliable, flexible, and secure. It is based on a tiny microkernel running in kernel mode with the rest of the operating system running as a number of isolated, protected, processes in user mode. It runs on x86 and ARM CPUs, is compatible with NetBSD, and runs thousands of NetBSD packages.
Minix
The reasons for disliking it vary, but there is at least one common thread among those who are upset about it: Systemd is being shoved down their throats, in that several of the most widely used, widely loved, deeply entrenched linux distributions have announced that they are adopting it. Many people who use those distributions do so for very good reasons, and since there are no equivalent alternatives, these people are being forced to either accept systemd (which will cause them unwanted trouble) or migrate to an inferior distribution (which will also cause them unwanted trouble). That kind of thing is enough to piss anyone off.
And...it's obvious you've never administered a systemd box....or tried...or even read about systemd or unit files/services.
It's so ridiculously easy to make nice clean dependencies so that my service starts up when it should only when it should, without needing anything more than VIM to write them in maybe 10 lines per unit file.
For example, I have a service that just runs a binary (an rpc type server). There's a single line, in the *text* file (because that's all there is), telling it that when the binary exits, then the service has closed. There's also a single flag that I have set that restarts the service if the binary ever exits. (yay, automatic restart and logging)
Then there's a list of different types of dependencies at the top. My script should not start without networking, it also shouldn't start before some helper services, and it depends on a kernel module device, so all of those are listed *one line each, maybe 15 characters*.
I also have a simple unit for that device driver, so that whenever I load or unload the device driver, it fires up fire up or kills the service, and all of the dependencies, automatically.
Not a "make sure it has time" type sleep needed anywhere because *that would mean my startup was fundamentally broken* (and it's rare to *not* see them in old boot scripts).
When I'm debugging new builds, I just do "systemctl --failed" and it gives me a nice list of what services failed and why. Then "systemctl status " for more details, with a bit of log message.
You can stay in the stone age and grep your text log file (which systemd also dumps its messages to by default on most distributions), or you could just do "journalctl -u --this-boot" and see exactly what happened in a nice clean live and navigatable format.
Well, I dislike it because it makes it much harder to administer a box as a UNIX-type machine with a simple text editor. Now it seems like I'm stuck with meta-scripts invoking meta-scripts invoked by other scripts to do something as simple as changing my DNS servers.
I run Fedora 21, a systemd distro. You want to change your dns servers on Fedora 21?
You can use the Network GUI thing nm-connection-editor or whatever equivalent your desktop uses.
Or if you prefer the terminal or console you can use nmtui which is the same thing in a terminal/console
Or you can /etc/resolv.conf That still works. You might still need to reset the connection after the change.
vim
Or you can:
nmcli con mod connection-name ipv4.dns "8.8.8.8 8.8.4.4"