public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jerry McBride <mcbrides9@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] initng or runit?
Date: Tue, 22 Aug 2006 20:06:27 -0400	[thread overview]
Message-ID: <200608222006.27412.mcbrides9@comcast.net> (raw)
In-Reply-To: <20060821153508.6b32e585.hilse@web.de>

On Monday 21 August 2006 09:35, Hans-Werner Hilse wrote:
> Hi,
>
> On Sun, 20 Aug 2006 22:01:24 -0400 Jerry McBride
>
> <mcbrides9@comcast.net> wrote:
> > Would some kind soul save me a bit of research time? Which of the two
> > alternative init schemes are faster, initng or runit?
>
> That most likely doesn't depend on the init process. Most time is
> consumed by the numerous (re-)starts of /bin/sh, i.e. bash in most
> cases, through all the init scripts.
>
> If you're about to play with an embedded device like machine and boot
> time really matters, I'd suggest writing the system setup tasks (rcS)
> in pure C. If you want to save a few shell startups, you might as well
> use /etc/inittab and sysvinit. Sysvinit, initng, runit or minit (which
> I like best) doesn't really matter for timing. That time is wasted in
> other places.
>
> For a VDR (digital PVR) machine, I'm using busybox' reduced sysvinit
> clone. Works like a charm, from boot till VDR running it's about 30sec.
> You might get a few more seconds for reimplementing system setup in
> pure C, as suggested. AFAIK, e.g. the Linksys Linux firmware does that.
> You might consider using their program as a template..
>

We've settled upon initng and fcache. Between the two, I can boot a "fully 
loaded" laptop in under 13 seconds. That's pretty impressive.

Thanks for the tips and info.

Cheers... Jerry.


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-08-23  0:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21  2:01 [gentoo-user] initng or runit? Jerry McBride
2006-08-21  8:36 ` Neil Bothwick
2006-08-21  8:51   ` [gentoo-user] " Alexander Skwar
2006-08-21  9:27     ` Neil Bothwick
2006-08-21 13:35 ` [gentoo-user] " Hans-Werner Hilse
2006-08-23  0:06   ` Jerry McBride [this message]
2006-08-23  1:58     ` Thomas Kear
2006-08-23  3:23       ` Dale
2006-08-23  7:12       ` Mrugesh Karnik
2006-08-23 14:17       ` Hans-Werner Hilse
2006-08-24  0:07         ` Jerry McBride
2006-08-23 22:42 ` Daniel Iliev
2006-08-24  0:04   ` Jerry McBride
2006-08-24  1:28     ` [gentoo-user] [OT] " Daniel Iliev
2006-08-24 21:48       ` Jerry McBride

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=200608222006.27412.mcbrides9@comcast.net \
    --to=mcbrides9@comcast.net \
    --cc=gentoo-user@lists.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