From: "David Bryson" <david@futuretel.com>
To: Ned Ludd <solar@gentoo.org>
Cc: stephane ancelot <sancelot@free.fr>, gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Creating a gentoo based system for embedded
Date: Fri, 8 Oct 2004 15:57:53 -0700 [thread overview]
Message-ID: <20041008225753.GC27957@sledge.futuretel.com> (raw)
In-Reply-To: <1097260863.32208.20980.camel@simple>
On Fri, Oct 08, 2004 at 02:41:03PM -0400, Ned Ludd wrote:
> catalyst probably needs some work in this area. (patches welcome)
> Like the ability to create read-only cramfs/squashfs/jffs2/etc file
> systems. I think currently it's setup to spit out an ext{2,3} file.
>
actually the default embedded target spits out cramfs.
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-08 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 14:47 [gentoo-embedded] Creating a gentoo based system for embedded stephane ancelot
2004-10-07 18:43 ` Daniel Frickemeier
2004-10-07 19:04 ` Ned Ludd
2004-10-08 7:04 ` stephane ancelot
2004-10-08 13:55 ` Heath Holcomb
2004-10-08 6:55 ` stephane ancelot
2004-10-08 18:41 ` Ned Ludd
2004-10-08 22:57 ` David Bryson [this message]
2004-10-08 23:25 ` Ned Ludd
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=20041008225753.GC27957@sledge.futuretel.com \
--to=david@futuretel.com \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=sancelot@free.fr \
--cc=solar@gentoo.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