All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RFC: poky-tiny: init procedure
Date: Sat, 16 Jun 2012 09:53:25 +0100	[thread overview]
Message-ID: <4FDC4985.6040405@r-finger.com> (raw)
In-Reply-To: <4FDBC1FC.3050008@linux.intel.com>

Hi Darren,

On 16/06/12 00:15, Darren Hart wrote:
> I dont think
> Tim's comment was wrong there. Of course "big system" is subjective, to
> me that's anything over 4 MB of storage and 8MB of RAM, for Tim, that's
> 1 MB of RAM.

Indeed, I was thinking of something like the OpenRisc board
(http://opencores.org/shop,item,9), which is a 1MB flash / 32MB RAM,
which I now realize is a huge system by both your and Tim standards :)


> Your point on eliminating shell scripts is a good one though.

In my experience scripts tend show fairly visibly on poky bootchart,
that's all.

I was thinking that for a small system, where I know exactly what I
want, the rc.local file could probably be fairly easily replaced with a
custom config-less spawner written in C. If done with a view to permit
easy modification of the .c source file, it would not be any more hassle
customizing than tweaking a shell script. But you would loose the
ability to tweak config over ssh, which is a significant trade off for
development / debugging, so I think the rc.local is a better default
approach (and alternatives can always be dropped in using the
ALTERNATIVES mechanism anyway).

I think the busybox sysvinit is probably worth experimenting with to get
some idea what size of a system it would be a viable alternative for the
default, and document that somewhere.

Tomas


  reply	other threads:[~2012-06-16  8:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  0:33 RFC: poky-tiny: init procedure Darren Hart
2012-06-14  1:09 ` Tim Bird
2012-06-14  1:20   ` Darren Hart
2012-06-14  2:55     ` Darren Hart
2012-06-14  7:11 ` Tomas Frydrych
2012-06-14 21:09   ` Darren Hart
2012-06-15  6:31     ` Tomas Frydrych
2012-06-15  7:05       ` Thomas Petazzoni
2012-06-15 23:04         ` Darren Hart
2012-06-15 19:49       ` Tim Bird
2012-06-15 21:26         ` Tomas Frydrych
2012-06-15 23:15           ` Darren Hart
2012-06-16  8:53             ` Tomas Frydrych [this message]
2012-06-15 21:10   ` Tim Bird
2012-06-15 23:21     ` Darren Hart
2012-06-18 11:50     ` Richard Purdie

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=4FDC4985.6040405@r-finger.com \
    --to=tf+lists.yocto@r-finger.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.