From: Roy Lanek <lanek@novenine.com>
Subject: Re: runit integration
Date: Wed, 31 May 2006 12:04:50 +0700 [thread overview]
Message-ID: <20060531050450.GA26140@kayumanis> (raw)
In-Reply-To: <20060530234036.GD5387@home.power>
> > I think that runit should provide some compatibility
> > mechanism with the existing rc runlevels and
> > /etc/init.d/ scripts. Maintainers carefully polished
> > those scripts, [...]
>
> I don't think it's possible and good idea. Main reason
> to use daemontools/runit - get as secure and as reliable
> solution as possible. It's nearly impossible to write
> complex software which will be secure and reliable...
> and because of this daemontools and runit prefer most
> simplest and straight solutions. Your idea will add
> additional level of complexity and thus result in less
> security and realiability.
>
Plus, *reality check* [1] if you don't agree, please:
2.5 STARTUP SCRIPTS
...
Red Hat startup scripts
Startup scripts are one of things that distinguish
Linux distributions from each other. Red Hat's are a
complicated mess; they contain many comments such as
# stupid hack, but it should work
and
# this is broken!
...
SUSE startup scripts
Startup scripts are one area in which SUSE really
outshines the other Linux variants [2]. SUSE's
startup scripts are well organized, robust, and well
documented. ...
Debian startup scripts
If SUSE is the ultimate example of a well-designed,
well-executed plan for the management of startup
scripts, Debian is the exact opposite. The Debian
scripts are fragile, undocumented, and unbelievably
inconsistent. ...
[1] Evi Nemeth, Garth Snyder, and Trent R. Hein, Linux
Administration Handbook, Prentice Hall [these fellows
are authorities on the domain: UNIX sysadmin]
[2] The Linux Administration Handbook covers three Linux
distributions in detail: Red Hat 7.2, SUSE 7.3,
Debian 3.0.
Moreover, I wonder how much the *famous trick* of
the how-to-boil-a-Bullfrog recipe [slowly increase
the temperature of the water] has played above ...
there where Evi et al. write of the--yup--"ultimate
example of a well-designed, well-executed plan for the
management of startup scripts."
Cheers,
/Roy Lanek
--
######################## bagai air di daun talas
##### . slackware ###### as if water on a leaf of talas
##### +-----linux ###### [two things that never get along ... talas has a
######################## thin waxy layer and therefore is waterproof]
prev parent reply other threads:[~2006-05-31 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 7:57 depuis
2006-05-30 14:23 ` Charlie Brady
2006-05-30 23:40 ` Alex Efros
2006-05-31 5:04 ` Roy Lanek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060531050450.GA26140@kayumanis \
--to=lanek@novenine.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).