9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] opera under linuxemu
Date: Wed,  2 Jan 2008 22:39:05 -0500	[thread overview]
Message-ID: <7d3530220801021939q597fd8adm3e9ca296b0d20cb6@mail.gmail.com> (raw)
In-Reply-To: <32d987d50801021929v1a3c478awdd22daebb96d8aa@mail.gmail.com>

Pardon me for be a doubting Thomas, but that screenshot looks a hell
of a lot like a VNC session. You know, with the X cursor in the top of
the window and the default X background behind it, and TWM providing
window decorations. Now, having file:/net/ open in one of the windows,
I don't know what's up :)
I'm sorry for being skeptical, but that's what I'm seeing.

John

On 1/2/08, Federico G. Benavento <benavento@gmail.com> wrote:
> hola,
>
> getting real static binaries in linux is a bit tricky and no one seems to
> be doing so, they always need ld-linux.so, libnss and others.
> cinap creates some kind of bundles that create a  fake ns in /tmp/$lbun
> with this (http://9hal.ath.cx/usr/cinap_lenrek/lbun/mklbun) or something
> like, but I know he got opera running in Plan 9.
> http://9hal.ath.cx/usr/cinap_lenrek/plan9opera.png
>
>
> On Jan 2, 2008 9:55 PM, ron minnich <rminnich@gmail.com> wrote:
> > anybody got a howto? I grabbed cinap's linuxemu from sources. Right
> > now I get this:
> >
> > cpu% ./8.out opera-9.25-20071214.1-static-qt.i386-en-687/bin/opera
> > opera-9.25-20071214.1-static-qt.i386-en-687/bin/opera: cant load
> > interpreter: '/lib/ld-linux.so.2' does not exist
> > cpu% bind -a /mnt/term/lib /lib
> > cpu% ./8.out opera-9.25-20071214.1-static-qt.i386-en-687/bin/opera
> > 8.out 20707: suicide: sys: trap: fault read addr=0x57425810 pc=0x57425810
> > cpu%
> >
> > I am wondering if there is some simple thing I'm missing. I thought
> > static would not need ld-linux.so.2 but ...
> >
> > thanks
> >
> > ron
> >
>
>
>
> --
> Federico G. Benavento
>


-- 
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn


  reply	other threads:[~2008-01-03  3:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  0:55 ron minnich
2008-01-03  2:54 ` Iruata Souza
2008-01-03  3:29 ` Federico G. Benavento
2008-01-03  3:39   ` John Floren [this message]
2008-01-03  3:58     ` Federico G. Benavento
2008-01-03  4:03       ` Uriel
2008-01-03  4:02     ` Uriel
2008-01-03  5:26       ` ron minnich
2008-01-03  7:45         ` Uriel
2008-01-03 22:12     ` cinap_lenrek
2008-01-03 22:24       ` John Floren
2008-01-03 22:43         ` Francisco J Ballesteros
2008-01-03 22:50           ` [9fans] contrib(1) (was: opera under linuxemu) Federico G. Benavento
2008-01-03 23:09             ` Pietro Gagliardi
2008-01-03 23:22               ` Federico G. Benavento
2008-01-03 23:39                 ` Pietro Gagliardi
2008-01-04  4:08             ` marina
2008-01-03 23:26               ` Federico G. Benavento
2008-01-04  4:28                 ` marina
2008-01-03 23:08         ` [9fans] opera under linuxemu cinap_lenrek
2008-01-03  8:37   ` Martin Neubauer
2008-01-03 10:54     ` Lluís Batlle
2008-01-03 10:55       ` Lluís Batlle
2008-01-03 21:07     ` csant
2008-01-04  2:34 Russ Cox

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=7d3530220801021939q597fd8adm3e9ca296b0d20cb6@mail.gmail.com \
    --to=slawmaster@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).