From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] finding help in v7 in 1980
Date: Fri, 10 Nov 2017 18:18:56 +0000 [thread overview]
Message-ID: <20171110181856.GF994@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <0d7c61c7-7f5a-1854-64c3-737f4de1233c@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On 10 Nov 2017 12:00 -0600, from will.senn at gmail.com (Will Senn):
> In V7, it's trickier because apropos doesn't exist, or the
> functional equivalent man -k, for that matter and books are hard to
> find (most deal with System V or BSD. I do find the command 'find
> /usr/man -name "*" -a -print | grep task' to be useful in finding
> man pages, but it's not as general as apropos.
>
> So, what was the process of learning unix like in the V7 days? What
> were your goto resources? More than just man and the sources? Any
> particular notes, articles, posts, or books that were really helpful
> (I found the article, not the book, "The Unix Programming
> Environment" by Kernighan and Mashey, to be enlightening
> https://www.computer.org/csdl/mags/co/1981/04/01667315.pdf)?
Semi-related thought, possibly helpful: Did the manuals (I mean the
printed ones) have indexes that were meaningful for such purposes? I'm
thinking something like the output of apropos / man -k, not just a
listing of command names and page numbers.
Sure knowing that the description for how to use ls was in section 1
page 42 might have been _helpful_, but not really for finding out _how
to list files_ in the first place...
--
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
next prev parent reply other threads:[~2017-11-10 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 18:00 Will Senn
2017-11-10 18:06 ` Larry McVoy
2017-11-10 18:12 ` Ralph Corderoy
2017-11-10 19:18 ` Chet Ramey
2017-11-10 18:18 ` Michael Kjörling [this message]
2017-11-10 18:19 ` Ralph Corderoy
2017-11-10 18:21 ` Ron Natalie
2017-11-10 19:15 ` Jon Forrest
2017-11-10 19:20 ` Ron Natalie
2017-11-10 19:47 ` William Pechter
2017-11-10 19:51 ` Bakul Shah
2017-11-11 16:46 ` Nemo
2017-11-10 18:32 Noel Chiappa
2017-11-10 19:35 ` Clem Cole
2017-11-10 22:28 ` Dave Horsfall
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=20171110181856.GF994@h-174-65.A328.priv.bahnhof.se \
--to=michael@kjorling.se \
/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).