From: csant <csant@csant.info>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] Investigating the Plan 9 Operating System - OSNews.com
Date: Thu, 20 Jul 2006 00:38:28 +0200 [thread overview]
Message-ID: <op.tcyjuewtd84skq@fiore.malebolge> (raw)
In-Reply-To: <3e1162e60607191528q19686c97t7f7e81a7251424be@mail.gmail.com>
> Oh it gets better:
"UNIX's name server, BIND, has been replaced by ndb, which is easy to
configure, much more secure, and is the partial basis for Plan 9's
powerful, distributed name space."
And since there *are* several bits and pieces of Plan 9 that I still do
not grasp, and since private namespaces have also been brought up recently
as something not every n00b gets right away: could anybody please explain
to me what exactly the Plan 9 namespaces have to do with ndb?
/c
next prev parent reply other threads:[~2006-07-19 22:38 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 21:47 csant
2006-07-19 22:25 ` David Leimbach
2006-07-19 22:28 ` David Leimbach
2006-07-19 22:38 ` csant [this message]
2006-07-19 23:50 ` erik quanstrom
2006-07-20 6:39 ` csant
2006-07-20 14:50 ` Ronald G Minnich
2006-07-20 15:08 ` Wes Kussmaul
2006-07-20 16:47 ` David Leimbach
2006-07-20 18:42 ` Ronald G Minnich
2006-07-20 0:06 ` Federico G. Benavento
2006-07-20 1:00 ` David Leimbach
2006-07-20 6:48 ` Christoph Lohmann
2006-07-20 12:25 ` Re: Re: [9fans] Investigating the Plan 9 Operating System - Brantley Coile
2006-07-20 13:32 ` Benn Newman
2006-07-20 16:30 ` Re: Re: [9fans] Investigating the Plan 9 Operating System - OSNews.com Lyndon Nerenberg
2006-07-20 0:06 ` Geoffrey Avila
2006-07-19 22:52 ` LiteStar numnums
2006-07-20 14:51 ` Ronald G Minnich
2006-07-23 14:14 ` LiteStar numnums
2006-07-23 14:13 ` erik quanstrom
2006-07-23 15:02 ` matt
2006-07-23 20:07 ` csant
2006-07-23 21:24 ` Federico G. Benavento
2006-07-23 21:29 ` csant
2006-07-23 22:22 ` Dan Cross
2006-07-24 6:03 ` Federico Benavento
2006-07-24 22:09 ` Plan 9
2006-07-24 22:18 ` andrey mirtchovski
2006-07-24 22:25 ` Federico G. Benavento
2006-07-24 22:39 ` jmk
2006-07-24 22:44 ` Ronald G Minnich
2006-07-25 14:44 ` Dave Lukes
2006-07-25 16:07 ` elbing
2006-07-25 16:41 ` ems
2006-07-25 16:56 ` Ignacio Torres Masdeu
2006-07-25 17:27 ` ems
2006-07-25 17:33 ` Michael Baldwin
2006-07-26 18:20 ` Dan Cross
2006-07-25 17:52 ` Iruatã Souza (muzgo)
2006-07-25 19:15 ` Skip Tavakkolian
2006-07-25 21:42 ` Sascha Retzki
2006-07-25 18:55 ` ems
2006-07-27 15:04 ` Wes Kussmaul
2006-07-27 15:40 ` Ronald G Minnich
2006-07-27 18:23 ` Wes Kussmaul
2006-07-27 20:20 ` Nicolás Victorero Mier
2006-07-28 2:29 ` erik quanstrom
2006-07-28 9:48 ` Harri Haataja
2006-07-28 10:59 ` erik quanstrom
2006-07-28 14:01 ` David Leimbach
2006-07-28 13:54 ` erik quanstrom
2006-07-28 15:35 ` Skip Tavakkolian
2006-07-28 14:05 ` Wes Kussmaul
2006-07-23 20:49 cse.psu.edu!9fans-bounces+9fans-archive=plan9.bell-labs.com, Andrew Hudson
2006-07-23 23:40 ` David Leimbach
2006-07-24 5:41 ` Christoph Lohmann
2006-07-24 8:19 ` Bruce Ellis
2006-07-24 15:04 ` John Floren
2006-07-24 15:23 ` andrey mirtchovski
2006-07-24 13:29 ` David Leimbach
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=op.tcyjuewtd84skq@fiore.malebolge \
--to=csant@csant.info \
--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).