From: "Christian MICHON" <christian.michon@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: uclibc@uclibc.org, detaolb-devel@lists.sourceforge.net,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: ANN: DetaolB v0.3 is released
Date: Mon, 18 Jun 2007 00:26:25 +0200 [thread overview]
Message-ID: <46d6db660706171526r7a05311cjebe84099e4fcb4c7@mail.gmail.com> (raw)
In-Reply-To: <200706160152.43073.rob@landley.net>
On 6/16/07, Rob Landley <rob@landley.net> wrote:
> On Thursday 14 June 2007 17:13:32 Christian MICHON wrote:
> > * /proc/miniconfig.gz: main ideas from Rob Landley, need documentation
>
> Actually, there was documentation for this before there was code. You can
> follow my development of the concept:
> (...)
I'm sorry Rob, I meant I need to document the changes I brought to your
original idea.
Download the iso, and once it's finished booting inside qemu, log in as
root and do this:
vi /proc/miniconfig.gz
you'll understand what I meant by not having documented (my changes)...
> > + gcc-3.4.6
>
> Heh. You're building qemu with your toolchain, aren't you? :)
nope, not yet. the reason for this gcc version is also due to colinux
requirements (I need a vmlinux api compatible with gcc-3.4.6)
I actually intend to deliver a few toolchains soon. But qemu is
definitely going in as a loadable module soon after Xwindows will
be in. :)
> "One of my most productive days was throwing away 1000 lines of code."
> - Ken Thompson.
excellent...
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu
prev parent reply other threads:[~2007-06-17 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 21:13 [Qemu-devel] ANN: DetaolB v0.3 is released Christian MICHON
2007-06-16 5:52 ` [Qemu-devel] " Rob Landley
2007-06-17 22:26 ` 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=46d6db660706171526r7a05311cjebe84099e4fcb4c7@mail.gmail.com \
--to=christian.michon@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).