* Re: [9fans] suicidal sam
@ 2001-04-30 13:53 rob pike
0 siblings, 0 replies; 4+ messages in thread
From: rob pike @ 2001-04-30 13:53 UTC (permalink / raw)
To: 9fans
>
> sam dies for files with sizes somewhere between 5K and 40K with the
> following message:
>
> sam 157: bad sys call number 51 pc 114e2
> sam 157: suicide: sys: bad sys call pc=0x000114e2
> samterm: host read error:
>
> The binary is correct fot the latest update (0425):
> md5sum /bin/sam
> 12113961fbf0d7fae04a18929142d82f /bin/sam
> Any ideas welcomed.
/sys/src/libc/9syscall/sys.h shows that 51 is PWRITE, a new system
call that the sam binary is using but your kernel apparently does not
have installed. You are probably running a new sam on an old-release
kernel.
-rob
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] suicidal sam
@ 2001-05-03 14:01 Thomas West
0 siblings, 0 replies; 4+ messages in thread
From: Thomas West @ 2001-05-03 14:01 UTC (permalink / raw)
To: 9fans
I did indeed have an inconsistent 9pcdisk and 9load, as Rob guessed.
I now have 9pcdisk and 9load with current md5sums in /386.
I propose to install them on my 'D' drive with the following
commands:
disk/kfscmd allow
disk/format -b /386/pbs -d -r 2 /dev/sdD0/9fat /386/9load /386/9pcdisk
plan9.ini
Is this the correct way to install these files?
Generally, are there any other files that are not actually installed by
/wrap/inst and that I should install?
Tom-
----- Original Message -----
From: rob pike <rob@plan9.bell-labs.com>
To: <9fans@cse.psu.edu>
Sent: Monday, April 30, 2001 6:53 AM
Subject: Re: [9fans] suicidal sam
> >
> > sam dies for files with sizes somewhere between 5K and 40K with the
> > following message:
> >
> > sam 157: bad sys call number 51 pc 114e2
> > sam 157: suicide: sys: bad sys call pc=0x000114e2
> > samterm: host read error:
> >
> > The binary is correct fot the latest update (0425):
> > md5sum /bin/sam
> > 12113961fbf0d7fae04a18929142d82f /bin/sam
> > Any ideas welcomed.
>
> /sys/src/libc/9syscall/sys.h shows that 51 is PWRITE, a new system
> call that the sam binary is using but your kernel apparently does not
> have installed. You are probably running a new sam on an old-release
> kernel.
>
> -rob
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] suicidal sam
@ 2001-05-02 23:05 Russ Cox
0 siblings, 0 replies; 4+ messages in thread
From: Russ Cox @ 2001-05-02 23:05 UTC (permalink / raw)
To: 9fans
don't bother with disk/format.
you should be able to do
9fat:
cp /386/9load /386/9pcdisk /n/9fat
unmount /n/9fat
russ
^ permalink raw reply [flat|nested] 4+ messages in thread
* [9fans] suicidal sam
@ 2001-05-01 3:58 Thomas West
0 siblings, 0 replies; 4+ messages in thread
From: Thomas West @ 2001-05-01 3:58 UTC (permalink / raw)
To: 9fans
sam dies for files with sizes somewhere between 5K and 40K with the
following message:
sam 157: bad sys call number 51 pc 114e2
sam 157: suicide: sys: bad sys call pc=0x000114e2
samterm: host read error:
The binary is correct fot the latest update (0425):
md5sum /bin/sam
12113961fbf0d7fae04a18929142d82f /bin/sam
Any ideas welcomed.
Thanks
-Tom
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-05-03 14:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-30 13:53 [9fans] suicidal sam rob pike
2001-05-01 3:58 Thomas West
2001-05-02 23:05 Russ Cox
2001-05-03 14:01 Thomas West
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).