From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <03ee01c3d6a8$37fb9430$640aa8c0@chrislamrock>
From: "Chris Lamrock" <chris@blackwidowguitars.com>
To: <9fans@cse.psu.edu>, "David Presotto" <presotto@closedmind.org>
References: <7dd606cf1883011837c57ebf97be1de5@plan9.bell-labs.com>
Subject: Re: [9fans] bind: exec header invalid
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Fri,  9 Jan 2004 07:00:47 -0500
Topicbox-Message-UUID: b48e9f8e-eacc-11e9-9e20-41e7f4b1d025

Okay I looked into this last night & found:

/386/bin/bind was of 0 file size
as was /bin/bind

soooo I did a complete reinstall - guess what?!?  Everything is fine!  I'm
not sure what happened, but chances are I had some sort of media failure
while installing.

Thanks to all who helped!  Now I can start playing with it tonight - can't
wait!

-Chris Lamrock


----- Original Message -----
From: "David Presotto" <presotto@closedmind.org>
To: <chris@blackwidowguitars.com>
Sent: Thursday, January 08, 2004 11:54 AM
Subject: Re: [9fans] bind: exec header invalid


> /386/bin/bind, the one with the bad exec header.  I take it
> you haven't created your own program called bind that
> you're trying to exec instead.  You might try
> explicitly typing
>
> /386/bin/bind -a '#l' /net
>
> to see if that might have been the case.
>
> screwed because the only way you can get at resources is
> to bind them, and if you can't bind them, ...
>
> You might try remaking just bind but fossil is pretty
> solid and having files come out bad usually means disk
> errors or some accident on your part (like copying something
> onto the file).
>
> To remake
>
> cd /sys/src/cmd
> touch bind.c
> mk bind.install
>
> The touch is just to make sure.  Then
> halt the file system
>
> fshalt
>
> and reboot.  The reboot is just to make sure that binds done
> by /rc/bin/termrc, your profile, etc really get done.