Mike Frysinger wrote: > On Friday 21 July 2006 17:03, Christopher Friedt wrote: >>Is there a published list of boards and their status for embedded gentoo?
> we dont support boards at the moment, just architectures > getting a bsp up and running is left as an exercise for the end user ;) >>Would anyone be interested in polishing up a gentoo embedded port onto >>that platform with me? > WRT54G ? that's mipsel right ? we've got mipsel/uclibc and mipsel/glibc > running ... >>Has anyone published a list of minimum or suggested specs for devices in >>terms of ram / flash ? > again, see previous comment ... > as you can see, Gentoo/embedded is at the 'for developers' stage ... it could > use a lot of work before being ready 'for users' and doing mini bsp releases > for like the nslu2/wrt54g/what-have-you ... if you really feel like getting > down and dirty, this is an area that is wide open at the moment ;) > -mike Well, I agree, all of this is a good idea and 'wide open'. I'm in the process of customizing a firewall, with several DMZs to put up embedded systems for outside developers to access and control various mechanical and imaging systems. I have an old TS-5500, based on AMD 133 MHz 586 PCMCIA, which is available. Besides using an x86 for a baseline, as an intro SBC to embedded gentoo, would ease the transition from workstation/server gentoo to embedded gentoo. After folks get use to embedded gentoo on an x86 platform, then they can diverge into a second embedded platform (arm, mips, sh, blackfin, ppc)..... Softening the upward migration path to so that other can migrate to embedded gentoo contributors is a good idea. I'd be receptive to purchasing/hosting several systems in this (embedded)DMZ for folks to play with, especially if there is a 'turnkey' packaging where all I have to do is re-flash a SD/CF card, modify configs and boot up the system, in the event something goes wrong. There would also have to be an ACL (Access Control List) such that I could regulate who gets access to these boards. I could use some suggestions on iptables rules for this (embedded) DMZ. I have spoken to several folks in the past that have tried this, and maintaining security is always a challenge. So a limited ACL in the beginning until the security mechanisms mature, is a prudent step. thoughts? James -- [email protected] mailing list
