Hi Folks on 07.11.2010 13:07, davidMbrooke wrote: > On Sat, 2010-11-06 at 23:46 +0100, KP Kirchdoerfer wrote: .. > > "Bering-uClibc" - No argument, I hope :-) > Version - Something like "4.0-beta1" > KARCH - "i686", "i486", "geode" etc. > ImgType - "syslinux", "pxelinux", "isolinux" > Variant - I'm thinking e.g. > "std" - default variant > "ser" - serial console variant > "alix" - tailored to the ALIX platform, maybe > > The full names might therefore be e.g. > > Bering-uClibc_4.0-beta1_i686_isolinux_std.iso > Bering-uClibc_4.0-beta1_i486_syslinux_ser.tar.gz > Bering-uClibc_4.0-beta1_geode_pxelinux_alix.tar.gz > > Which combinations actually get built will depend on the > images/*/buildimage.cfg files that get created. > > Thoughts?
Are you really sure, anyone aiming for a LEAF router wants to choose between 25 kernels? The big thing in the past was that you could just use one distribution and it would either just work or else you had to build a few modules on your own, and that was pretty easy. Now I don't even have a clue which of the predefined configs I should start with and cannot just easily combine modules into what I need ( at least iot looks like that ) So for my needs, a kernel booted by grub with geode support _and_ PCI-E (yes, it exists) I will obviously go through the whole hoopla. I think it is unfortunate to call something useless, make it modular and please keep LEAF modular. Keep the distro with a default kernel, other kernels can be added, but I don't see a reason for an image just for a specific kernel version. This can be added easily by just replacing the kernel. Neither do I see a reason for many different module configurations, provide a module tarball, so the community can choose. The only thing I see as important is an initrd with serial console support. This is the one I missed most in the (far) past. Also the default distro should know as many NIC types as possible. Load them as modules, so the experienced user can take them off easily. Keep a selection of kernels ready and write a /lib/modules tree to the iso image. Als please keep the modules in the directory tree at the position the kernel developers put them. It was always a pain in the butt to find decide where they should go, the LEAF way or the Kernel way. just my 0.02 SFr. cheers Erich ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
