Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] busybox, hardcoded config
Date: Sat, 25 Dec 2010 23:03:08 +0100	[thread overview]
Message-ID: <87ipyhpl2b.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20101224072947.17101by6ka661utc@www.home.zuerker.org> (Heiko Zuerker's message of "Fri, 24 Dec 2010 07:29:47 -0600")

>>>>> "Heiko" == Heiko Zuerker <heiko@zuerker.org> writes:

Hi,

 >> Could you detail why that specific behaviour on NFS is causing
 >> problems ?

 Heiko> (A rather lengthy explanation)

 Heiko> My situation is a bit different than most people using buildroot.
 Heiko> I'm trying to use buildroot for a full blown, security focused distribution.
 Heiko> Since Devil-Linux is already well established, I have to reproduce the
 Heiko> current features.

 Heiko> Busybox is only used as a static binary in the initramfs to initialize
 Heiko> the system, find the configuration and the distribution media.

 Heiko> We're using the full blown glibc and busybox can't be statically
 Heiko> compiled if nfs support is on, since it needs it for dns resolution.

So your problem is basically that you're trying to do static linking
with glibc, which is known to not work very well, and is considered
deprecated by the glibc developers
(http://www.akkadia.org/drepper/no_static_linking.html). Wouldn't it
make more sense to use uclibc for the initramfs, or alternatively use
dynamic linking?

 Heiko> This may cause other people more issues. I'm sure not everybody can
 Heiko> used the provided config files and has to do some minor adjustments,
 Heiko> but still relies on some of the auto-config features.

Yes, I don't like extra (inconsistent) magic.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-12-25 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 13:33 [Buildroot] busybox, hardcoded config Heiko Zuerker
2010-12-24  7:52 ` Thomas Petazzoni
2010-12-24 13:29   ` Heiko Zuerker
2010-12-25 22:03     ` Peter Korsgaard [this message]
2010-12-26 14:08       ` Heiko Zuerker
2010-12-27 15:28         ` Peter Korsgaard
2010-12-27 15:34           ` Heiko Zuerker
2010-12-27 15:46             ` Peter Korsgaard
2010-12-24 13:22 ` Peter Korsgaard

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=87ipyhpl2b.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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