From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] contrib/install fgb/X11?
Date: Tue, 16 Nov 2010 01:58:17 -0300 [thread overview]
Message-ID: <AANLkTiku72VbnSHEvjAMpOTevaV93F2pYk-U85M_rCjP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinKxuP1UgPvo=JbTeKiDAOE1KFr7frTsZ39yZP8@mail.gmail.com>
btw, there are no lbuns for firefox and such, but it works, opera does too
On Tue, Nov 16, 2010 at 1:57 AM, Federico G. Benavento
<benavento@gmail.com> wrote:
> ok, dillo is a linux binary, right? and it looks like is looking for
> a unix socket,
> but equis has APE sockets!
> so for dillo try tcp DISPLAY=127.0.0.1:0
>
>
> On Tue, Nov 16, 2010 at 1:47 AM, David Leimbach <leimy2k@gmail.com> wrote:
>>
>>
>> On Mon, Nov 15, 2010 at 4:59 PM, ron minnich <rminnich@gmail.com> wrote:
>>>
>>> On Mon, Nov 15, 2010 at 3:37 PM, Federico G. Benavento
>>> <benavento@gmail.com> wrote:
>>> > also it shouldn't take that long... if you have the latest contrib
>>> > tools what happens
>>> > it's this: it first fcp's an iso.bz2 to your /tmp and runs replica from
>>> > there.
>>> >
>>>
>>>
>>> neat. That's a good step. 9pm won't use replica but at the same time
>>> this looks like a great idea.
>>>
>>> ron
>>>
>> Ah ok, well it does in fact appear to be working. Took me a minute to
>> realize I needed to set my DISPLAY to :0.
>> I have an old shell bundle of linuxemu dillo, but that does *not* work.
>> Xclock does.
>> cpu% ./dillo
>> [624803] syscall 191/ugetrlimit not implemented
>> [624803] syscall 149/sysctl not implemented
>> Gdk-WARNING **: locale not supported by Xlib, locale set to C
>> Gdk-WARNING **: can not set locale modifiers
>> [624803] syscall 209/newgetresuid not implemented
>> _X11TransSocketOpen: socket() failed for local
>> _X11TransSocketOpenCOTSClient: Unable to open socket for local
>> _X11TransOpen: transport open failed for local/virtualbunny:0
>> Gtk-WARNING **: cannot open display: :0
>> cpu%
>> Dave
>
>
>
> --
> Federico G. Benavento
>
--
Federico G. Benavento
next prev parent reply other threads:[~2010-11-16 4:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 15:39 David Leimbach
2010-11-15 16:01 ` ron minnich
2010-11-15 16:04 ` David Leimbach
2010-11-15 16:09 ` David Leimbach
2010-11-15 16:15 ` Stanley Lieber
2010-11-15 16:21 ` David Leimbach
2010-11-15 16:17 ` Steve Simon
2010-11-15 16:12 ` erik quanstrom
2010-11-15 16:17 ` David Leimbach
2010-11-15 16:20 ` David Leimbach
2010-11-15 16:44 ` ron minnich
2010-11-15 18:45 ` Steve Simon
2010-11-15 16:24 ` erik quanstrom
2010-11-15 16:27 ` David Leimbach
2010-11-15 16:36 ` David Leimbach
2010-11-15 16:46 ` ron minnich
2010-11-15 18:34 ` David Leimbach
2010-11-15 18:44 ` David Leimbach
2010-11-15 18:47 ` Steve Simon
2010-11-15 18:49 ` David Leimbach
2010-11-15 21:50 ` Yaroslav
2010-11-15 21:52 ` David Leimbach
2010-11-15 23:33 ` Federico G. Benavento
2010-11-15 23:37 ` Federico G. Benavento
2010-11-15 23:42 ` David Leimbach
2010-11-15 23:45 ` David Leimbach
2010-11-15 23:56 ` David Leimbach
2010-11-16 0:38 ` Federico G. Benavento
2010-11-16 0:59 ` ron minnich
2010-11-16 4:47 ` David Leimbach
2010-11-16 4:57 ` Federico G. Benavento
2010-11-16 4:58 ` Federico G. Benavento [this message]
2010-11-16 5:01 ` David Leimbach
2010-11-16 5:21 ` cinap_lenrek
2010-11-15 16:26 erik quanstrom
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=AANLkTiku72VbnSHEvjAMpOTevaV93F2pYk-U85M_rCjP@mail.gmail.com \
--to=benavento@gmail.com \
--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).