public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wouter van Kleunen <kleunen@cs.utwente.nl>
To: Terje Kvernes <terjekv@math.uio.no>
Cc: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Init replacement
Date: Fri, 2 May 2003 18:35:41 +0200 (MEST)	[thread overview]
Message-ID: <Pine.SOL.4.33.0305021834090.7275-100000@taurus> (raw)
In-Reply-To: <wxxd6j1h2nd.fsf@nommo.uio.no>


I updated the "About" page on the website. I hope that will explain why i
prefer a compiled language over a shell script.

Wouter

On 2 May 2003, Terje Kvernes wrote:

> Wouter van Kleunen <kleunen@cs.utwente.nl> writes:
>
> > On 2 May 2003, Terje Kvernes wrote:
> >
> > > converting init-scripts to XML is a scary process.  init-scripts
> > > should IMHO be human readable, as atomic as possible, and testable
> > > without depending on much more than having a generic shell.  in
> > > addition to verboseness and lack of readability, XML makes it
> > > "interesting" to integrate more complex scripts, like autofs.
> > >
> > > yes, XML is easier to generate for a machine, but you generally
> > > don't generate init-scripts, if you do you probably build them
> > > from templates, which aren't XML friendly either.
> >
> > local res="$(cat /proc/modules | egrep 'serial' | cut -f1 -d" ")"
> >
> > remaining="$(cat /proc/mounts | awk `( print $3 " " $2 )'| \
> >      grep -E ^'code|nfs|ncpfs|smbfs' | awk '( print $2 | '| sort -r)"
> >
> > human readable, i see... hmmmm
>
>   it's readable, yes.
>
> > how can you test something like this?
>
>   by running it bit by bit on the command line, and testing each
>   command.  of course, you can clean up stuff like the above as well
>   to make it more readable.  then again, how would you achieve the
>   same as what the script does without doing just the same thing?
>
> > it will break very easily.
>
>   not really.  there are reasons why one doesn't change the format of
>   proc mounts.  it looks complex, and it is, but it's also very much
>   tried and true.  one could argue about the lack of 'trap' or
>   something similar tools in the scripts though.
>
> > and writing a init script for a daemon is very simple with my
> > system. Not all daemons have an ready to run gentoo init script you
> > know.
>
>   and a lot of scripts require a great deal of "magic" before they
>   run.  why do you think the initscript for autofs looks the way it
>   does?  because start-stop-daemon automount works?  :-)
>
> --
> Terje
>
> --
> gentoo-dev@gentoo.org mailing list
>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-02 16:34 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 [this message]
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
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=Pine.SOL.4.33.0305021834090.7275-100000@taurus \
    --to=kleunen@cs.utwente.nl \
    --cc=gentoo-dev@gentoo.org \
    --cc=terjekv@math.uio.no \
    /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