On Tue, 3 Feb 2009 09:15:26 +0100 "Hoefle Marco" <Marco.Hoefle@nanotronic.ch> wrote: > >> our customer is using uClinux from a linux distributer charging indirectly > >> licensing fees for things they took from uClinux.org and other community > >> developed stuff. Furthermore, their drivers are buggy and not well tested. > >> Thus I thought emdebian might be a good alternative with well tested drivers > >> and packages. Thus I want to make a emdebian crush demo > >> on their board they are currently using (based on a Xscale 270PXA, 16 MByte > >> Flash and 64 MByte RAM). The problem is that I am not familiar with debian > >> packages (we use Redhat). Which is where the problems started. I think I can see where you've gone wrong now. *There is NO upgrade path from Debian to Emdebian Crush* i.e. you cannot install Debian onto an ARM board and then expect it to upgrade to Crush. You must build a root filesystem for Crush and install it *instead* of Debian. To build packages for Crush, you need to be running Debian on your desktop / powerful laptop. Emdebian Grip is different - you can install Debian and then migrate to Grip (that is how Grip works with the Debian Installer). Crush is VERY different - there is currently no support for migrating from Debian to Crush because the release freeze for Debian Lenny has prevented any of the fixes being introduced into Debian to allow such a migration, partially due to an inability to update the version of busybox used in Debian right now. > >> What I did for the demo so far: > >> - I installed debian lenny and the emdebian tools using the repositories > >> http://build.emdebian.org/emdebian/ unstable main > >> http://www.emdebian.org/debian/ unstable main WRONG. I didn't notice this at first, you do NOT use the emdebian.org/emdebian repositories except AFTER installation onto the board. www.emdebian.org and buildd.emdebian.org are the same machine. emdebian-tools does all this for you, correctly, anyway. I don't understand why you thought it necessary to tinker with the sources lists in the first place, let alone why you added the emdebian.org/emdebian repository. Please file a bug against buildd.emdebian.org indicating where the website can be improved to stop this happening again. > >> And a few other things are not clear to me: I saw that uboot > >> is referenced on the emdebian website. After the emdebian crush flow is > >> there a kernel and a file system image which can be loaded with uboot? You need to provide the kernel (and modules) yourself. There are no kernels for Emdebian Crush at this time. > >> Is there a step by step document available on how to install emdebian crush > >> on a emedded system with little storage resources? http://www.emdebian.org/docs/howto.html If sections are unclear or misleading, please file bugs against buildd.emdebian.org > >From my point of view, emdebian needs a little work to do all you want to do. > It is not so much I want, just a little emdebian demo ;-). Emdebian isn't at that stage right now. The learning curve is steep and it has to start with knowing how Debian works. Emdebian *is* Debian, you do need to be familiar with Debian before Emdebian is likely to make any sense. That won't change until the next Debian release *after* Lenny. -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
Attachment:
pgpCJKZg9WRXU.pgp
Description: PGP signature