9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] THX hell
Date: Tue,  1 May 2007 11:42:30 -0700	[thread overview]
Message-ID: <13426df10705011142s943fa15leee215f5bbe0ab4c@mail.gmail.com> (raw)

OK, here's a quandary.

THX is the tiny horrible xen, a little USB stick that I've got a
standalone system, AND a terminal you can boot from (e.g.) 9grid.net.
It has ballooned (firefox) to require a 2GB USB stick, but hey,
they're $15 at Fry's, who cares. You can boot it, it boots fine and
works fine on my T41.

It's nice, we don't even load X11, since we have Aki's FB drawterm.
Just load fbdev, good to go.

The goal here is to make Linux an insignificant part of the machine.
Boot Linux as dom0, but run Linux in (e.g.) 32MB, and give most of the
machine to Plan 9. Linux is a driver. Your immediate interface to Plan
9 is bash. There are no /etc/rc* scripts.

on my T60, there is no fbdev support. And you can't use vesafb. You
can't use vesafb in Linux, as the 16 bit part of linux never runs
under Xen. I would need to add vesafb support to Xen. This makes my
brain hurt.

I could add X11 to THX, and we could use drawterm-x11. This is not
really what we wanted to do, but ...

I was trying to have this ready to demo at BAP9UG, May 10, but this is
a snag! There is no easy FB support for T60, and I think this problem
will just become worse. Not being able to load vesafb is a problem.

So, choices:
1. Stick with Xen, add vesafb to Xen, done.
2. Stick with Xen, add X server to THX distro, run drawterm-x11, done.
3. Move to KVM, so we can have vesafb, use drawterm-fb, done.

any ideas here? What makes sense?

ron


             reply	other threads:[~2007-05-01 18:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 18:42 ron minnich [this message]
2007-05-01 18:46 ` Richard Miller
2007-05-01 18:52   ` ron minnich
2007-05-01 20:59 ` geoff
2007-05-01 21:40 ` Bakul Shah
2007-05-01 21:45   ` ron minnich
2007-05-01 22:14   ` Steve Simon
2007-05-02  0:24     ` ron minnich
2007-05-02  0:29       ` Eric Van Hensbergen
2007-05-02  9:14 ` csant
2007-05-02 17:00   ` ron minnich
2007-05-02 17:28     ` Anthony Sorace
2007-05-02 17:45       ` W B Hacker
2007-05-03  7:23         ` csant
2007-05-02 22:26     ` csant

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=13426df10705011142s943fa15leee215f5bbe0ab4c@mail.gmail.com \
    --to=rminnich@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).