From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8ccc8ba40708120336k60107c2boa7c4f343a8e4d838@mail.gmail.com>
Date: Sun, 12 Aug 2007 12:36:12 +0200
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] THNX
In-Reply-To: <13426df10708112153v6b29d49awa7293abcfa714b25@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <13426df10708101749v132987b8r290a861f65d82d42@mail.gmail.com>
	<8ccc8ba40708110623l13a83029t3ecd23b00063acf2@mail.gmail.com>
	<13426df10708112153v6b29d49awa7293abcfa714b25@mail.gmail.com>
Topicbox-Message-UUID: a716a81e-ead2-11e9-9d60-3106f5b1d025

Omero tries to exploit a full plan b environment, but can work without
one. Thus,
I'd forget about bns et al. (as long as you don't want your
environment to adapt to
new/gone machines in the environment).

Thus, to use omero I'd say that you can do either 1) or 2) below. If
you have problems
with that, or whatever, I might help more if you tell me exactly what
you did and what the
problem was.

1:  from a drawterm:

- run rio, run omero. that would be it.
(once vera fonts are there, and /devs mountpoints, I mean)

2:  from a terminal (against a CPU server):

- run omero in your terminal (you may exit from the ox, you won't be using it)
- from tthat  ns, cpu to your cpu server, and bind omero to /devs/$sysname^ui
- from that ns, in the cpu, run ox (it would open files, run commands
on the cpu server, but use
/devs/$sysname^ui to create omero panels).

Now some comments:
- vera fonts should be there, in the cpu ns
- to use a shared clipboard, /dev/snarf and /dev/sel should be rw files (we keep
them under $home/lib and bind them at /dev, for all machines for the same user).

But, in any case, if you have problems with this, when I get back in
town (one or two
weeks), I can try to reproduce all this and provide a more precise
recipe, if that's what
you want.


hth