public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hans-Werner Hilse <hilse@web.de>
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, 7 Dec 2004 14:51:54 +0100	[thread overview]
Message-ID: <20041207145154.2aa3f7e3.hilse@web.de> (raw)
In-Reply-To: <41B4FE81.2040502@XLsigned.net>

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).

>   2. ntfsutils, smb, ... are not available in current "buildroot".
>      Anyone out there that has integrated this into "buildroot"
>      already?(or rather compiled/linked against uClibc manually)

Try to use Gentoo, it really works quite well. I've managed to compile
samba (even the server) and ntfsprogs with the default ebuilds. The NFS
support mentioned in the subject relies on the kernel as said in recent
thread here ("can't emerge nfs-utils") but can work, too. Userspace NFS
doesn't seem to work yet because of not-glibc-like rpc support in
uclibc.

>   3. "buildroot" uses its own "package management" for downloading and
>      compiling of sources.
>      Is it possible to benefit from "gentoo-portage" and do (a kind
>      of) cross-compiling and linking against uClibc?

Yes, you've got a lot more build scripts. If they work is another
question. And I personally found it easier to use Gentoo for all this.
When building your final filesystem, you should make a copy of the build
system and delete everything that isn't needed. You can, on the other
hand, build packages when emerging and then use "ROOT=/your/target/root
emerge -K package" for everything you need.

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.

HWH

--
gentoo-embedded@gentoo.org mailing list


  reply	other threads:[~2004-12-07 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1102222658.7085.32.camel@valhalla>
2004-12-07  0:51 ` [gentoo-embedded] gentoo-mini-linux (2.6.X + uClibc + busybox + udev + hotplug/coldplug + *fsutils + smb/nfs+ ...) for system-setup Buttchereit, Axel (XLsigned)
2004-12-07 13:51   ` Hans-Werner Hilse [this message]
2004-12-07 17:08 Buttchereit, Axel (XLsigned)
2004-12-07 17:39 ` Hans-Werner Hilse
2004-12-07 21:52   ` Buttchereit, Axel (XLsigned)

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=20041207145154.2aa3f7e3.hilse@web.de \
    --to=hilse@web.de \
    --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