From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 7 May 2011 00:01:35 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <20110506172053.GA32005@clanspum.net> <9D638F5B-62D7-4B70-8557-A6777476C9B9@9srv.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] updating 9vx's Plan 9 install Topicbox-Message-UUID: e059f618-ead6-11e9-9d60-3106f5b1d025 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