I will use pull -n from now on. But it will still not help if one needs to
recompile kernel with new syscalls or similar. Erics procedure helps to recover
to old state, but i never tried it, it may be that some commands needed new
syscall too, i tried to copy to 9fat with same error, maybe it
The safe way to upgrade your file server is simply to update the kernel
binaries (for example, with the ones I'm providing) on your 9fat and reboot.
Then, you can pull the updated program binaries from /n/sources.
There is no need to wait, because you have to be running the new kernel
before
note to self: add /dev/sdE?/9fat to vac
streamline getting 9LOAD in place w/o corruption
i got the impression that sources were in some inconsistent state.
if the only change is the new system call, isn't it sufficient to:
* pull only /sys/src/9
* build the kernels you need and install on boot medium
* reboot
* pull again and rebuild all the binaries
since existing binaries would
0intro's last paragraph says the same thing.
On Sun, May 18, 2014 at 8:32 AM, Skip Tavakkolian
skip.tavakkol...@gmail.com wrote:
i got the impression that sources were in some inconsistent state.
if the only change is the new system call, isn't it sufficient to:
* pull only /sys/src/9
*
* pull only /sys/src/9
* pull -s sys/src/libc
* build the kernels you need and install on boot medium
* reboot
I recovered by using 9fs snap so I could get an earlier state
of /386. 9fs dump triggered the syscall error.
rebuilding/installing the binaries from local sources takes very little
time and guarantees that pull will not overwrite them (unless forced).
On Sun, May 18, 2014 at 8:38 AM, Jeff Sickel j...@corpus-callosum.comwrote:
* pull only /sys/src/9
* pull -s sys/src/libc
* build the kernels
fyi, pulling/merging (e.g. adding IL back), building the kernels, booting
and building the binaries works as expected for all cpu types in my
environment (pc, bcm, rb and kw).
On Sun, May 18, 2014 at 9:03 AM, Skip Tavakkolian
skip.tavakkol...@gmail.com wrote:
rebuilding/installing the
On Sun May 18 18:56:49 EDT 2014, skip.tavakkol...@gmail.com wrote:
fyi, pulling/merging (e.g. adding IL back), building the kernels, booting
and building the binaries works as expected for all cpu types in my
environment (pc, bcm, rb and kw).
i'd put a vote into restoring il to the standard
On May 18, 2014, at 8:54 PM, erik quanstrom quans...@quanstro.net wrote:
On Sun May 18 18:56:49 EDT 2014, skip.tavakkol...@gmail.com wrote:
fyi, pulling/merging (e.g. adding IL back), building the kernels, booting
and building the binaries works as expected for all cpu types in my
i'd put a vote into restoring il to the standard kernels. there's no
downside.
My vote, too.
++L
Great
machine, on 9atom.
Which raises another question: are 9atom and 9front in synch with the
BL distribution (itself in question) regarding syscall 53?
++L
12 matches
Mail list logo
