9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Aki Nyrhinen" <anyrhine@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow
Date: Tue, 12 Dec 2006 18:51:40 -0700	[thread overview]
Message-ID: <218917ef0612121751n5624f2c4x1ee668035457aa3f@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60612121637s4919f5c7r9a6608617dbdbdf6@mail.gmail.com>

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

after watching andrey run plan9 in parallels and seeing the drawterm
windows on x11, i'd have agreed with you, but i must say it feels a lot
less bad when the "parasite" is full-screen and the "host" programs like
firefox are in a smaller rio window that you can kill or hide at will.

the firefox i'm writing this in is running full-screen (f11) on a 1000 by
1000 pixel vnc session and the illusion of having it native is pretty
damn good (for me anyway) at least until my drawterm hack crashes
and i start shouting untranslatable words (i hope it's better now that
i realized drawterm didn't have reentrant memimagedraw)

On 12/12/06, David Leimbach <leimy2k@gmail.com> wrote:
>
> > I can't deny the utility of having Firefox (I'm writing this in a
> > Firefox window), but even if Plan 9 could run Firefox, the next
> > thing would be oh but it needs to be able to run these ten
> > plugins, and so on and so on.  Personally, I think you are going
> > to be much happier running Plan 9 in some VM environment on
> > Linux or Windows than putting in the effort for the other way around.
> >
>
> And a lot of times, at the end of the day, I feel that as a result of
> wanting to run Plan 9 in a VM environment, even in Parallels, makes me
> sad, and I'd almost rather use Inferno :-)
>
>
> > Russ
> >
>

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

      reply	other threads:[~2006-12-13  1:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10 23:52 erik quanstrom
2006-12-12  0:22 ` Dave Eckhardt
2006-12-12  2:29   ` Russ Cox
2006-12-12  5:01     ` Lucio De Re
2006-12-12 14:21       ` Brantley Coile
2006-12-12  9:22     ` Charles Forsyth
2006-12-12  9:41       ` Bruce Ellis
2006-12-12 14:31         ` Brantley Coile
2006-12-12 14:55         ` ron minnich
2006-12-12 15:18           ` Eric Van Hensbergen
2006-12-12 15:25             ` erik quanstrom
2006-12-12 22:01             ` ron minnich
2006-12-12 22:19               ` Latchesar Ionkov
2006-12-12 23:13                 ` ron minnich
2006-12-12 23:47                   ` Bakul Shah
2006-12-12 23:37                 ` Charles Forsyth
2006-12-13 18:27                   ` ron minnich
2006-12-13 19:02                     ` Matt
2006-12-13 19:13                       ` Latchesar Ionkov
2006-12-14 18:55                         ` David Leimbach
2006-12-13  0:41               ` quite Off Topic: " Georg Lehner
2006-12-13  3:46                 ` Jack Johnson
2006-12-13 21:04                 ` ron minnich
2006-12-13 21:13                   ` Russ Cox
2006-12-13 21:30                     ` Bakul Shah
2006-12-12  9:41       ` Gabriel Diaz
2006-12-12  9:51         ` Bruce Ellis
2006-12-12 10:28           ` Lucio De Re
2006-12-12 10:30             ` Bruce Ellis
2006-12-12 23:26               ` Scott Schwartz
2006-12-12 14:42             ` Brantley Coile
2006-12-12 14:51               ` Gabriel Diaz
2006-12-12 11:49           ` Charles Forsyth
2006-12-12 14:17     ` Brantley Coile
2006-12-13  0:37     ` David Leimbach
2006-12-13  1:51       ` Aki Nyrhinen [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=218917ef0612121751n5624f2c4x1ee668035457aa3f@mail.gmail.com \
    --to=anyrhine@gmail.com \
    --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).