decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Well, Fedora seems to be killing itself | 179 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Well, Fedora seems to be killing itself
Authored by: Wol on Saturday, July 28 2012 @ 11:03 AM EDT
Well, the reason is, if you read the systemd documentation, that SysV init
scripts are a huge pile of spaghetti.

In MAJOR breach of the Unix "do one thing and do it well" philosophy.
Systemd takes all the things that are repeated time and time again in any
well-formed SysV script, and replaces them with little executables.

I'm not going to comment how well (or not) systemd has achieved its aim, but the
intention is to make things much simpler. Instead of 90% of a SysV script being
a copy of other SysV scripts, it's now a call to a shared routine. Much less
opportunity for bugs. Much less live code for bugs to hide in. And most scripts
- containing thousands of lines of boilerplate - replaced by a config file maybe
ten lines long.

Oh - and systemd sets out to be SysV compatible. It's just that, rather than
putting systemd in a SysV wrapper, it does it the other way round putting SysV
in a systemd wrapper. And if that doesn't work, it's a recognised systemd bug
(unless they find the bug in the SysV script! :-)

Cheers,
Wol

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )