9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Jack Johnson" <knapjack@gmail.com>,
	"Fans of the OS Plan 9 from Bell     Labs" <9fans@cse.psu.edu>
Subject: RE: [9fans] Plan 9 killer applications?
Date: Tue, 16 Nov 2004 13:24:05 -0800	[thread overview]
Message-ID: <7DD37218104E31429E79EB0BB136800E11C4B3@vargas.ntdom.cupdx> (raw)

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

Union directories and the file-oriented system... beautiful beyond words.  This is how operating systems should have been all along!!
 
-Ben

	-----Original Message----- 
	From: Jack Johnson [mailto:knapjack@gmail.com] 
	Sent: Tue 11/16/2004 1:14 PM 
	To: Fans of the OS Plan 9 from Bell Labs 
	Cc: 
	Subject: Re: [9fans] Plan 9 killer applications?
	
	

	On Tue, 16 Nov 2004 09:17:08 -0700, andrey mirtchovski
	<mirtchov@cpsc.ucalgary.ca> wrote:
	> user-level "mount" and "bind" come a close second and third :)
	
	I agree, along with Steve's venti + fossil.
	
	Relatedly, I was thinking on the drive this morning that Inferno could
	actually be an interesting alternative to either the standard p2p
	networks or even freenet, with SSL and union mounts support you could
	do some interesting things, in the "killer app" vein.
	
	-Jack
	


[-- Attachment #2.1: Type: text/plain, Size: 292 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/ms-tnef;
	name="winmail.dat"
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: winmail.dat.suspect --]
[-- Type: application/octet-stream, Size: 4150 bytes --]

             reply	other threads:[~2004-11-16 21:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 21:24 Benjamin Huntsman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 17:25 Benjamin Huntsman
2004-11-17 20:34 ` Vester Thacker
2004-11-17 15:33 Brantley Coile
2004-11-17 16:51 ` Matthias Teege
2004-11-17 17:52 ` Jack Johnson
2004-11-17 18:06   ` Dave Lukes
2004-11-17 23:16   ` geoff
2004-11-18  0:06     ` Jack Johnson
2004-11-18  5:32       ` vdharani
2004-11-18  1:56         ` Tim Newsham
2004-11-18  3:54           ` Jack Johnson
2004-11-18  0:59 ` Kenji Okamoto
2004-11-16 16:07 David Leimbach
2004-11-16 16:11 ` Fco. J. Ballesteros
2004-11-15 19:28   ` Steve Simon
2004-11-16 16:17   ` andrey mirtchovski
2004-11-16 17:07     ` matt
2004-11-16 17:15     ` rog
2004-11-17  0:15       ` Charles Forsyth
2004-11-17  1:08         ` Kenji Okamoto
2004-11-17  8:58           ` Richard Miller
2004-11-17 15:01             ` Ronald G. Minnich
2004-11-16 21:14     ` Jack Johnson
2004-11-16 16:37 ` Matthias Teege
2004-11-17 20:53 ` Vester Thacker
2004-11-22 20:16   ` Dan Cross

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=7DD37218104E31429E79EB0BB136800E11C4B3@vargas.ntdom.cupdx \
    --to=bhuntsman@mail2.cu-portland.edu \
    --cc=9fans@cse.psu.edu \
    --cc=knapjack@gmail.com \
    /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).