9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] what features would you like in a shell?
Date: Tue, 31 Mar 2009 12:55:01 -0400	[thread overview]
Message-ID: <3aaafc130903310955j1c4122f0yaed8eb5acaeda02d@mail.gmail.com> (raw)
In-Reply-To: <607fb38c-9095-4045-abbb-28fa454184aa@l38g2000vba.googlegroups.com>

On Tue, Mar 31, 2009 at 11:29 AM, noagbodjivictor
<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.
>
> what do you think of it?

Bad idea. What if I expect it to die and maybe want to debug it before
running it again? What if the kernel killed it because it was hogging
resources? Respawning something that constantly gets killed will
probably render the machine unusable. What if the program dies really
quickly? The shell could get caught in a very tight loop you can't
interrupt, and the user winds up killing the shell itself and opening
a new one (after getting really aggravated).

I suppose you could make it optional, but then again, why can't the
user just restart the process by hand?

>
> 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.
>
>



  parent reply	other threads:[~2009-03-31 16:55 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
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 [this message]
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=3aaafc130903310955j1c4122f0yaed8eb5acaeda02d@mail.gmail.com \
    --to=jrm8005@gmail.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).