9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Dan Cross" <crossd@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] How can I shift a variable other than ?
Date: Sat, 10 Mar 2007 17:20:43 -0500	[thread overview]
Message-ID: <aa7e41150703101420o5c2d0f83na6c750a6e6243b63@mail.gmail.com> (raw)
In-Reply-To: <20070310215344.GH12719@kris.home>

On 3/10/07, Kris Maglione <bsdaemon@comcast.net> wrote:
> On Sat, Mar 10, 2007 at 04:20:22PM -0500, Dan Cross wrote:
> >Nonsense.  You think rc has never changed before?  There have been
> >plenty of non-backwards compatible changes in Plan 9.
>
> You miss the point entirely. I agree that things shouldn't stay the same
> simply for the sake of compatibility. Plan 9 threw away a bunch of UNIX
> crud in the begining, and was not set in stone from the begining. I have
> no desire to add teletypes and ioctls to be compatible with UNIX.
>
> The point is that rc(1) has been rc since the begining. It's rc
> everywhere. If you write an rc script, you can expect it work wherever
> you send it. The one infuriating exception which I've run across is the
> UNIX port, which I have to worry about being in peoples' PATHs on UNIX,
> rather than the Plan 9 version.
>
> If there are to be changes, there's no reason to make those
> changes to rc. It would be best to create a new shell that deals with
> the shortcomings of rc, rather than adding features and cruft. That is
> how UNIX got to be so cruddy to begin with. The reason that sh(1) and
> Plan 9 are so nice is because they reevaluated and threw away most of
> what came before them.

No, I didn't miss the point, which, if carried to its logical
conclusion would imply that we should just write a new operating
system whenever we want to add something new.  There's nothing set in
stone about any system; the problems you describe come when people
start believing that there is.  The proliferation of shells under Unix
could have been avoided by carefully re-evaluating the existing offers
and making appropriate changes.  Instead, we ended up with Shell Soup.

Rc is just a program; yes, a pretty good one, but it is not a
religious document: it is open to interpretation, re-evaluation and
change.

Put another way, one of the reasons Plan 9 has remained so nice over
the years is because the folks primary responsible for it have been
open to making reasonable changes where appropriate.

> >>It runs on Inferno, which runs on Plan 9. You can script for Plan 9 in
> >>Inferno's sh. You can even script for UNIX in it. I've done both. It
> >>works. It's not even ugly.
>
> Then perhaps, as has been said for ages, it is best to make the
> integration between Inferno and Plan 9 more seemless, and the
> installation easier. It would, indeed, be nice to include Inferno in
> Plan 9 by default.

You're replying to yourself there.

        - Dan C.


  reply	other threads:[~2007-03-10 22:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10 12:32 erik quanstrom
2007-03-10 17:30 ` Kris Maglione
2007-03-10 21:20   ` Dan Cross
2007-03-10 21:53     ` Kris Maglione
2007-03-10 22:20       ` Dan Cross [this message]
2007-03-11 12:12       ` matt
2007-03-11 20:23         ` Kris Maglione
2007-03-11 22:11           ` erik quanstrom
2007-03-11 23:14             ` Martin Neubauer
2007-03-12  8:50               ` Kris Maglione
2007-03-12 12:26                 ` erik quanstrom
2007-03-12 13:37                   ` Anthony Sorace
2007-03-12 13:39           ` Dan Cross
2007-03-12 15:22             ` Russ Cox
2007-03-12 17:05               ` Dan Cross
2007-03-12 18:41                 ` Kris Maglione
2007-03-13 14:59           ` rog
2007-03-13 15:22             ` erik quanstrom
2007-03-13 15:40               ` [9fans] minimal-instruction-sets (was: How can I shift a variable other than ?) andrey mirtchovski
2007-03-13 15:40             ` [9fans] How can I shift a variable other than ? C H Forsyth
2007-03-13 17:45               ` Anthony Sorace
2007-03-13 20:39                 ` Paweł Lasek
2007-03-13 17:32             ` Anthony Sorace
  -- strict thread matches above, loose matches on Subject: below --
2007-03-10  4:46 erik quanstrom
2007-03-10  5:14 ` Kris Maglione
2007-03-09  4:38 erik quanstrom
2007-03-09  4:48 ` erik quanstrom
2007-03-09  5:27   ` Federico G. Benavento
2007-03-09  5:31     ` erik quanstrom
2007-03-09  7:00       ` Kris Maglione
2007-03-09 13:55         ` erik quanstrom
2007-03-09 14:09           ` Kris Maglione
2007-03-09 14:33             ` erik quanstrom
2007-03-09 14:37             ` erik quanstrom
2007-03-09  4:57 ` lucio
2007-03-09 14:41   ` erik quanstrom
2007-03-08  8:00 YAMANASHI Takeshi
2007-03-08  8:41 ` Russ Cox
2007-03-09 18:23 ` rog
2007-03-09 19:25   ` Kris Maglione

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=aa7e41150703101420o5c2d0f83na6c750a6e6243b63@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).