Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] get minimal rootfs to be even smaller
Date: Fri, 31 May 2013 17:24:35 +0200	[thread overview]
Message-ID: <51A8C0B3.2030008@juszkiewicz.com.pl> (raw)
In-Reply-To: <1370011262.8846.63.camel@phil-desktop.brightsign>

W dniu 31.05.2013 16:41, Phil Blundell pisze:
> On Fri, 2013-05-31 at 16:11 +0200, Marcin Juszkiewicz wrote:
>> Next one can be ldconfig which is ~600KB.
> 
> There's already an option to turn that off: you can set 
> USE_LDCONFIG=0 in your distro configuration (which micro does, for 
> example). Converting that to be a modern DISTRO_FEATURE would be a 
> fine thing.

Thanks for hint - may look at it next week.

> On the udev thing I guess my initial reaction would be that if you 
> want the smallest rootfs you probably don't want to be using udev at 
> all.

I just wanted to have smallest possible image without doing any distro
config changes. Think "minimal image for testing KVM" where KVM host
rootfs can be built with same setup.


  reply	other threads:[~2013-05-31 15:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 14:11 [RFC] get minimal rootfs to be even smaller Marcin Juszkiewicz
2013-05-31 14:11 ` [PATCH] udev: do not recommend pciutils/usbutils ids Marcin Juszkiewicz
2013-05-31 14:50   ` Burton, Ross
2013-05-31 14:41 ` [RFC] get minimal rootfs to be even smaller Phil Blundell
2013-05-31 15:24   ` Marcin Juszkiewicz [this message]
2013-06-11  2:06 ` Khem Raj
2013-06-11  4:27   ` Saul Wold
2013-06-11 15:03   ` Phil Blundell
2013-06-11 15:22     ` Khem Raj
2013-06-11 15:26       ` Phil Blundell
2013-06-11 15:40         ` Khem Raj
2013-06-11 15:43           ` Phil Blundell
2013-06-11 15:55             ` Burton, Ross
2013-06-11 15:36       ` Martin Jansa

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=51A8C0B3.2030008@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --cc=openembedded-core@lists.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