From: "Buttchereit, Axel (XLsigned)" <XL@XLsigned.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] gentoo-mini-linux (2.6.X + uClibc + busybox + udev + hotplug/coldplug + *fsutils + smb/nfs+ ...) for system-setup
Date: Tue, 07 Dec 2004 18:08:01 +0100 [thread overview]
Message-ID: <41B5E371.1010907@XLsigned.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans-Werner Hilse wrote:
> Hi,
>
> On Tue, 07 Dec 2004 01:51:13 +0100
> "Buttchereit, Axel (XLsigned)" <XL@XLsigned.net> wrote:
>
>
>>Now for my (open) questions:
>> 1. "buildroot" obviously does not provide a "fully featured" root-fs
>> for
>> kernel-2.6, i. e. with udev, hotplug/coldplug.
>> Anyone out there with experience on that?
>
>
> I've managed to use the new embedded-stage1 from Gentoo to compile
> myself a basic system, which is at least what buildroot does plus lots
> of more apps. I've even managed to compile xorg (6.8.0-r4 was the only
> one that worked for me right out of the box, it's currently masked).
>
> A last tip: I wouldn't recommend to actually install busybox into your
> dev environment. Just emerge it with "emerge --buildpkgonly busybox" and
> then do a "ROOT=/your/target/root emerge -K busybox"
>
> Note that gentoo won't work as a cross compilation env, AFAIK.
>
Thanks!
I have just downloaded an experimental x86-uClibc stages1. :-)
For both my development system and my target system(s) are "x86",
I think that "chroot"-ing into my build environment (based on stage1)
should also work. i. e. re-use my current 2.6.9-kernel.
(The target kernel is also 2.6.9, but for generic i386)
Something like this should work. Right?
1. extract stage1 to "rootfs/"
2. copy modules from generic i386-kernel to rootfs/lib/modules (???, see below)
3. configure networking (rootfs/etc/resolv.conf)
4. chroot roofs /bin/bash
- ----------------------------------------------------------------
5. emerge sync
6. /usr/portage/scripts/bootstrap.sh
7. emerge system
8. customize and emerge ... udev hotplug coldplug ntfsutils busybox...
9. exit
- -----------------------------------------------------------------
10. Create "small" (32MB) ext2-filesytem on flat file "rootfs,ext2"
11. mount "rootfs.ext2" using "-o loop"
12. Copy all relevant files and folders from "rootfs/" to mounted "rootfs.ext2"
13. gzip "rootfs.ext2"
14. copy "rootfs.ext2.gz" and "bzImage" (gerneric i386-kernel) to my
PXE-Server (fli4l) and add a boot menu entry (PXEGRUB, menu.1st)
Maybe it's a better idea to emerge "gentoo-dev-sources" while "chroot"-ed
and build the kernel.
- -Axel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBteNxWr3rpUlTqH4RAjm6AJ9IO3eJDelJMnHx9uMJTBaY/DzWdQCfeC2d
u3lc2CaGAMubuvo4TpRNyeY=
=xRjb
-----END PGP SIGNATURE-----
--
gentoo-embedded@gentoo.org mailing list
next reply other threads:[~2004-12-07 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 17:08 Buttchereit, Axel (XLsigned) [this message]
2004-12-07 17:39 ` [gentoo-embedded] gentoo-mini-linux (2.6.X + uClibc + busybox + udev + hotplug/coldplug + *fsutils + smb/nfs+ ...) for system-setup Hans-Werner Hilse
2004-12-07 21:52 ` Buttchereit, Axel (XLsigned)
[not found] <1102222658.7085.32.camel@valhalla>
2004-12-07 0:51 ` Buttchereit, Axel (XLsigned)
2004-12-07 13:51 ` Hans-Werner Hilse
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=41B5E371.1010907@XLsigned.net \
--to=xl@xlsigned.net \
--cc=gentoo-embedded@lists.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