linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Jeff Angielski <jangiels@speakeasy.net>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Creating rootfs
Date: Mon, 11 Oct 2004 23:14:09 +0100	[thread overview]
Message-ID: <35fb2e59041011151463b2a4bf@mail.gmail.com> (raw)
In-Reply-To: <547E0D34-1BB5-11D9-909B-003065F9B7DC@embeddededge.com>

On Mon, 11 Oct 2004 14:42:40 -0400, Dan Malek <dan@embeddededge.com> wrote:
> 
> On Oct 11, 2004, at 1:22 PM, Jeff Angielski wrote:
> 
> > So how are people creating the rootfs for their embedded target these
> > days?  Busybox?  PTX?  Strip down some existing filesystem?

[ This wants to go to linuxppc-embedded from now on. ]

I use PTXdist but with a crosstool generated toolchain at the moment.
I then package up stuff that isn't in PTXdist - but you could
experiment with embedded Debian et al.

> Those are the solutions, choose whatever works best for you.

There's a whole bunch of distributions out there too. However rolling
your own is the best bet for a small filesystem if you're not buying
commercial tools at this point. Otherwise, go pay Monta, DENX, or one
of the other embedded developer supporting companies for a flashy
solution.

Jon.

  reply	other threads:[~2004-10-11 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 17:22 Creating rootfs Jeff Angielski
2004-10-11 18:42 ` Dan Malek
2004-10-11 22:14   ` Jon Masters [this message]
2004-10-11 23:19     ` Wolfgang Denk
2004-10-11 23:35       ` Jon Masters
2004-10-12  7:54     ` Marc Leeman
2004-10-12  9:20 ` Marius Groeger

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=35fb2e59041011151463b2a4bf@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=dan@embeddededge.com \
    --cc=jangiels@speakeasy.net \
    --cc=jonathan@jonmasters.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).