From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] updating 9vx's Plan 9 install
Date: Sat, 7 May 2011 00:01:35 -0400 [thread overview]
Message-ID: <b5aa08b5f54cd1d4edc4742a3dc9f1d8@ladd.quanstro.net> (raw)
In-Reply-To: <CCE2FF34-0462-4853-938C-A2B7E5DDA640@storytotell.org>
On Fri May 6 23:55:38 EDT 2011, fusion@storytotell.org wrote:
>
> On May 6, 2011, at 11:31 AM, Anthony Sorace wrote:
>
> > In addition to the tree Andrey noted, the general
> > answer is simply to download the normal distribution
> > image and use that. The effect is the same as using
> > the tree Andrey pointed to and updating, but you'll
> > save yourself time and work by just grabbing the
> > current image.
> >
> > http://plan9.bell-labs.com/plan9/download/plan9.iso.bz2
> >
> > just mount the image and copy the contents to
> > wherever you'd like your 9vx root to live, and point
> > 9vx at that.
> >
>
>
> That didn't work. Rio doesn't live long; you create a window and then get this:
>
> invalid opcode f0 0f b1 at eip 00013f3b
> invalid opcode f0 0f b1 at eip 00020dc2
looks like your 9vx itself is confused, not rio. that's a lock; cmpxchg.
; 9fs sources
post...
; acid /n/sources/plan9/386/bin/rio
/n/sources/plan9/386/bin/rio:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: src(0x20dc2)
/sys/src/libc/386/atom.s:8
3 ainclp:
4 MOVL (BX), AX
5 MOVL AX, CX
6 INCL CX
7 LOCK
>8 BYTE $0x0F; BYTE $0xB1; BYTE $0x0B /* CMPXCHGL CX, (BX) */
9 JNZ ainclp
10 MOVL CX, AX
11 RET
12
- erik
next prev parent reply other threads:[~2011-05-07 4:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 17:20 Daniel Lyons
2011-05-06 17:22 ` andrey mirtchovski
2011-05-06 17:31 ` Anthony Sorace
2011-05-06 18:13 ` ron minnich
2011-05-06 18:31 ` Daniel Lyons
2011-05-07 3:54 ` Daniel Lyons
2011-05-07 4:01 ` erik quanstrom [this message]
2011-05-07 4:05 ` erik quanstrom
2011-05-07 4:13 ` Daniel Lyons
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=b5aa08b5f54cd1d4edc4742a3dc9f1d8@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).