9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] what features would you like in a shell?
Date: Tue, 31 Mar 2009 11:47:57 -0400	[thread overview]
Message-ID: <b15e4ef6b678f21943a3f18598804f73@quanstro.net> (raw)
In-Reply-To: <607fb38c-9095-4045-abbb-28fa454184aa@l38g2000vba.googlegroups.com>

On Tue Mar 31 11:37:06 EDT 2009, noagbodjivictor@gmail.com wrote:
> 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.

unfortunately, the most common reason for a program to go
arwy is that the program is broken and it will break again when
reloated.

it would be more interesting to explore how a shell in plan 9
could be used to build simple fs.

rc has a very interesting virtual machine.  it might be interesting
to build a shell with some hooks into its vm.  paul haahr and
byron built a shell with scheme-y internals and exposed them.
interesting, but complicated.

it would be interesting to use something closer to regular expressions
rather than standard shell globbing.  the challenge would be
to avoid gratuitous breakage and yet allow the match operator
to be much more powerful.

these are areas where rc might be improved upon.  however,
as per usual, it was hard to improve on bourne, and it's even
harder to improve on duff.

nevertheless, i learned quite a bit from failing to improve on
rc.

- erik



  reply	other threads:[~2009-03-31 15:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 15:29 noagbodjivictor
2009-03-31 15:47 ` erik quanstrom [this message]
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
2010-10-03 16:25 C H Forsyth
2010-10-05 19:12 ` erik quanstrom

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=b15e4ef6b678f21943a3f18598804f73@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).