9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] go to this site
Date: Tue, 27 Oct 2009 08:39:29 -0700	[thread overview]
Message-ID: <3e1162e60910270839r7fe92b4fq50eff874b356655f@mail.gmail.com> (raw)
In-Reply-To: <988de8fc743f8699838c8b950aca71c3@ladd.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

On Tue, Oct 27, 2009 at 8:33 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> > I mean, say your company has 25 satellite offices... why should they all
> > have to do redundant work to update all the systems across the board.
>  Isn't
> > the repetition going to cause a higher chance of someone missing
> something?
>
> absent the plan 9 terminal model, who updates users' machines?
>

Right, that was the big illogical hole in the plan they had.  I couldn't
figure out why anyone who had everything the company needed for business
production and work, would want to use a PC with local storage for a
terminal system to a mainframe that basically couldn't do too much more.

I guess PCs were a cheap way to go, or Dell (or whomever it was) gave them a
great deal or something to make it seem it was worth their while.

Even all the email was on the mainframe, but it wasn't called email, it was
something else.

I suppose a few people may have needed word processing or spreadsheets or
whatever, but that was only because there was no way developed to do word
processing or spreadsheets on the mainframe.

Old stuff becoming new again shouldn't be surprising to anyone at this point
though I guess.

Dave


>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 1848 bytes --]

  reply	other threads:[~2009-10-27 15:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<3e1162e60910270826m281a7a9awba6ea117b7351605@mail.gmail.com>
2009-10-27 15:33 ` erik quanstrom
2009-10-27 15:39   ` David Leimbach [this message]
     [not found] <<4AE70F74.7000505@authentrus.com>
2009-10-27 15:23 ` erik quanstrom
2009-10-27 15:50   ` ron minnich
2009-10-27 17:32     ` Wes Kussmaul
2009-10-27 18:07   ` Wes Kussmaul
2009-10-27 18:59     ` erik quanstrom
2009-10-27 19:57       ` Wes Kussmaul
2009-10-27 20:11         ` erik quanstrom
2009-10-27 20:33           ` Wes Kussmaul
2009-10-27 20:36           ` Wes Kussmaul
2009-10-27  0:00 ron minnich
2009-10-26 20:33 ` Jacob Todd
2009-10-27  0:38 ` Joseph Stewart
2009-10-27  0:47   ` Jeff Sickel
2009-10-27  0:41 ` dave.l
2009-10-27  0:50 ` Geoffrey Avila
2009-10-27  1:52 ` Latchesar Ionkov
2009-10-27  2:39   ` ron minnich
2009-10-27 13:03     ` Eris Discordia
2009-10-27  3:21   ` andrey mirtchovski
2009-10-27  3:47     ` ron minnich
2009-10-27  3:49       ` ron minnich
2009-10-27 15:19         ` Wes Kussmaul
2009-10-27 15:26           ` David Leimbach
2009-10-27 18:42         ` Sam Watkins
2009-10-27  4:06       ` W B Hacker
2009-10-27  5:42 ` Skip Tavakkolian
2009-10-27  8:00 ` tlaronde
2009-10-27  8:12   ` lucio

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=3e1162e60910270839r7fe92b4fq50eff874b356655f@mail.gmail.com \
    --to=leimy2k@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).