Hi, On Fri, Jun 6, 2014 at 1:30 PM, Bakul Shah <ba...@bitblocks.com> wrote: > On Fri, 06 Jun 2014 13:02:14 +0530 Ramakrishnan Muthukrishnan > <vu3...@gmail.com> wrote: >> On Fri, Jun 6, 2014 at 11:30 AM, Bakul Shah <ba...@bitblocks.com> wrote: >> > On Fri, 06 Jun 2014 10:48:21 +0530 Ramakrishnan Muthukrishnan <vu3rdd@gmail >> .com> wrote: >> >> Well, looks like I cannot run any binaries anymore and getting the >> >> suicide message! I don't have anything critical on this vm image and >> >> can re-install it. But I want to see if I can recover it and how. I >> >> will re-read the "syscall 53" thread to look for any solutions. >> > >> > Aren't the old binaries saved under the same name but >> > prefixed with _? If you haven't rebooted yet, you can use >> > those to copy the new kernel to the FAT partition. >> >> Thanks, I didn't know that old binaries are kept prefixed with _. Very nice! >> >> I copied the kernels from David (9legacy.org/download/kernel.tar.bz2), >> untar'ed it. This copied into /386/9pcf. Then I do: > > I don't know what's on 9legacy.org. Copy the labs kernel from > /386/9pcf since after reboot it will support the updated labs > binaries that use nsec() syscall. > > My assumption is you are running an old kernel with new > binaries.
Yes. >> 9fat: >> _cp /386/9pcf /n/9fat/9pcf >> >> But I get an error message: '/n/9fat/9pcf clone failed'. > > 9fat: will use the new binaries! Look at /rc/bin/9fat: and Ah, that's right. Thanks. > follow the steps using the old binaries. The following may > be enough. > > _dossrv > _mount -c /srv/dos /n/9fat /dev/sdC0/9fat Worked perfectly! Thanks. -- Ramakrishnan
