From: "H. Peter Anvin" <hpa@zytor.com>
To: Matt Ranon <mranon@javadevices.com>
Cc: linux maillist <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE][PATCH] Kcli - Kernel command line interface.
Date: Mon, 23 Apr 2007 15:06:13 -0700 [thread overview]
Message-ID: <462D2DD5.7000701@zytor.com> (raw)
In-Reply-To: <875184.9239.qm@web88101.mail.re2.yahoo.com>
Matt Ranon wrote:
> The Jem team is pleased to announce the release of Kcli, an in-kernel command line interface. Kcli is intended for a special class of embedded Linux applications. The Linux kernel has become the defacto standard OS for embedded applications. This means that Linux is getting bent in some ways that may appear strange to some. One of these ways, is embedded applications that do not use user space. User space consists of a statically linked, one line program, that simply sleeps forever, transforming Linux into a classical embedded RTOS. VxWorks developers will understand what we are talking about, and they may recall how much they depend on the VxWorks shell. Kcli attempts to meet the need for a shell for this class of embedded Linux applications.
We already have that, it's called initramfs; you can use either busybox
or klibc ash in this space, and no need to run it in kernel space.
Running this kind of crap in kernel space is lunacy in the extreme.
-hpa
next prev parent reply other threads:[~2007-04-23 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 21:31 [ANNOUNCE][PATCH] Kcli - Kernel command line interface Matt Ranon
2007-04-23 22:06 ` H. Peter Anvin [this message]
2007-04-23 23:33 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2007-04-24 1:12 Matt Ranon
2007-04-24 2:35 ` Satyam Sharma
2007-04-24 12:36 ` Tilman Schmidt
2007-04-24 14:34 ` Sam Ravnborg
2007-04-28 17:44 ` Matt Mackall
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=462D2DD5.7000701@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mranon@javadevices.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