From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] SunOS 4 documentation
Date: Wed, 12 Apr 2017 19:20:29 -0700 [thread overview]
Message-ID: <20170413022029.GM14143@mcvoy.com> (raw)
In-Reply-To: <08eb864b-784b-28e5-63b3-420cfbc5f684@telegraphics.com.au>
On Wed, Apr 12, 2017 at 10:13:33PM -0400, Toby Thain wrote:
> On 2017-04-12 7:31 PM, Larry McVoy wrote:
> >All done in troff I believe. Though not for long, I think they switched
> >to framemaker around then.
> >
> >Whoops, I'm wrong, I looked, that's clearly framemaker. Sigh. I love me
> >some troff, even to this day. I really really really wish that someone
> >had done framemaker, word, whatever, that was the GUI interface that had
> >troff under the covers. Why? Because you can version control the source
>
> You can get really really close to that dream with TeX based tools like LyX,
> etc (and indeed Blue Sky Research had a wysiwyg TeX system back in the late
> 1980s).
I know, my dad wrote a book with Blue Sky Research's stuff.
> While troff can get stuff done in its area, for heavy duty work and exacting
> typography, TeX's markup blows troff out of the water, I am afraid.
I'd like to learn more about that. I'd done a ton of stuff in troff,
had to do a paper recently in LaTex and I did not find it at all better.
It was a technical paper, usual stuff, text and tables and figures
and references. I'm not great at LaTex so maybe it's just my bias
but I really like troff. In fairness, I like groff, I got James to hack
some stuff into pic for me.
But it started with troff. I still remember walking out of the computer
science bookstore with a copy of the troff manual. That was sort of my
introduction to Unix and it fits.
> --Toby
> (typesetter/typographer/TeX porter)
>
> >and diffs will actually make sense. Best of luck doing that with any
> >GUI editor.
> >
> >On Wed, Apr 12, 2017 at 03:55:30PM -0700, Cory Smelosky wrote:
> >>Found it.
> >>
> >>http://bitsavers.trailing-edge.com/pdf/sun/sunos/4.1/800-3805-10A_System_and_Network_Administration_199003.pdf
> >>
> >>On Wed, Apr 12, 2017, at 14:54, Cory Smelosky wrote:
> >>>All,
> >>>
> >>>Does anyone have SunOS 4 documentation?
> >>>
> >>>I am trying to properly configure UUCP and I am unable to find proper
> >>>documentation.
> >>>
> >>>--
> >>> Cory Smelosky
> >>> b4 at gewt.net
> >>
> >>
> >>--
> >> Cory Smelosky
> >> b4 at gewt.net
> >
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2017-04-13 2:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 21:54 Cory Smelosky
2017-04-12 22:55 ` Cory Smelosky
2017-04-12 23:31 ` Larry McVoy
2017-04-13 2:13 ` Toby Thain
2017-04-13 2:16 ` Steve Nickolas
2017-04-13 2:25 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 14:25 ` Nemo
2017-04-13 15:41 ` Andreas Kusalananda Kähäri
2017-04-13 16:35 ` Toby Thain
2017-04-13 2:20 ` Larry McVoy [this message]
2017-04-13 13:41 ` [TUHS] " Steffen Nurpmeso
2017-04-13 15:40 ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 23:22 ` Steffen Nurpmeso
2017-04-14 0:40 ` Greg 'groggy' Lehey
2017-04-14 1:59 ` Nemo
2017-04-14 3:00 ` Toby Thain
2017-04-14 2:59 ` Toby Thain
2017-04-14 13:38 ` Steffen Nurpmeso
2017-04-14 13:56 ` Michael Kerpan
2017-04-14 16:55 ` Steffen Nurpmeso
2017-04-14 22:24 ` Toby Thain
[not found] ` <CAHfSdrVAnPn3hwFR0ie0o-yuqGX0hu+LWweNZngpoY4=efTSaA@mail.gmail.com>
2017-04-15 14:23 ` Michael Kerpan
2017-04-15 15:09 ` Toby Thain
2017-04-15 16:07 ` [TUHS] TeX/troff/typesetting markups - " Mutiny
2017-04-15 21:48 ` Dave Horsfall
2017-04-15 22:12 ` ron minnich
2017-04-16 0:02 ` Dave Horsfall
2017-04-15 15:27 ` [TUHS] TeX/troff/typesetting markups - " Clem Cole
2017-04-15 17:05 ` Toby Thain
2017-04-15 17:10 ` Toby Thain
2017-04-18 4:49 ` Greg 'groggy' Lehey
2017-04-14 13:07 ` Wolfgang Helbig
2017-04-14 20:56 ` Clem Cole
2017-04-16 13:42 ` Tim Bradshaw
2017-04-13 14:14 ` [TUHS] " Nemo
2017-04-13 16:34 ` Steve Simon
2017-04-13 23:14 ` Steffen Nurpmeso
2017-04-14 8:30 ` Steve Simon
2017-04-14 13:21 ` Steffen Nurpmeso
2017-04-13 13:28 ` John Labovitz
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=20170413022029.GM14143@mcvoy.com \
--to=lm@mcvoy.com \
/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).