From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f529df46e1e55bfc99f46e442a9c58d3@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] suggestion: avoiding out of date binaries
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
In-Reply-To: <9ecfac33ae83c9838c5e1ad9f978f668@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 19 May 2003 09:25:45 +0200
Topicbox-Message-UUID: b217678c-eacb-11e9-9e20-41e7f4b1d025

I see. That's nice. I'm very happy to know that sources binaries are kept
updated.

Now that you ask,
the binaries were paqfs and mkpaqfs for the arm as well as 5[cla] for the
pc. What happen was that a freshly recompiled bitsy kernel was not able to
attach to the paqdisk nor to file servers. I just recompiled 5[cla] and
then recompiled /sys/src/paqfs for the arm and everything got working.

This is what outofdate said for 5c, for example.

; outofdate /386/bin/5c
/386/bin/5c: /386/include/u.h
/386/bin/5c: /sys/include/libc.h
/386/bin/5c: /sys/src/cmd/cc/dcl.c
/386/bin/5c: /sys/src/cmd/cc/dpchk.c
/386/bin/5c: /sys/src/libc/9sys/dirstat.c
/386/bin/5c: /sys/src/libc/fmt/dofmt.c


thanks a lot for your replies