From: paul_wu@wnexus.com.tw
To: Tommy Reynolds <reynolds@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Which embedded linux is better for being a router? eCos? uclinux?
Date: Mon, 25 Nov 2002 09:01:05 +0800 [thread overview]
Message-ID: <48256C7C.0005853D.00@TWHSZDS1.WISTRON.COM.TW> (raw)
CPU will be MIPS. Does uclinux support multi-processes? Or there is 3rd choice
for such embedded Linux?
Paul
Tommy Reynolds <reynolds@redhat.com> on 2002/11/22 11:25:49 PM
To: Paul Wu/WNI/Wistron@Wistron
cc: linux-kernel@vger.kernel.org
Subject: Re: Which embedded linux is better for being a
router? eCos? uclinux?
This document is classified as Normal
Overcoming an impressive lethardy, paul_wu@wnexus.com.tw mumbled:
> Try to make a router running a embedded linux OS, but don't know select which
> one is better, eCos? uclinux?
> Does anyone have such experiences?
By far the easiest solution is to use ordinary Linux on a really old,
cheap PC, or a PC-on-a-board.
eCos can be built with the smallest memory and resource footprint of
any of the other techniques, but may not already support the Ethernet
cards or other devices you need: eCos just doesn't have the sheer
number of device drivers as does Linux.
uCLinux would work well enough, as it's intended for cheap-as-dirt
CPU's that lack an MMU. The features it lacks (there is no "fork()"
only "vfork()") can be easily worked around but your application
software may need tweaking.
Without knowing your engineering requirements it is impossible to say
what you need.
next reply other threads:[~2002-11-25 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 1:01 paul_wu [this message]
2002-11-25 2:23 ` Robert Love
2002-11-25 9:58 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 4:29 paul_wu
2002-11-22 15:25 ` Tommy Reynolds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48256C7C.0005853D.00@TWHSZDS1.WISTRON.COM.TW \
--to=paul_wu@wnexus.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=reynolds@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®