From: geoff@plan9.bell-labs.com
To: pgentry@blueyonder.co.uk, 9fans@cse.psu.edu
Subject: Re: [9fans] CD Image problem
Date: Wed, 29 Aug 2007 20:12:21 -0400 [thread overview]
Message-ID: <e3fde5957abf5bcb35553ae2ad72e44d@plan9.bell-labs.com> (raw)
In-Reply-To: <wqHAi.152437$lx3.43198@fe3.news.blueyonder.co.uk>
Yesterday's image seems to have been truncated; I'm not sure why.
Today's image looks like it's the right size.
34425 --rw-rw-r-- M 8 sys sys 35250903 Aug 29 04:59 plan9.iso.bz2
4445 --rw-rw-r-- M 8 sys sys 4551165 Aug 28 04:46 plan9.iso.bz2.old
next prev parent reply other threads:[~2007-08-30 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 9:10 Peter
2007-08-29 9:39 ` Bakul Shah
2007-08-30 0:12 ` geoff [this message]
2007-08-30 2:49 ` geoff
2007-08-30 3:32 ` Uriel
2007-08-30 4:23 ` geoff
2007-08-30 6:03 ` Uriel
2007-08-30 11:09 ` erik quanstrom
2007-08-30 15:42 ` geoff
2007-08-30 6:07 ` Peter Gentry
2007-08-30 15:30 ` geoff
2007-08-30 17:40 ` Axel Belinfante
2007-08-31 7:53 ` Peter Gentry
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=e3fde5957abf5bcb35553ae2ad72e44d@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=pgentry@blueyonder.co.uk \
/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).