From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] suicide message on vmware
Date: Fri, 6 Jun 2014 01:00:50 -0700 [thread overview]
Message-ID: <20140606080050.2BF1AB844@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 06 Jun 2014 13:02:14 +0530." <CAA6Yd9WXBn4ppX0yjK0phgkqq9va1FAZ2ADAP99YtUs2XUSGnQ@mail.gmail.com>
On Fri, 06 Jun 2014 13:02:14 +0530 Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> wrote:
> On Fri, Jun 6, 2014 at 11:30 AM, Bakul Shah <bakul@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.
> 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
follow the steps using the old binaries. The following may
be enough.
_dossrv
_mount -c /srv/dos /n/9fat /dev/sdC0/9fat
Unless dossrv is already running (use _ps) and /n/9fat is
already mounted, in which case you will have to _unmount it
and kill dossrv.
next prev parent reply other threads:[~2014-06-06 8:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 3:15 Ramakrishnan Muthukrishnan
2014-06-06 3:21 ` erik quanstrom
2014-06-06 4:05 ` Ramakrishnan Muthukrishnan
2014-06-06 5:18 ` Ramakrishnan Muthukrishnan
2014-06-06 6:00 ` Bakul Shah
2014-06-06 7:32 ` Ramakrishnan Muthukrishnan
2014-06-06 8:00 ` Bakul Shah [this message]
2014-06-06 8:33 ` Ramakrishnan Muthukrishnan
2014-06-06 15:24 ` Bakul Shah
2014-06-06 15:35 ` erik quanstrom
2014-06-06 15:46 ` Ramakrishnan Muthukrishnan
2014-06-06 15:50 ` erik quanstrom
2014-06-06 16:49 ` Bakul Shah
2014-06-06 16:59 ` erik quanstrom
2014-06-06 15:52 ` Ramakrishnan Muthukrishnan
2014-06-06 15:55 ` erik quanstrom
2014-06-06 16:07 ` Ramakrishnan Muthukrishnan
2014-06-06 16:26 ` erik quanstrom
2014-06-06 16:38 ` Ramakrishnan Muthukrishnan
2014-06-07 11:24 ` Ramakrishnan Muthukrishnan
2014-06-07 11:29 ` Aram Hăvărneanu
2014-06-07 14:42 ` erik quanstrom
2014-06-07 17:11 ` Ramakrishnan Muthukrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140606080050.2BF1AB844@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).