Re: [9fans] suicidal sam

Re: [9fans] suicidal sam

[Thomas West]

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
>
>

Re: [9fans] suicidal sam

[Russ Cox]

don't bother with disk/format.
you should be able to do

	9fat:
	cp /386/9load /386/9pcdisk /n/9fat
	unmount /n/9fat

russ

[9fans] suicidal sam

[Thomas West]

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

Re: [9fans] suicidal sam

[rob pike]

>
> 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