From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <971AAC0D-143C-4B6E-A856-A325E163D3F0@corpus-callosum.com> Date: Sun, 18 May 2014 15:55:33 -0700 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e013d0ce84a741c04f9b48b70 Subject: Re: [9fans] syscall 53 Topicbox-Message-UUID: e826b168-ead8-11e9-9d60-3106f5b1d025 --089e013d0ce84a741c04f9b48b70 Content-Type: text/plain; charset=UTF-8 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.tavakkolian@gmail.com> wrote: > 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 wrote: > >> >> > * 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. >> >> >> >> > --089e013d0ce84a741c04f9b48b70 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
fyi, pulling/merging (e.g. adding IL back), building the k= ernels, booting and building the binaries works as expected for all cpu typ= es in my environment (pc, bcm, rb and kw).



On Sun, May 18, 2014 at 9:03 AM, Skip Ta= vakkolian <skip.tavakkolian@gmail.com> wrote:
rebuilding/installing the binaries from local sources take= s very little time and guarantees that pull will not overwrite them (unless= forced).



On Sun, May 18, 2014 at 8:38 AM, Jeff Sickel <jas@corpus-callosum.com> wrote:

> * pull only /sys/src/9

=C2=A0* 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. =C2=A09fs dump triggered the syscall error.





--089e013d0ce84a741c04f9b48b70--