On Fri Mar 31, 2000 at 12:47:59PM -0600, Richard Jennings wrote:
>
> Is this the direction that Lineo and Blue Cat will take us? I would
> think that this is more in line with traditional embedded systems.
I work for Lineo, so I can comment a bit, though I'm not at all
an official spokesperson or anything...
Using the kernel's "init=/bin/foo" command line is workable, if you are not
planning on doing any multiprocess things, and if you are willing to live with
the many problems this can produce. In really tight spots, this can do the job
but for most situations this is not acceptable. Sometimes I have had
applications where I made /sbin/init be a shell script and that was perfectly
sufficient. It really depends on the application.
Embedix Linux uses the init implementation (and many of the other tools)
provided by BusyBox (http://busybox.lineo.com/) and uses /etc/inittab to
specify what programs to start up, what order to start them in, etc. BusyBox
init's /etc/inittab is not comptable with sysvinit's /etc/inittab, since
BusyBox lets you specify which VT to start programs on (which is very nice
since you can usually avoid using a getty). Anyways, using BusyBox + ash +
elvis-tiny + iproute + GNU libc + the linux kernel makes for a excellent base
for most embedded Linux applications. If GNU libc is a bit too big for your
application, try out NewLib (the embedded C library) and it may help,
Hope this is helpful,
-Erik
--
Erik B. Andersen Web: http://www.xmission.com/~andersen/
email: [EMAIL PROTECTED]
--This message was written using 73% post-consumer electrons--
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
