Hi All,
Thanks for all your comments so far.
Of interest, elinux.org has some "real" data about very small
linux versions.
From what I see it is VERY hard to determine what RAM is really needed
by the kernel??!!
So any cleanup and shrink effort could be quite a large effort?
That said, we REALLY need to have available a BARE MINIMUM kernel that
is clearly documented so the MINIMUM requirements to run any sort of linux
can be easily determined. I am NOT planning to become the focal point
person for such an effort, but it is probably worth being said :).
Further comments welcome.
warm regards,
John
On Mon, 13 Oct 2008, bifferos wrote:
> --- On Sun, 12/10/08, RHS Linux User <[EMAIL PROTECTED]> wrote:
>
> > From: RHS Linux User <[EMAIL PROTECTED]>
> > Subject: Re: [OpenWrt-Devel] Smallest Linux
> > To: "OpenWrt Development List" <openwrt-devel@lists.openwrt.org>
> > Date: Sunday, 12 October, 2008, 11:26 AM
> >
> > I am very much looking forward to anyone's further
> > comments and
> > suggestions.
>
> I can only suggest looking at NetBSD instead if memory and flash is
> really tight. You'll do better than with OpenWrt (if you leave aside
> the lack of tiny dhcp client daemon and 'micro' versions of other
> useful utils), but you still won't get anywhere near what you want.
> Here's some info on running NetBSD on an Edimax router:
> http://linux-adm5120.sourceforge.net/netbsd/
>
> Bear in mind that LwIP (http://www.sics.se/~adam/lwip/), a
> tcp/ip stack for embedded systems itself takes up 'tens of kilobytes'
> of RAM, so how you do with 50KB will depend on whether you need
> tcp/ip or not presumably.
>
> Also, the discussion on the OpenWrt list focuses around a complete
> OpenWrt installation, whereas you can just use a kernel. There was
> an interesting article in Linux Journal explaining how to write
> an ftp client as a kernel module:
> http://www.linuxjournal.com/article/7660
>
> One could simply write one's application by inserting one's own
> code into the C entry point in the kernel, but I think there
> would need to be a lot of money in it to make it worthwhile.
>
>
>
>
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
