| Servers are very rarely rebooted and a speedy boot isn't usually that important.

I don't run any servers but it seems to me if I have to reboot my server, I want it back online pretty quick.

Old init mainly addresses service start and stop. Systemd allows for keeping those services running. I'd think that would be pretty important on a server too.

Not sure if you're kidding or serious, but I LIKE a message that expresses hope.

Thanks.

You may have heard that crap, but none of it is true.
What is true is that your system boots way faster running systemd.
That's what the "imagine booting with systemd" comment is about.

| Is that you, Lennart?

| https://www.freedesktop.org/wi...

That's really udevd, one of the many daemons that is managed by systemd.

I think Lennart and company first revamped the init system then they turned their attention to the many services the init system manages. They really shouldn't be attaching the systemd moniker to all this stuff, it's giving the wrong impression. The systemd init system is rather small. It's all the services they're revamping that creates the huge source file.

What possible difference does it make how init script support is implemented?

If you are a glutton for punishment, you're free to write init scripts and they "work" as they used to.

| I love the newer longer command syntax.

So this is Unix, if you don't like the long commands, set up some aliases. Problem solved.

It's so big because the systemd developers have taken on supporting lots of stuff that's not part of the init system.

No need to bury the trees.

Trees drop leaves (containing carbon) every year. Building deeper and deeper carbon rich soil. Even when the trees die, much of the carbon remains in the soil.

Your memory is only okay (faulty in some areas).

Those read and print areas ran from 1-80, not 0-79. Print area started at 201. (The machine addressing was truly decimal user friendly, no counting from zero required.)

All the 1401's I worked on had hardware multiply/divide. I know they made them without, but I never worked somewhere that tried to save money that way.

The characters were definitely not "bytes". The term bytes was introduced with S/360.

There was no "checkmark" bit, it was called a wordmark.

I never saw anyone write a card loader, the compiler would spit out the card loader as the first 5 cards of the object deck.

I started on the 1401 in 1964.

I actually watched the video.
Seems like Facebook is finding systemd useful.
They really present some extreme use cases.
At one point they call systemd "awesome" so no doubt they will "keep it".

Agree completely.

I've been using a systemd system for years now. Not one problem related to systemd. Unless you call fast start up and shut down a problem. The old init scripts were a mess, each one slightly different with no easy way to tell what commands each one would accept, and no way to get something simple, like the human readable purpose of the script. Systemd is a big improvement, for some reason rejected by people that somehow feel empowered because they can hack startup/shutdown scripts.

Seems like none of these web page designers can figure it out.

Want to present an overview that will draw your users in? Represent each item with a SINGLE LINE of TEXT. Slashdot, Fark, Google News, not a single site can figure it out.

After that, hover or click on more, or whatever. But you can't beat that old tried and true one line per subject interface.

Not if you combine the 2 airplane costs.
11.50 airplane cost
14.00 airplane maintenance
====
25.50 real airplane cost

Everyone knows, you peel off one of the dozens of stickers that the vendor installed, then you place it over the camera.

What you have is called tinnitus. Look it up and stop believing in magic.