From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] why not Lvx for Plan 9?
Date: Tue, 8 Jul 2008 13:39:21 -0400 [thread overview]
Message-ID: <9dd24bcd20558c5a4480048decad8b73@9srv.net> (raw)
In-Reply-To: <20080708172610.ADA9E1E8C2B@holo.morphisms.net>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
Well, there's also people like me: I prefer and am able to use
Plan 9 the bulk of the time, but have a few particular tasks I
need Linux for. It'd be nice to be able to stick the Linux box
in a little jail.
I'm very glad 9vx exists: I now have Plan 9 on my OS X laptop.
I'd like Lvx to stick on my Plan 9 cpu servers. As it stands, I'll
be converting one of my older cpu servers into a linux box in a
few weeks. That makes me feel unclean.
Anthony
[-- Attachment #2: Type: message/rfc822, Size: 2190 bytes --]
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] why not Lvx for Plan 9?
Date: Tue, 8 Jul 2008 13:27:59 -0400
Message-ID: <20080708172610.ADA9E1E8C2B@holo.morphisms.net>
> However, I have somewhat confused mind.... Why it's not Linux vx for
> Plan9? I have no intention to make it bad, however, if we believe
> Plan 9 is better than Linux, then Linux vx for Plan9 should be more
> neccessary, shouldn't ?
I wrote 9vx for people like me, who would prefer to use
Plan 9 but, for various reasons, must use FreeBSD or
Linux or Mac OS X.
Linux vx for Plan 9 would help people who prefer to use
Linux but must use Plan 9. I am sure such people exist,
but I feel no sympathy toward them. ;-)
Russ
prev parent reply other threads:[~2008-07-08 17:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 15:28 kokamoto
2008-07-08 15:58 ` David Leimbach
2008-07-08 16:04 ` erik quanstrom
2008-07-08 16:33 ` ron minnich
2008-07-08 16:47 ` Charles Forsyth
2008-07-09 4:33 ` LiteStar numnums
2008-07-08 17:46 ` Eric Van Hensbergen
2008-07-08 17:49 ` erik quanstrom
2008-07-08 18:38 ` a
2008-07-08 19:01 ` erik quanstrom
2008-07-08 19:46 ` a
2008-07-08 20:03 ` Eric Van Hensbergen
2008-07-08 20:15 ` William Josephson
2008-07-08 20:38 ` Eric Van Hensbergen
2008-07-08 21:25 ` ron minnich
2008-07-08 22:16 ` Steve Simon
2008-07-08 22:32 ` David du Colombier
2008-07-09 0:01 ` don bailey
2008-07-09 0:13 ` ron minnich
2008-07-09 3:17 ` Eric Van Hensbergen
2008-07-09 3:43 ` ron minnich
2008-07-09 3:45 ` erik quanstrom
2008-07-09 4:44 ` David Leimbach
2008-07-08 18:50 ` David Leimbach
2008-07-08 17:19 ` Skip Tavakkolian
2008-07-10 12:58 ` matt
2008-07-10 13:47 ` Russ Cox
2008-07-10 14:03 ` erik quanstrom
[not found] ` <B94154D0-97B5-4FFF-A140-E47D95FC1307@flyingwalrus.net>
2008-07-12 15:59 ` erik quanstrom
2008-07-10 15:18 ` ron minnich
2008-07-10 16:33 ` Charles Forsyth
2008-07-10 16:36 ` ron minnich
2008-07-10 19:25 ` cinap_lenrek
2008-07-10 19:50 ` ron minnich
2008-07-11 9:10 ` Kernel Panic
2008-07-11 16:12 ` ron minnich
2008-07-10 14:01 ` erik quanstrom
2008-07-08 17:27 ` Russ Cox
2008-07-08 17:39 ` a [this message]
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=9dd24bcd20558c5a4480048decad8b73@9srv.net \
--to=a@9srv.net \
--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).