9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] X11 setup problem
Date: Wed, 20 Jun 2007 10:08:31 +0100	[thread overview]
Message-ID: <15e00d9c62116ee262720b9164341c97@quintile.net> (raw)
In-Reply-To: <7d3530220706200147wf2125d3uec46458555d1c63e@mail.gmail.com>

> Looks like the problem here is that the iso is SO old, it expects a
> kfs file system rather than the current fossil fs.

Exactly, the x11 iso predates fossil.

I am sure this was discussed a fairly recently,
fbg rembembers the answer, if you google comp.os.plan9
you should find some hints.

the x11 port offers only 8 bit pixmaps to the clients
so all images must be remapped to the physical displays
depth in the server, so its slow on 16bit and 32bit displays.

This said it does work though annoyingly some programs
refuse to cooperate with 8bit displays, most notably
firefox ☹

If you are interested, the port consists of a single file
(brazil.c from memory) and I for one would find a new port
that supports 16 and 32 bit displays very useful.

Also beware, recompiling X11 from scratch takes a 20 or 30
times as long as compiling the plan9 kernel.

-Steve



  reply	other threads:[~2007-06-20  9:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20  8:38 pavlovetsky
2007-06-20  8:47 ` John Floren
2007-06-20  9:08   ` Steve Simon [this message]
2007-06-20  9:29 ` [9fans] " pavlovetsky
2007-06-20 11:40   ` Anthony Sorace
2007-06-20 13:54     ` Paweł Lasek
2007-06-21  8:51     ` pavlovetsky
2007-06-20 14:14   ` pavlovetsky
2007-06-20 14:42   ` pavlovetsky
2007-06-20 22:15   ` Steve Simon
2007-06-20 22:55     ` john
2007-06-21  7:29       ` Steve Simon
2007-06-22  8:57   ` pavlovetsky
2007-06-22  9:40     ` Steve Simon

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=15e00d9c62116ee262720b9164341c97@quintile.net \
    --to=steve@quintile.net \
    --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).