From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9c2bc5209eebb5231039a853b9c737d1@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: <7cf0f110637fa5f27d15f4de1b76ac66@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:13:27 +0200
Topicbox-Message-UUID: b20a207c-eacb-11e9-9e20-41e7f4b1d025

> Which binaries in particular were out of date?  That isn't
> supposed to happen anymore.
> Perhaps you weren't pulling the binaries because you'd
> compiled them before (and thus they're locally modified).

Almost all the binaries are out of date here. I just checked and I
think that happens on sources too. For example:

; ; ls -l (/n/sources/plan9/ /)^sys/include/libc.h
--rw-rw-r-- M 63 glenda sys 18829 Apr  4 05:13 /n/sources/plan9/sys/include/libc.h
--rw-rw-r-- M  9 sys    sys 18829 Apr  4 05:13 /sys/include/libc.h
; ls -l (/n/sources/plan9/ /)^386/bin/rc
--rwxrwxr-x M  9 sys    sys 140122 Feb 18 04:14 /386/bin/rc
--rwxrwxr-x M 63 glenda sys 140122 Feb 18 04:14 /n/sources/plan9/386/bin/rc

That's what outofdate says, in fact.

; outofdate /386/bin/rc
/386/bin/rc: /sys/include/libc.h