From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?
Date: Wed, 2 May 2012 10:40:46 -0400 [thread overview]
Message-ID: <587DDED9-F4BD-4613-A558-34A336EBBB5F@9srv.net> (raw)
In-Reply-To: <201205021304.q42D4CdK017010@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
> Hi. Do the postscript / PDF files available from http://plan9.bell-labs.com
> reflect the current state of the system? I'm curious about both the reference
> manual and the various files from /sys/doc.
They do not. I've only verified that the most recent changes are not in there; I
can't say how far back that goes. I'm not sure if there's a schedule for
regeneration. Stick with the source if you have doubts.
Note that while /sys/man is expected to describe the current state of the system,
that's not really a good assumption for /sys/doc. Some of those papers describe
aspects of the system that have changes significantly since they were written
(the paper on 8½ being the most obvious example).
Anthony
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]
next prev parent reply other threads:[~2012-05-02 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 13:04 arnold
2012-05-02 14:40 ` Anthony Sorace [this message]
2012-05-02 14:49 ` Anthony Sorace
2012-05-02 17:19 ` Aharon Robbins
2012-05-02 17:44 ` erik quanstrom
2012-05-02 18:37 ` Taj Khattra
2012-05-02 20:40 ` Anthony Sorace
2012-05-02 21:01 ` Matthew Veety
2012-05-03 16:54 ` [9fans] how up to date are the PDF doc files onplan9.bell-labs.com? Tristan
2012-05-03 17:45 ` Aharon Robbins
2012-05-03 17:59 ` Brian L. Stuart
2012-05-03 18:15 ` hiro
2012-05-03 21:12 ` Mohamed
2012-05-03 21:40 ` Anthony Sorace
2012-05-02 18:06 [9fans] how up to date are the PDF doc files on plan9.bell-labs.com? arnold
2012-05-02 18:22 ` erik quanstrom
2012-05-02 18:48 ` Aharon Robbins
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=587DDED9-F4BD-4613-A558-34A336EBBB5F@9srv.net \
--to=a@9srv.net \
--cc=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).