From: Lucio De Re <lucio@proxima.alt.za>
To: Russ Cox <rsc@plan9.bell-labs.com>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] big pull
Date: Mon, 23 Jun 2003 12:49:04 +0200 [thread overview]
Message-ID: <20030623124903.Q2250@cackle.proxima.alt.za> (raw)
In-Reply-To: <7c507c45132a212a9ae4444aa4ba2f53@plan9.bell-labs.com>; from Russ Cox on Mon, Jun 23, 2003 at 06:35:14AM -0400
On Mon, Jun 23, 2003 at 06:35:14AM -0400, Russ Cox wrote:
>
> The next pull will be a big one.
> Due to various changes in the C library,
> basically all the system binaries changed,
> so it seemed like a good time to sync up.
>
Russ,
will you release a new ISO image at the same time, please? With a
release identifier in it?
I'm a little lost here with the number of versions that I have
managed to accumulate, and a final issue would have a very salutary
effect.
My biggest problem, sadly, is that I don't seem to be able to bring
the base system up to speed. After a pull update from a CD-ROM
image I generated myself, a "diff -r" between the source and
destination yields quite a lot of discrepancies :-(
If one can't be sure of having a consistent system (which could be
caused, of course by a number of anomalies, for example, I had an
empty /sys/src/9/pc/apic.c on the Fossil server :-( then things
get a bit rough.
I'm not sure how one goes about sanity checking the system, but it
would be good if replica had a tool to do something of a check.
Hm, maybe it does, but not explicitly. I'm a lazy person and fail
to see things that are not spelled out to me.
++L
PS: And thanks to you and all the team contributors for your efforts
and all the benefit you have bestowed on us. To paraphrase a trite
cinema character: "We're not worthy!"
PPS: I meant to ask you this a while back, but keep treating it as
not important enough to warrant a separate mail message: where is
the U9FS source that has been released separately? Is a link to
it from the Plan 9 pages not perhaps warranted?
next prev parent reply other threads:[~2003-06-23 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 10:35 Russ Cox
2003-06-23 10:49 ` Lucio De Re [this message]
2003-06-23 10:56 ` Lucio De Re
2003-06-24 2:20 ` Russ Cox
2003-06-23 14:02 ` Joel Salomon
2003-06-23 14:03 ` boyd, rounin
2003-06-23 14:20 ` Joel Salomon
2003-06-24 2:18 ` Russ Cox
2003-06-24 3:05 ` okamoto
2003-06-25 0:26 ` Russ Cox
2003-06-25 2:38 ` okamoto
2003-06-25 7:48 ` Fco.J.Ballesteros, nemo
2003-06-25 7:50 ` Lucio De Re
2003-06-25 8:01 ` Fco.J.Ballesteros, nemo
2003-06-25 7:56 ` Lucio De Re
2003-06-25 9:25 ` Richard Miller, miller
2003-06-26 1:57 ` Russ Cox
2003-06-26 9:11 ` Richard Miller, miller
2003-06-26 1:59 ` Russ Cox
2003-06-26 8:10 ` Fco.J.Ballesteros, nemo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030623124903.Q2250@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=rsc@plan9.bell-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).