From: "Christian MICHON" <christian.michon@gmail.com>
To: detaolb-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
uClibc <uclibc@uclibc.org>
Subject: [Qemu-devel] ANN: DetaolB v0.3 is released
Date: Thu, 14 Jun 2007 23:13:32 +0200 [thread overview]
Message-ID: <46d6db660706141413n18610efv5b3e63ed6dae2a6a@mail.gmail.com> (raw)
DetaolB v0.3 is being released 14th,June 2007 on sf.net
=> http://sourceforge.net/project/showfiles.php?group_id=140321&package_id=155481&release_id=516140
- this is mostly a release with tons of added features
- this is mostly a proof of concept
- this is not a bugfix release
- your feedback will shape it into v1.0 someday, so please post
at the DetaolB mailing list: detaolb-devel@lists.sourceforge.net
Changelog:
==========
- it's bigger now: ~17Mb, but it's still smaller than slax-frodo :)
- you can still log using root with no password (this will change)
- kernel 2.6.21 with following patches...
* acpi, ide/atapi drivers added
* /proc/miniconfig.gz: main ideas from Rob Landley, need documentation
* aufs: another unionfs
* squashfs
* lzma vmlinux: a great thanks to Ming Ching Tiew!
* complete git patches released on sf.net
- still based on initramfs early userspace, now using switch_root
* 1st phase is using a minimal static bbox
* 2nd phase is mounting cdrom and 5 squashfs modules in aufs new root.
This is a common scheme inspired by slax, yet simplified for speed.
* 3rd phase is root switching and over to standard init phase
* main drawback: changes to the rootfs are lost if you reboot. I've
not figured out a smart way using initramfs+aufs+squashfs and
access rootfs changes from RAM...
* but it's still blazing fast even in qemu!
- 5 default squashfs modules are present and enabled
* "barebone" is busybox-1.6.0 with rootfs config files + mksquashfs
* "uclibc" is uClibc-0.9.29 + zlib
* "ncurses" is ncurses-5.2, needed for uclibc/bbox/kernel compilation
* "toolchain" is needed for C compilation
+ gcc-3.4.6
+ binutils-2.16.1
+ bash-3.2
+ bison-2.1
+ flex-2.5.33
+ make-3.81
+ misc. coreutils mandatory for uclibc/bbox/kernel compilation
* "vim" is a full vim-7.1 installation
* these modules were compiled using DetaolB v0.3, and config files
for uclibc and busybox are inside /root
* "git" is compiled but not included yet
- a 2.6.17 version of DetaolB v0.3 exist for colinux! it'll be
available on demand, or will be released anyway at version 1.0
HOW TO USE IT ?
===============
- use your favorite emulator: qemu, virtualbox, even vmplayer!
- you need to provide an hda image preformatted in ext2 if you want
to work on a non-volatile area (busybox has no more ext2fs tools ??)
- boot it, do some compilation, enjoy it
- please note it has no network capabilities
- this distro is not meant for real hardware yet (but it will be soon)
FEEDBACK, QUESTIONS, INSULTS, POSTCARDS:
========================================
christian.michon@gmail.com
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu
next reply other threads:[~2007-06-14 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 21:13 Christian MICHON [this message]
2007-06-16 5:52 ` [Qemu-devel] Re: ANN: DetaolB v0.3 is released Rob Landley
2007-06-17 22:26 ` Christian MICHON
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=46d6db660706141413n18610efv5b3e63ed6dae2a6a@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=detaolb-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--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).