From: Brendan J Simon <brendan.simon@ctam.com.au>
To: busybox@busybox.net, Linux MTD <linux-mtd@lists.infradead.org>
Subject: Minux v Ext2 on DoC2000
Date: Mon, 22 Jul 2002 12:23:53 +1000 [thread overview]
Message-ID: <3D3B6CB9.8020505@ctam.com.au> (raw)
I'm building an embedded system with an MPC8260 powerpc processor and a
DiskOnChip2000. It's quite a big embedded system (32MB DOC, 64MB RAM,
132MHz+ processor). I'm using BusyBox with uClibc and kernel version
2.4.18-pre8. I'm trying to save as much space on the DOC as possible.
I've got two partitions with identical information (well almos). One
is a failsafe backup partition.
I am currently using ext2 on the DOC as this was setup by a colleague.
I was thinking of changing to Minux as the essential minux tools are
already available in BusyBox. I already maintain BusyBox under my
configuration management system and don't want to maintain e2fsprogs as
well, unless it is necessary. It all depends on the advantages and
disadvantages beteween ext2 and minux.
Has anyone got any experience with Minux and Ext2 on a DOC2000 device
runinng a linux embedded system ? I'm sure the answer is yes :)
Could someone briefly list the main advantages and disadvantages of
minux/ext2 on such an embedded system ?
Pointers to other sources of information would also be greatly appreciated.
Thanks,
Brendan Simon.
reply other threads:[~2002-07-22 2:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D3B6CB9.8020505@ctam.com.au \
--to=brendan.simon@ctam.com.au \
--cc=busybox@busybox.net \
--cc=linux-mtd@lists.infradead.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