Since the definition of "embedded" vary depending on who you talk to, what is considered an embedded Linux distribution will also vary.

As other have said, you can go with distribution building tool kit, like :

• T2 SDE
• OpenEmbedded
• LinuxFromScratch
• Buildroot

You can also use any "standard" Linux distribution, which can often be customized for an embedded environment. They have the advantage of being heavily tested in their normal environment. So you can choose any of :

• Fedora (with Revisor, Instalinux)
• OpenSuse (with SuseStudio, Instalinux)
• Debian (with Reconstructor, Instalinux)
• Ubuntu (with Reconstructor, Instalinux)
• Gentoo
• Slackware (with NimbleX)
• CentOS (with Instalinux)
• gNewSense (with Builder)

Finally, you can also build your own completely, from source. In that case, BusyBox will probably be helpful since it provide a lot of functionalities and common application. To help you with that, there is the nice 3 parts series : Building Tiny Linux Systems with Busybox (part 1, part 2, and part 3)

You may want to take a look at the OpenEmbedded project. It is a meta-distribution, meaning it s more of a distribution construction kit rather than ready distribution. But using it may take effort on your part. The same applies to all embedded solutions, though.

BusyBox

BusyBox is designed to be a small executable for use with the Linux kernel, which makes it ideal for use with embedded devices. It provides a fairly complete environment for any small or embedded system.

What do you actually mean by "Embedded Linux"? It depends what you want to run on that.

For example you can use OpenWRT, but there are surely others which might better fit your purpose.

If you want to build some multimedia thing, Moblin might be a solution as well.

You might want to look at the Beagle Board.

It s not x86, but decent community of developers, and it will give a good idea how to build and run embedded Linux.(i.e. flash file system, somewhat limited RAM...) and its real cheap!

I can also recommend these two books:

Building Embedded Linux Systems and

Embedded Linux Primer

I d start by having a look at the output of the buildroot tool which comes with busybox.

You are suggesting that you want to make your own Linux distribution, this is fine but you really need to know how to use an existing one first. I am assuming you understand fully how Linux boots and works on a basic level. You ll need

• Some kind of boot media (in some cases this CAN be a rom, but usually isn t) that the firmware can boot from (in most cases the firmware on x86 is some kind of bios, or bios-like - except on things like Macs)
• A boot loader - I like to use syslinux because it s easy (and boots from a dos filesystem)
• A kernel
• A root filesystem of some kind - you can use an initramfs for this in which case, it s loaded by the bootloader and expanded at boot time. Initramfs is cool, it avoids the need for a "real" root fs or block device drivers etc (at the expense of some ram, but ram is easy).
• A C library (unless all your exes are static linked)
• Some userspace software

I d strongly recommend using an emulator (such as vmware) to test this, it reduces turnaround time a lot. A development system will need to have rather a lot of disc space, as you ll probably need to compile everything in the above list, and possibly some other tools as well (such as gcc and C library) which aren t small. Your build box will probably need to be running a proper Linux distribution.

I have done this and it s good fun, but frustrating at times (debugging can be a mission in itself)

Happy hacking :)

Busybox + LFS, Gentoo, Arch all do the job well

First to you d compile your stuff in a chroot jail on dev computer, last you don t need to compile but you need to mirror/keep your own repository because you can t get old packages from official arch repositories.

I suggest debian