Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[arnold]

Thanks Erik.

Is it hard to produce a tar ball of .ps or .pdf files from current troff
input?

Thanks,

Arnold

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[erik quanstrom]

i couldn't forward the result in email.  see

	/n/sources/contrib/quanstro/doc.tbz

- erik

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Aharon Robbins]

> /n/sources/contrib/quanstro/doc.tbz

THANKS!  Copying now (via 9pfuse).

Arnold

[9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[arnold]

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.

Thanks!

Arnold

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Anthony Sorace]

[-- 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 --]

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Anthony Sorace]

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

> Stick with the source if you have doubts.

Actually, that's not even necessary. The online HTML
version gets the latest changes. You'll only need the
sources if you want to generate PS/PDF explicitly, say
for printing.

Anthony


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Aharon Robbins]

Hi Anthony.

Thanks for the answers.

> > 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.

OK.

> 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).

Is anyone updating at least the troff versions of the papers? That is,
if I go with the source, will I get something (more) current?

> > Stick with the source if you have doubts.
>
> Actually, that's not even necessary. The online HTML
> version gets the latest changes. You'll only need the
> sources if you want to generate PS/PDF explicitly, say
> for printing.

Well, actually printing is what I had in mind, but maybe I'm being
too much of a luddite.

Has anyone tried producing the doc using groff under Linux, or would
it require a running Plan 9 system to correctly (re)generate everything?

Thanks,

Arnold

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[erik quanstrom]

[437 files]
> Is anyone updating at least the troff versions of the papers? That is,
> if I go with the source, will I get something (more) current?
>
> > > Stick with the source if you have doubts.
> >
> > Actually, that's not even necessary. The online HTML
> > version gets the latest changes. You'll only need the
> > sources if you want to generate PS/PDF explicitly, say
> > for printing.
>
> Well, actually printing is what I had in mind, but maybe I'm being
> too much of a luddite.
>
> Has anyone tried producing the doc using groff under Linux, or would
> it require a running Plan 9 system to correctly (re)generate everything?

some of the .ms are updated ...  here are the most recent.
--rw-rw-r-- M 764 glenda sys  18522 Jun 16  2011 port.ms
--rw-rw-r-- M 764 glenda sys  30524 Oct 13  2011 compiler.ms
--rw-rw-r-- M 764 glenda sys  37928 Jan  6 13:52 comp.ms
--rw-rw-r-- M 764 glenda sys  31666 Jan 21 20:34 asm.ms

there's a mkfile in /sys/doc which should update all the ps.

groff probablly won't do a good job unless you fix the fonts.

- erik

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Taj Khattra]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

>
> Has anyone tried producing the doc using groff under Linux, or would
> it require a running Plan 9 system to correctly (re)generate everything?
>

not sure about groff, but i think they should be reproducible under linux
using plan9port troff.

[-- Attachment #2: Type: text/html, Size: 421 bytes --]

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Anthony Sorace]

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

> Is anyone updating at least the troff versions of the papers? That is,
> if I go with the source, will I get something (more) current?

It varies by paper. Some are updated, some not. The papers on the
compiler suite get some updates, but the 8½ paper not. That paper,
for example, provides a really good view on how one could use the
system principles to construct a window system; the fact that the
current window system is constructed differently doesn't really
change that.

> Well, actually printing is what I had in mind, but maybe I'm being
> too much of a luddite.

Nothing wrong with printing. Having a physical copy of the manual
is invaluable when things go sideways, and reading the papers on
a high-DPI, non-reflective surface is a joy. Since I don't believe
anyone has Plan 9 driving an e-Ink display (anyone? anyone?),
paper does nicely.

> Has anyone tried producing the doc using groff under Linux, or would
> it require a running Plan 9 system to correctly (re)generate everything?

As others have said, I suspect groff will have issues (I have no idea
how to test that locally), but I can confirm that p9p's works as
expected.

Anthony


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]

Re: [9fans] how up to date are the PDF doc files on plan9.bell-labs.com?

[Matthew Veety]

On May 2, 2012, at 4:40 PM, Anthony Sorace wrote:
> Since I don't believe anyone has Plan 9 driving an e-Ink display
> (anyone? anyone?),
> paper does nicely.

Maybe a good addition to the ARM port?

--
Veety