9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@9fans.net
Subject: Re: [9fans] what features would you like in a shell?
Date: Sun,  3 Oct 2010 17:25:25 +0100	[thread overview]
Message-ID: <4047832032da58ba5cc019968de8d912@vitanuova.com> (raw)

quite typically it's more than a little late, but i was finally able to scan in
an old RSRE paper that was relevant to the following. the scanning system i had
at the time couldn't cope.

anyway, it's at
	http://www.vitanuova.com/dist/doc/rsre-3522-curt.pdf

-------------------------------------
Newsgroups: comp.os.plan9
From: noagbodjivictor <noagbodjivic...@gmail.com>
Date: Tue, 31 Mar 2009 15:29:44 GMT
Local: Tues, Mar 31 2009 4:29 pm
Subject: what features would you like in a shell?
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
hello,
I'm a undergrade CS student doing a project for my introductory
operating systems class. my team wants to write a simple shell from  scratch.
one idea we have found so far is the following. the shell will record
all the programs it has run. whenever a program goes awry and is
killed by the kernel. the shell will reload it.
what do you think of it?
also, we know there are many many shells out there. and our professor
would not like us to write from scratch. we wanted because it provides
much exercise. but we certainly don't know about all the shells out
there.
so I'm writing to get your opinions. maybe there are thing that people
implement themselves but want included in the shell itself? or just
something they want implemented?
thanks a lot in advance for your help.



             reply	other threads:[~2010-10-03 16:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 16:25 C H Forsyth [this message]
2010-10-05 19:12 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2009-03-31 15:29 noagbodjivictor
2009-03-31 15:47 ` erik quanstrom
2009-03-31 16:10 ` matt
2009-03-31 16:26   ` erik quanstrom
2009-04-01  2:39     ` sqweek
2009-04-01  3:14       ` erik quanstrom
2009-03-31 16:14 ` rapogue
2009-03-31 16:19   ` André Günther
2009-03-31 16:19   ` erik quanstrom
2009-03-31 16:27     ` erik quanstrom
2009-03-31 16:16 ` noagbodjivictor
2009-03-31 16:47   ` erik quanstrom
2009-03-31 17:03     ` michael block
2009-04-01  9:28   ` matt
2009-04-01  9:43     ` yy
2009-04-01 10:01       ` matt
2009-04-01 12:41         ` hiro
2009-04-01 12:54           ` Martin Neubauer
2009-03-31 16:55 ` J.R. Mauro
2009-03-31 18:28 ` Corey
2009-04-02 18:41 ` John Stalker
2009-04-02 23:20   ` LiteStar numnums

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=4047832032da58ba5cc019968de8d912@vitanuova.com \
    --to=forsyth@vitanuova.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).