From: don bailey <don.bailey@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ATAPI document
Date: Thu, 14 Feb 2008 14:29:39 -0700 [thread overview]
Message-ID: <47B4B2C3.3040000@gmail.com> (raw)
In-Reply-To: <66a83e62001c5015c16e7a32e194cb32@quanstro.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> i remember the draft t13 standards being free on the t13 website.
>
I had a whole mirror of t13.org's documents.
At one point you could actually download the spec under some user's
directory on their FTP. I'm sure they're still there in some form or
another.
D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHtLK7yWX0NBMJYAcRAvDkAKCXC67+21Sn7GR4lMqCDLn3StcIEQCgp2pq
StWl/ZjG5vGaJ39yK2nKvoI=
=a7E1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-14 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 20:14 ron minnich
2008-02-14 20:25 ` erik quanstrom
2008-02-14 21:29 ` don bailey [this message]
2008-02-14 22:46 ` Michaelian Ennis
2008-02-15 16:24 ` jmk
2008-02-15 16:30 ` jmk
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=47B4B2C3.3040000@gmail.com \
--to=don.bailey@gmail.com \
--cc=9fans@cse.psu.edu \
/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).