[9fans] Pull and compile latest kernel (sys call 53 error)
Hello,
How should I properly update to the latest kernel on a new install of Plan 9
from Bell Labs?
I downloaded Plan9, ran the "pull" script, and then tried to compile and
install a new kernel by running mk install in /sys/src/9/pc
Compilation seemed to go fine, but then I got an syscall 53 error (the error
seems to come from "ar", see below).
Thank you,
Patryk
-- snip --
8c -FTVw -I. ../port/sysproc.c
8c -FTVw -I. ../port/taslock.c
8c -FTVw -I. ../port/tod.c
8c -FTVw -I. ../port/xalloc.c
8c -FTVw main.c
names=`{membername $newprereq}
ar vu ../boot/libboot.a8 $names
rm $names
ar 856: bad sys call number 53 pc becd
ar 856: suicide: sys: bad sys call pc=0xbecd
mk: names=`{membername $newprereq} ar ... : exit status=rc 849: ar 856: sys:
bad sys call pc=0xbecd
term%
Re: [9fans] Pull and compile latest kernel (sys call 53 error)
> you need to reboot using one of the kernels you pulled first. > How do I find the kernels that I pulled? They don't appear to be in /sys/src/9/pc After I have found the kernel, do I with it by copying it into /n/9fat as specified here?: http://plan9.bell-labs.com/wiki/plan9/compiling_kernels/ Thank you, Patryk
Re: [9fans] Pull and compile latest kernel (sys call 53 error)
> they are in /386 (ie - /386/9pcf). a pull copies binaries as well > as source. Thank you, it's working perfectly. Patryk
Re: [9fans] Alternative Plan 9 Logo
Wow, that looks really sharp. It seems appropriate to have such a logo for an operating system that is the potential next step after unix.PatrykOn Jan 03, 2014, at 02:07 PM, phineas.p...@gmail.com wrote: Hi everyone, I'm tinkering with an alternative Plan 9 logo. Any comments or suggestions? Is there even any interest in something like this? http://pdf.multics.org/9_Logo_Concept.pdf Best, Peter
Re: [9fans] Vanilla Plan 9 or one of the flavors?
Hi Alex, I just joined the list, and so I missed your question. But I also opted for going with the vanilla distribution. Enjoy -- it's been pretty fun so far! Patryk > On Jan 5, 2014, at 15:54, Alex Jordan wrote: > >> On Mon Dec 30 21:03:24 EST 2013, alexander3223...@gmail.com wrote: >> Basically, would you guys recommend I try the Bell Labs >> distribution of Plan 9, 9front, or 9atom as my first installation? > Since no one seems to have an opinion on this, I'm going with the Bell > Labs distribution. We'll see how it goes. > >> On Mon, Dec 30, 2013 at 8:33 PM, erik quanstrom >> wrote: >> well let me know if i can answer any questions or fix anything. funny how >> we all get >> pigeon holed. i thought i did 9atom to support more hardware. :-) > Will do, thanks! > smime.p7s Description: S/MIME cryptographic signature
Re: [9fans] Vanilla Plan 9 or one of the flavors?
On Jan 05, 2014, at 09:09 PM, Lyndon Nerenberg wrote: But the reality is: the labs are no more. No funding, no interest, no anything. Geoff and Jim are due for retirement from this mailing list. (Jim left ages ago, in fact.) Let's let them go in peace. I'm fairly new here, but it seems that so long as the /n/sources/contrib mechanism exists, we can go on providing patches to the plan9 user community indefinitely... Although, it seems that Geoff and Jim were the ones who authorized creating files in contrib. Is their retirement going to be a showstopper for contrib? (The archives at http://9fans.net/archive/ don't seem to be working, so I'm not able to check for recent mentions of this on the mailing list.)Thank you,Patryk
Re: [9fans] Help with networking on Virtual Box
Hi Peter, I had the same DNS issue under VirtualBox. Here is my procedure after every reboot (I am new to plan9 so there may be a better way): 1. Run ip/ipconfig 2. cat /net/ipselftab to find your VM's internal ip (10.0.x.x?) 3. Set your IP in /lib/ndb/local ip = … 4. Run ndb/dns -r I don't know enough about plan9 to know why this is necessary. I pieced this procedure together using the docs and help from the IRC channel. Plan9 is really cool though -- enjoy! Best, Patryk > On Feb 11, 2014, at 3:32, Peter Hull wrote: > > Dear All, > I am just trying to set up Plan 9 so I can have a play with it. I'm > running it in VirtualBox 4.3.6 and I'm running into the DNS problem > that has been reported earlier [1] > > ip/ipconfig seems to run fine but it assigns an address of 127.0.0.1 > and DNS doesn't work. > > Unfortunately (as far as I can see) the previous reports didn't come > up with a solution or the reporter found a different way to run Plan > 9. > > I used the -D option on ip/ipconfig and got this: > term% ip/ipconfig -D > ipconfig: parsebootp: new packet > ipconfig: parseoptions: type(53) len 1, bytes left 58 > ipconfig: parseoptions: serverid(54) len 4, bytes left 55 > ipconfig: parseoptions: lease(51) len 4, bytes left 49 > ipconfig: parseoptions: ipmask(1) len 4, bytes left 43 > ipconfig: parseoptions: ipgw(3) len 4, bytes left 37 > ipconfig: parseoptions: dns(6) len 4, bytes left 31 > ipconfig: got offer from 0.0.0.0 > ipconfig: lease=86400 > ipconfig: server=192.168.1.1 sname= > ipconfig: parsebootp: new packet > ipconfig: parseoptions: type(53) len 1, bytes left 58 > ipconfig: parseoptions: serverid(54) len 4, bytes left 55 > ipconfig: parseoptions: lease(51) len 4, bytes left 49 > ipconfig: parseoptions: ipmask(1) len 4, bytes left 43 > ipconfig: parseoptions: ipgw(3) len 4, bytes left 37 > ipconfig: parseoptions: dns(6) len 4, bytes left 31 > ipconfig: got ack from 0.0.0.0 > ipconfig: lease=86400 > ipconfig: ipaddr=192.168.1.25 ipmask=255.255.255.0 > ipconfig: ipgw=192.168.1.1 > ipconfig: dns=192.168.1.1 > ipconfig: server=192.168.1.1 sname= > term% cat /net/ndb > ip=127.0.0.1 ipmask=/104 ipgw=:: > sys=gnot > sys=gnot > dns=192.168.1.1 > > Does anyone know how I might go about solving the problem? > > Thanks, > Peter > > [1]: http://9fans.net/archive/2013/08/31 >
