Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:A body in motion etc. (Score 1) 67

Don't waste your precious analogies on Slashdot; they'll only be torn to pieces.

Unless they're car analogies. Then they'll be driven into the ground.
Allow me: this new super cluster discovery is like finding out your car isn't just driving up the ramp of a semi trailer, but that the semi-trailer is on the deck of an air-craft carrier.

Comment Re:Troll much? (Score 4, Insightful) 613

You do have to put a fraction of the time you did in 30+ years of learning your way around SYSV systems into actually learning systemd in order to expect the same level of proficiency.

This is BS. "Learning" SYSV configuration takes 15 minutes to explain run levels and that everything is scripts and (usually) symlinks. You could even learn what you need by recursively grepping /etc for a process name and the script it's in is readable to anyone with programming experience. GP pointed out that a config file for systemd is sitting in /lib. WTF?

Comment Re:Troll much? (Score 1) 613

-Starting up /bin/sh hundreds of times during boot is wasteful and slows boot. Systemd mitigates that by enabling more lightweight service start. However you'd have to care something about boot times, which is rarely even in the mobile category [...]

-Sequential startup of services is silly when many can be started in parallel. Of course now you have to debug a less deterministic boot process to enable such a thing, with the same inscrutable code paths for the sake of a faster boot very few people needed.

Especially in the server world. The OS boot time is a fraction of my server's boot process. Starting out, you've got POST with RAM tests et al. The RAID array spins up and does its dance. Maybe IPMI gets in the mix. The NICs might have their own prompt for configuration changes lasting a few seconds. And sometimes the BIOS decides to give a detailed list of events with a ten second countdown (bypassable with a keystroke). Then some particularly silly BIOSes complain for a few seconds about a lack of keyboard. Finally, the MBR is touched. systemd will never speed up the slowest part of the boot process, so it's useless for that purpose in a server environment.

Comment Re:The Future! (Score 1) 613

Newcomers don't mess around with init systems genius. The debate pro/against systemd is something that power users/sysadmins have, not grandma and cousing Louie.

GP didn't say willfully-ignorant. Newcomers come in all shapes and sizes. The ones newly coming to Linux are usually still power users and sysadmins in the other operating systems they're used to. I remember starting out with Linux. It was weird compared to SunOS, but it wasn't as weird as IRIX. Being new back then meant learning a few oddities and moving on. A decade and a half later, Apple's version of Unix is doing annoyingly convoluted stuff with xml and binary config files, and Linux seems to want to follow into the giggle weeds. Nobody wants to keep it simple any more.

Slashdot Top Deals

The only possible interpretation of any research whatever in the `social sciences' is: some do, some don't. -- Ernest Rutherford

Working...