From: Justin Whitney <ripple.gentoo@ripple.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] initscripts in python
Date: 16 Apr 2003 16:54:15 -0400 [thread overview]
Message-ID: <1050526455.25760.100.camel@osiris.ripple.be> (raw)
In-Reply-To: <20030416085248.GD1795@Daikan.pandora.be>
Thanks for the arguments thus far.
So added to the cons list is:
*addition of newer less-tested interpreter could add instability
*very small/short scripts incur overhead
Here are two mitigating arguments to counter the first statement.
First - a separate, stable build of python could be used as the
system-boot interpreter. it might make sense to statically link it and
so forth to lower dependencies... perhaps even to optimize it in some
respects, for its task.
Second, a shell script like the runscript.sh that is already used could
be used to launch the interpreter and check for a runtime failure. On
failure it could launch the .sh version of the bootscript. This means
keeping two copies of the shellscripts obviously (which wouldn't be a
bad idea anyway...) this would at least have the benefit of salvaging
the boot...
As for the overhead problem with very small scripts, I don't see that
going away... in fact converting such scripts would be a waste of time
in the first place, because it doesn't make use of any of the advantages
proposed by the change. It would make more sense to set up the boot
process to be able to run both kinds so you don't waste your time.
--Justin
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-16 20:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 1:29 [gentoo-dev] initscripts in python Justin Whitney
2003-04-16 4:09 ` Daniel Armyr
2003-04-16 5:38 ` merv
2003-04-16 7:25 ` Jeff Rose
2003-04-16 8:49 ` merv
2003-04-16 8:19 ` Paul de Vrieze
2003-04-16 8:52 ` Sven Vermeulen
2003-04-16 20:54 ` Justin Whitney [this message]
2003-04-17 20:05 ` merv
2003-04-17 5:49 ` Joseph Carter
2003-04-17 6:27 ` George Shapovalov
2003-04-17 18:25 ` merv
2003-04-17 7:42 ` Paul de Vrieze
2003-04-16 22:44 ` Abhishek Amit
2003-04-17 6:45 ` Sven Vermeulen
2003-04-17 20:56 ` merv
2003-04-17 22:26 ` Caleb Shay
2003-04-17 23:32 ` merv
2003-04-17 18:18 ` merv
2003-04-16 21:08 ` Brad Laue
2003-04-17 6:47 ` Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 11:13 merv
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=1050526455.25760.100.camel@osiris.ripple.be \
--to=ripple.gentoo@ripple.be \
--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