From: "Christian MICHON" <christian.michon@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: detaolb-devel@lists.sourceforge.net, uclibc@uclibc.org,
qemu-devel@nongnu.org, Cedric Hombourger <chombourger@gmail.com>
Subject: Re: [Qemu-devel] ANN: DetaolB v0.4 is released
Date: Thu, 5 Jul 2007 22:28:30 +0200 [thread overview]
Message-ID: <46d6db660707051328p367b7701l928997f55757d5c4@mail.gmail.com> (raw)
In-Reply-To: <200707051523.36843.rob@landley.net>
On 7/5/07, Rob Landley <rob@landley.net> wrote:
> What's the difference between deltaolb and Firmware Linux, anyway? I'm still
> curious about this.
a few differences, quite minor actually (that's why I said in the past we
shared many common goals :-) )...
I actually started this in 2002, but then hit many bugs in uclibc. In the end,
I actually used a trimmed LFS approach, using zisofs. My bootable env
then was ~45Mb. At that time, buildroot was also starting... I lacked of
time to work on it.
The biggest difference today is that your firmware is based on automation
or Makefiles, whereas I still use a LFS type of approach. I first build a
static minimal toolchain with a static busybox: all native, no cross
compilation. Then I chroot in it, compile uclibc, busybox, the toolchain.
The rest is obvious, but quite manual. I really should do Makefiles...
The other difference is that I base detaolb on aufs/squashfs (I do not
think you passed that stage yet, if I recall not all the archs you're
targetting can take this). That's today's improvement over the stuff
I did in 2002 using zifofs.
> Oh, by the way, the Fedora for Arm project is also building natively on arm,
> but they got some fast ARM hardware and stuck lots of DRAM and hard drive
> space onto it rather than using QEMU.
in 2003/2004, I also worked on porting linux to an Ipaq h2215. I actually then
used buildroot arm precompiled, and managed to chroot in it using nfs over
usb. quite cool, and the speed was better than qemu today. It was just a
400Mhz Xscale.
I'm still interested in your cross compiling tutorial. I believe we all are :)
If I start putting too many archs in the picture, I believe DetaolB will be
redundant with Firmware. This is not intended. Originally I wanted to
share the portable x86 env I carry on my usb key. Some of you asked
for a sparc32 port. I'll complete this one at least (I'm progressing quite
fast on it).
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu
prev parent reply other threads:[~2007-07-05 20:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 23:58 [Qemu-devel] ANN: DetaolB v0.4 is released Christian MICHON
2007-06-30 7:47 ` Blue Swirl
2007-06-30 10:36 ` Johannes Schindelin
2007-06-30 10:51 ` Thiemo Seufer
2007-06-30 12:07 ` Christian MICHON
2007-06-30 17:15 ` Blue Swirl
2007-07-10 17:34 ` Rob Landley
2007-07-10 18:30 ` Blue Swirl
2007-07-10 19:42 ` Rob Landley
2007-07-11 11:17 ` Blue Swirl
2007-07-11 13:34 ` [Detaolb-devel] " Christian MICHON
2007-07-11 14:20 ` Christian MICHON
2007-07-11 17:33 ` Rob Landley
2007-07-11 20:20 ` Christian MICHON
2007-07-11 17:38 ` Rob Landley
2007-07-11 20:26 ` [Detaolb-devel] " Christian MICHON
2007-06-30 12:10 ` Christian MICHON
2007-07-04 18:30 ` Christian MICHON
2007-07-04 18:54 ` Blue Swirl
2007-07-04 19:45 ` Christian MICHON
2007-07-04 20:18 ` Blue Swirl
2007-07-04 20:30 ` Christian MICHON
2007-07-04 20:52 ` Blue Swirl
2007-07-04 21:04 ` Christian MICHON
2007-07-05 12:41 ` Christian MICHON
2007-07-04 20:25 ` Andreas Färber
2007-07-04 20:32 ` Christian MICHON
2007-07-06 15:07 ` Rob Landley
2007-07-04 19:50 ` Cedric Hombourger
2007-07-04 19:54 ` Cedric Hombourger
2007-07-10 20:32 ` Bernhard Fischer
2007-07-10 20:36 ` Christian MICHON
2007-07-04 20:11 ` Christian MICHON
2007-07-05 19:23 ` Rob Landley
2007-07-05 20:28 ` Christian MICHON [this message]
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=46d6db660707051328p367b7701l928997f55757d5c4@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=chombourger@gmail.com \
--cc=detaolb-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=uclibc@uclibc.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).