From: Evan Powers <powers.161@osu.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Init replacement
Date: Fri, 2 May 2003 15:54:56 -0400 [thread overview]
Message-ID: <200305021554.56144.powers.161@osu.edu> (raw)
In-Reply-To: <Pine.SOL.4.33.0305022113560.8920-100000@taurus>
On Friday 02 May 2003 03:23 pm, Wouter van Kleunen wrote:
> For example firewall generators generate init scripts. And sysvinit
> frontends (KDE has a frontend) uses it. I think also mandrake has a
> frontend for selecting which services get booted. I dunno about suse or
> red hat. I don't say these distro's should immediatly start using this
> init. But your claim that only 1 program parses these files is not true.
I'm not sure if those are particularly good counter examples. I'm not totally
familiar with KDE's frontend, but I was, at a time, familiar with the
Linuxconf equivalent.
Sysvinit frontends probably do not actually look inside the init scripts; all
they care about is the filename. The menus for selecting which service to run
at boot are really asking which script files you want in which runlevels.
Most frontends serve only to manipulate the symlinks. So the script's format
is still parsed by only one program.
As for firewall generators...what sort of generated script are you talking
about? I'd imagine you mean that the program merely generates a sequence of
iptables commands which initialize the tables correctly, since iptables
doesn't have a file format of it's own. I'm not sure how wrapping the
sequence of commands in XML markup is accomplishing anything....
That said, don't take my criticisms too harshly. I think there's much that can
be done to improve Gentoo's init system (despite it's being quite good,
compared to other systems, at present), and I think your direction is
interesting. But there are a number of things in your approach which give me
pause.
Good luck in any case,
Evan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-02 19:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 9:34 [gentoo-dev] Init replacement Wouter van Kleunen
2003-05-02 9:44 ` Paul de Vrieze
2003-05-02 9:54 ` Wouter van Kleunen
2003-05-02 10:50 ` Terje Kvernes
2003-05-02 11:24 ` Wouter van Kleunen
2003-05-02 13:57 ` Terje Kvernes
2003-05-02 16:35 ` Wouter van Kleunen
2003-05-02 17:08 ` Jon Kent
2003-05-02 17:20 ` Paul de Vrieze
2003-05-02 19:23 ` Wouter van Kleunen
2003-05-02 19:54 ` Evan Powers [this message]
2003-05-02 20:03 ` Wouter van Kleunen
2003-05-02 19:56 ` Paul de Vrieze
2003-05-02 20:09 ` Sven Vermeulen
2003-05-02 12:01 ` Jim Bowlin
2003-05-02 21:53 ` leon j. breedt
2003-05-03 9:08 ` Wouter van Kleunen
2003-05-03 10:05 ` Martin Schlemmer
2003-05-04 16:05 ` Wesley Leggette
2003-05-04 18:12 ` Martin Schlemmer
2003-05-04 23:48 ` Wesley Leggette
2003-05-05 12:33 ` foser
2003-05-05 18:31 ` Wesley Leggette
2003-05-03 13:20 ` leon j. breedt
2003-05-04 9:42 ` Paul de Vrieze
2003-05-04 12:39 ` [gentoo-dev] " Robert Wittams
2003-05-05 10:20 ` A.Waschbuesch
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 20:34 [gentoo-dev] " Joshua Brindle
2003-05-02 21:36 ` Martin Schlemmer
2003-05-02 21:50 ` George Shapovalov
2003-05-03 9:14 ` Wouter van Kleunen
2003-05-04 16:02 ` Wesley Leggette
2003-05-05 5:23 ` C. Brewer
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=200305021554.56144.powers.161@osu.edu \
--to=powers.161@osu.edu \
--cc=gentoo-dev@gentoo.org \
/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