[9fans] syscall 53

Hello, help please, after recent (15 May) pull: mntgen 31: bad sys call number 53 pc 813f ipconfig, keyfs, webfs webcookies, faces = the same. ls -l for example shows ls 222: bad sys call number 53 pc bb8f ls 222: suicide: sys: bad sys call pc=0xbb8f acid leads to /sys/src/libc/386/main9.s:16

Re: [9fans] syscall 53

On Sat May 17 06:28:02 EDT 2014, puta2001-...@yahoo.com wrote: Hello, help please, after recent (15 May) pull: mntgen 31: bad sys call number 53 pc 813f ipconfig, keyfs, webfs webcookies, faces = the same. ls -l for example shows ls 222: bad sys call number 53 pc bb8f ls 222: suicide:

Re: [9fans] syscall 53

it requires 3 syscalls and not two, and takes about 2x as long. it's still good grief. s/two/one/. - erik

Re: [9fans] syscall 53

Since the kernels on /n/sources haven't been recompiled yet, I've uploaded an archive with the 9pcf and 9pccpuf kernel binaries. In case you pulled the updated binaries and aren't able to use you system anymore, you can just replace the 9fat kernels with them.

[9fans] syscall 53

Thanks, tried to compile kernel with no luck cause of the same syscall 53. Was postponing some kind of dump file system until it finally got me :) webfs needs 53,  so no internet. Will load some linux and copy kernels into 9fat. thanks.

Re: [9fans] syscall 53

On Sat May 17 09:55:16 EDT 2014, puta2001-...@yahoo.com wrote: Thanks, tried to compile kernel with no luck cause of the same syscall 53. Was postponing some kind of dump file system until it finally got me :) webfs needs 53,  so no internet. Will load some linux and copy kernels into

[9fans] syscall 53

Already copied kernels to 9fat, all is working fine, seems plan9 got a bit faster generaly.

Re: [9fans] syscall 53

p.s. Caps lock is not working. Also copying in 9fat directory shifts file time current time+3 hours, even +6 hours if renaming (mv). My timezone is +3 GMT. Its native plan9 on ibm t42.

Re: [9fans] syscall 53

A lot more than Caps lock is not working…. This has been some of the worst 36+ hours I’ve had w/ Plan 9, and no end in site to get everything running again. I sure hope the NSEC change is worth it in the long run. I did want to write some Go code yesterday, but this rebuild has eaten up most of

Re: [9fans] syscall 53

s/site/sight/ Might not be so bad… one day, but it does mean that handling the stand-alone file server needs to have a few more controls in place to prevent a pull. -jas On May 17, 2014, at 4:17 PM, Jeff Sickel j...@corpus-callosum.com wrote: A lot more than Caps lock is not working…. This

Re: [9fans] syscall 53

thanks for the heads-up. i'll wait pulling from sources for now. On Sat, May 17, 2014 at 2:17 PM, Jeff Sickel j...@corpus-callosum.comwrote: A lot more than Caps lock is not working…. This has been some of the worst 36+ hours I’ve had w/ Plan 9, and no end in site to get everything running

Re: [9fans] syscall 53

On Sat May 17 15:16:03 EDT 2014, puta2001-...@yahoo.com wrote: p.s. Caps lock is not working. Also copying in 9fat directory shifts file time current time+3 hours, even +6 hours if renaming (mv). My timezone is +3 GMT. Its native plan9 on ibm t42. the standard plan 9 key map maps caps

Re: [9fans] syscall 53

thanks for the heads-up. i'll wait pulling from sources for now. I guess we need one of two alternatives at this point: either somebody documents how to recover from a pull by first reconstructing (or binding from the dump) the critical commands or we are given some indication by Bell Labs so