Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Lund <mgl@doredevelopment.dk>
To: openembedded-devel@openembedded.org
Subject: Re: Pull request from DoréDevelopment - New: Micro distro/image
Date: Sat, 02 May 2009 11:29:25 +0200	[thread overview]
Message-ID: <49FC1275.7080202@doredevelopment.dk> (raw)
In-Reply-To: <200905020946.08201.marcin@juszkiewicz.com.pl>

On 02-05-2009 09:45, Marcin Juszkiewicz wrote:
> Dnia piątek, 1 maja 2009 o 14:21:35 Martin Lund napisał(a):
>    
>> The "Micro" distribution/image is created because we feel that there
>> is a need for a truly tiny and clean distro and image definition in
>> OE for those users out there that needs a very tiny Linux rootfs with
>> virtually nothing installed except busybox, libc, udev, and a few
>> init scripts. On arm the jffs2 image size is only 1 MB (uclibc
>> based). No bloat allowed.
>>      
>
> You already mentioned that you have a bloat in that image - udev is not
> required as busybox-mdev can also populate /dev/ with nodes.
>
> Regards,
>    
Its still work in progress -  thats why I wrote the following in my wiki 
todo list ;)

* Replace udev with mdev (a big maybe, depends on mdev maturity)

Initially udev is the one thing that I dont want to compromise too much 
on functionality - its important that the device nodes are created 
correctly. Disregarding code size, the real downside by picking mdev is 
that the implementation supports a different rule base (at least that 
was so last time I checked - be it some time ago and back then it was 
also quite buggy).

Im going to give mdev a new review soon -  most likely I will go with 
mdev in the end for the sake of keeping things simple and tiny 
regardless of its limitations.

Actually I plan to review the whole busybox configuration to make sure 
its fit.

Br, Martin


  reply	other threads:[~2009-05-02  9:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 12:21 Pull request from DoréDevelopment - New: Micro distro/image Martin Lund
2009-05-01 12:39 ` Michael 'Mickey' Lauer
2009-05-01 12:49 ` Philip Balister
2009-05-01 13:00   ` Michael 'Mickey' Lauer
2009-05-01 13:54   ` Martin Lund
2009-05-01 17:24     ` Philip Balister
2009-05-01 21:30 ` Leon Woestenberg
2009-05-01 21:33   ` Philip Balister
2009-05-01 22:12     ` Leon Woestenberg
2009-05-01 21:37 ` GNUtoo
2009-05-01 21:44 ` Otavio Salvador
2009-05-01 23:07   ` Martin Lund
2009-05-02  7:45 ` Marcin Juszkiewicz
2009-05-02  9:29   ` Martin Lund [this message]
2009-05-02 18:14 ` Marco Cavallini
2009-05-03 12:26   ` Leon Woestenberg
2009-05-03 17:33     ` Martin Lund
2009-05-03 17:35       ` Philip Balister
2009-05-03  4:39 ` Pull request from Dor?Development " Denys Dmytriyenko
2009-05-03 12:24   ` Leon Woestenberg
2009-05-04  2:06     ` Denys Dmytriyenko
2009-05-04  7:52 ` Pull request from DoréDevelopment " Holger Schurig

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=49FC1275.7080202@doredevelopment.dk \
    --to=mgl@doredevelopment.dk \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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