From: craig@hollabaugh.com (Dr. Craig Hollabaugh)
To: Wolfgang Denk <wd@denx.de>
Cc: brian.auld@adic.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Bare bones filesytem using Karim's book
Date: Tue, 3 Jun 2003 10:50:23 -0600 (MDT) [thread overview]
Message-ID: <20030603165023.460CB27D97@chuy.ouraynet.com> (raw)
In-Reply-To: <20030603151233.92CABC5492@atlas.denx.de>
> Also, the approach to strip down a general purppose distribution
> (even an embedded one) does not make much sense - as I wrote before,
> you better design your system bottom up by starting with an empty
> filesystem and just adding the really required components. Where
> "required" means "required to perform some task you defined in your
> project specification".
I agree, here's how you start. After kernel initializes everything it
executes init, so what libraries does init require?
holla@gibson[502]: ldd /sbin/init
libc.so.6 => /lib/libc.so.6 (0x4001a000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Well that is if you're running init and want libc. ldd bash, sash,
ash, busybox whatever.
Craig
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-03 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 13:55 Bare bones filesytem using Karim's book brian.auld
2003-06-03 15:12 ` Wolfgang Denk
2003-06-03 16:50 ` Dr. Craig Hollabaugh [this message]
2003-06-03 16:00 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 15:28 brian.auld
2003-06-02 21:18 brian.auld
2003-06-02 21:54 ` Wolfgang Denk
2003-06-02 23:56 ` Karim Yaghmour
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=20030603165023.460CB27D97@chuy.ouraynet.com \
--to=craig@hollabaugh.com \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).