From: Scott Schwartz schwartz@bio.cse.psu.edu
Subject: [9fans] seek offset
Date: Fri, 18 Sep 1998 13:37:53 -0400 [thread overview]
Message-ID: <19980918173753.3WRYGseKNWVz7ls210j8T726Qimizie9NTls3VpPWgc@z> (raw)
arisawa@ar.aichi-u.ac.jp writes:
| It was easy to fix b.com.
Maybe we should collect the improved versions of b.com and devata
somewhere? If you send the boddle to the list it will get into the
archives at least.
What's the situation with >2gb scsi disks?
next reply other threads:[~1998-09-18 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-18 17:37 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-09-19 2:00 arisawa
1998-09-18 6:21 arisawa
1998-09-17 3:03 Russ
1998-09-17 2:37 arisawa
1998-09-16 14:09 rob
1998-09-16 13:12 jmk
1998-09-16 12:10 Russ
1998-09-16 7:02 arisawa
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=19980918173753.3WRYGseKNWVz7ls210j8T726Qimizie9NTls3VpPWgc@z \
--to=9fans@9fans.net \
/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).