On Thu, 22 Jan 2009 23:05:17 +0100 Erik Schanze <schan...@gmx.de> wrote:
> > Running emdebian-tools within a chroot can cause numerous > > difficulties, especially if you try to create a chroot within a > > chroot. These problems are not unique to emdebian-tools - it can be > > difficult to create a Debian debootstrap within an existing > > debootstrap. > > > > If your desktop is Debian Etch, you have to install Lenny to get > emdebian-tools. So I tried a chroot as described in emsetup(1). > Is this way not save? It's not fully tested and prone to problems outside the direct control of the emdebian-tools package. I'll add the advice on /etc/hosts to the manpage but I don't think it's right for emsetup to go meddling with /etc/hosts, even inside a chroot (if it can even detect that it is inside a chroot). Actually, saying that you're running Etch may explain why you haven't had the updates to emdebian-tools 1.4.14 - you may need to tweak the /etc/apt/sources.list.d/emdebian.sources.list to look for unstable if it doesn't already. I'm not even sure if you have any cross-building toolchains available (not that you need them personally) with your setup. Please can you send me the output of 'apt-cache policy' ? reportbug should have asked for this information when you submitted the original bug. What tool did you use? (If you say 'reportbug-ng' I think I'll scream.) http://www.linux.codehelp.co.uk/serendipity/index.php?/archives/119-reportbug-ng-unfit-for-purpose-Absolutely..html Using Etch as a base is a completely untested situation (another one). > You mean one could build every package that is needed for debootstrap > with emdebian-tools and do debootstrap afterwards? Is there any > documentation available? http://www.emdebian.org/docs/howto.html (Except that you're using the emdebian patches to native build, not cross-build. See also #492374.) Be aware: It is a VERY long process, but yes, essentially what you would need to do is: 1. Solve problems outlined in #492374 and report back on any other fixes necessary. 2. use em_autobuild from emdebian-tools 1.4.14 (earlier versions are extremely unlikely to work) 3. create a local repository (I'd recommend reprepro) into which the packages can be included. 4. pass that repository to emsandbox using the machine:variant support. debootstrap is very unlikely to work with Emdebian Crush packages, even native packages. The replacement of coreutils with an active busybox, removal of perl, removal of manpages, replacement of update-alternatives and install-info and many other changes as-yet undiscovered. There is a good reason why Emdebian Crush 1.0 will only be released on ARM. ;-) It took me many, many months to get Crush available for ARM and until I can make a whole load of changes in Debian (which in turn means after the Lenny release) it may take roughly the same amount of time to port Crush to another architecture (other than armel). If you would like to prove me wrong, be my guest! I'll do what I can to help. :-) > > Sorry. There is no prospect of providing i386 packages any time soon > > because i386 is not a priority architecture for embedded devices. > > Not yet, but with Intel-Atom it will come. Perhaps as arch "lpia". I disagree - the Intel-Atom is not currently a suitable target for Emdebian Crush, you need to look at Emdebian Grip which is designed for netbook devices like the Acer Aspire1. Are you saying that even smaller devices (true handhelds and smartphones) will be based on the Atom? Before Emdebian could support lpia, Debian would need changes that I have no idea how to implement at this time. Could be fun though. I would strongly recommend that you do not consider building Crush for a device like an Acer Aspire1 or Eee PC. If you have a different device in mind, let me know. I'm running Emdebian Grip on an Acer Aspire1 - although there are problems with Grip right now, the problems are truly minor in comparison with using Crush. http://lists.debian.org/debian-embedded/2009/01/msg00074.html > What could I do to get a minimal RootFS for i386 (Intel-Atom)? Use Emdebian Grip, with the provisos above. It's probably easiest to simply use Debian-Installer with one of the latest Lenny pre-releases based on net-installer D-I beta1 (or 2 if it is around) and use the pre-seeding instructions: http://www.emdebian.org/grip/#preseeding > Is there any good documentation to build custom RootFS with emdebian? The documentation reflects the problems outlined in the email I just sent in response to your private enquiry. I wrote most of the pages on the emdebian website and I am fully aware that doing this means that the current website is desperately in need of updates to make it more useful to people other than myself. http://www.emdebian.org/emdebian/customisation.html http://www.emdebian.org/emdebian/machinevariants.html (Those are reliant on using ARM.) Grip documentation is at: http://www.emdebian.org/grip/index.html -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
pgpWONv9wbaqy.pgp
Description: PGP signature
