Bug 86520 - Enhancement: eCos needs a shell
Enhancement: eCos needs a shell
Status: CLOSED WONTFIX
Product: eCos
Classification: Retired
Component: Other (Show other bugs)
CVS
All Linux
low Severity medium
: ---
: ---
Assigned To: Jonathan Larmour
Jonathan Larmour
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-24 20:26 EST by Jonathan Larmour
Modified: 2007-03-27 00:01 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-20 12:22:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jonathan Larmour 2003-03-24 20:26:51 EST
This is an enhancement requested at FOSDEM 2003. Here's an excerpt from a mail
message about this:

 * A shell! This has come up before and we kept telling people it's
inappropriate without processes, safe thread control (can you _really_ just
suspend/restart threads?), and frequently no filesystem. But people said we
should consider it as infrastructure so that _they_ can add shell stuff that
they want to.

Someone mentioned dash as a starting point... see
<http://v2dash.hypermart.net/>... but looking at it that can't have been right.
More relevant may be that it gives an idea of the commands a custom shell we
supplied _could_ provide.

A second but much more interesting idea IMO is to port TCLSH! That would be very
powerful, it's very portable, was even originally designed for an embedded
system. I like this idea a lot. It probably came from Bart of course ;-)
although I can't remember for sure.
Comment 1 Alex Schuilenburg 2003-06-20 12:22:07 EDT
This bug has moved to http://bugs.ecos.sourceware.org/show_bug.cgi?id=86520

Note You need to log in before you can comment on or make changes to this bug.