From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 27 Jul 2007 11:41:18 -0400
From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 advancements over Unix
Message-ID: <20070727154118.GA82735@kris.home>
References: <1185547777.637534.191320@22g2000hsm.googlegroups.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA"
Content-Disposition: inline
In-Reply-To: <1185547777.637534.191320@22g2000hsm.googlegroups.com>
User-Agent: Mutt/1.5.15 (2007-04-06)
Topicbox-Message-UUID: 97c11502-ead2-11e9-9d60-3106f5b1d025


--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 27, 2007 at 03:01:49PM +0000, Bilgehan.Balban@gmail.com wrote:
>Do you think these advancements over unix were successful?

Why do you think we're here?

>- The idea of using files for networking, did this prove superior over=20
>sockets?

That's an understatement.

>- Why was 8 1/2 abandoned? Is it because the graphics is much advanced
>over bitmap operations? Does plan9 use Xorg now? I think at least the
>idea of having a single private console sounds good.

8=BD was not abandoned, it was succeeded by rio. They work on the=20
same concepts, but rio is designed for the new draw device, and=20
lets clients access it directly. Switching to Xorg would cause=20
riots.

>- Having private namespaces means maintaining a namespace *per-=20
>process*. Would this not be more complicated than having a single one?

You speak in the wrong tense. We do have private namespaces.=20
They are different, but not more complicated.

Perhaps you should experiment rather than asking these=20
questions.

--=20
Kris Maglione

If you help a friend in need, he is sure to remember
you - the next time he's in need.

--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFGqhIdseQZD8Aui4wRArSRAJ9vNyKuMuiNBMU9I5Dy0zkjddILsACZAf0K
9MS/YDRNt5xLQmKnOyuJsZA=
=8FbK
-----END PGP SIGNATURE-----

--W/nzBZO5zC0uMSeA--