From: Wesley Leggette <wleggette@gate.net>
To: azarah@gentoo.org
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Init replacement
Date: 04 May 2003 11:05:23 -0500 [thread overview]
Message-ID: <1052064323.1707.7.camel@cyr.kaylix.net> (raw)
In-Reply-To: <1051956324.4516.21.camel@nosferatu.lan>
On Sat, 2003-05-03 at 05:05, Martin Schlemmer wrote:
> On Sat, 2003-05-03 at 11:08, Wouter van Kleunen wrote:
>
> > Yes. I have thought of adding a script-service. But i removed it, because
> > i do not like scripts. I agree that they are convenient for executing a
> > collection of commands, but bash is a very weak programming language.
> >
> > I will think about adding scripts. Maybe just to lower the difference
> > between my init and sysvinit. But rather not bash, bash is ugly :-(
> >
> > it would be nice if people wrote more scripts using functional languages.
> > (haskell, miranda, etc...)
> >
>
> Point is, where say 80% people can code in sh/bash, much less can do
> that in python, haskell, whatever. Thus dropping the 'user' interface
> to the init system being in bash/sh, will make it unusable for many
> users.
Oh come on. Like XML is really than difficult. I'm sure 80% know the
syntax, and Wouter's keywords are a lot simpler than Bash's. Besides,
80% is completly off for people who know bash (and XML syntax too).
Let's face it. Wouter's XML is a lot easier for newbies to learn. It has
actual english in it. I don't see why everyone is so defensive about
their beloved bash scripts.
>
> Having the startup scripts/modules binary though, means you cannot
> do quick changes, etc as well.
>
> And like many others did say, python/whatever have too large
> dependencies. For example, having python initscripts will make
> an initrd/diet_system a PITA to get running.
>
> Having SVC support build into init, now that is a reason why I would
> change init.
>
> Another question that bothers me ... if everybody is so against bash
> being slow, why don't they spent time to get bash's IO more optimised?
> For example, getting bash to read the whole script, and then executing
> it, and not reading line by line should already add much improvement.
>
>
> Anyhow, just a few quick thoughts,
--
Wesley Leggette <wleggette@gate.net>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-04 16:15 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
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 [this message]
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=1052064323.1707.7.camel@cyr.kaylix.net \
--to=wleggette@gate.net \
--cc=azarah@gentoo.org \
--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