public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: wlestes@wlestes.uncg.edu
To: lark@world.std.com, 2ndsight@taconic.net, blinux-list@redhat.com
Subject: Re: More on "man" and editors
Date: Tue, 22 Dec 1998 18:16:28 -0500	[thread overview]
Message-ID: <199812222316.SAA01029@wlestes.uncg.edu> (raw)
In-Reply-To: <199812201539.AA23419@world.std.com> (lark@world.std.com)

have a look at the following:

ftp.ocf.berkeley.edu:/pub/Library/Computer
http://plan9.bell-labs.com/7thEdMan/index.html

for the 2nd address, i find wget or similar tools to be of great
help in fetching large numbers of pages.

> I imagine that a number of enhanced freeware implementations of standard
> Unix utilities are without standard manpages.  A good resource would 
> probably be the last public Berkeley Standard Distribution manpages.  
> Because these are distributed under the Berkeley license (allowing free
> reproduction and distribution for non-commercial use only, but requiring
> licensing for commercial distribution) they are omitted from commercial
> packages and also from standard FSF-oriented sites, who prefer to only
> allow Copyleft distribution under the GNU Public License.  But the BSD
> manpages can be found on various archive sites.  I don't have a specific
> site at hand, but if nobody else does I'll dig one up...


  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Lar Kaufman
 ` wlestes [this message]
     [not found] <Pine.SUN.3.95.981223181024.1828A-100000@ariel.ucs.unimelb.EDU.AU>
 ` wlestes
     [not found] <199812182305.AA11300@world.std.com>
 ` Charles Hallenbeck
  -- strict thread matches above, loose matches on Subject: below --
 Lar Kaufman
 ` Charles Hallenbeck
   ` T.Pospisek's MailLists

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=199812222316.SAA01029@wlestes.uncg.edu \
    --to=wlestes@wlestes.uncg.edu \
    --cc=2ndsight@taconic.net \
    --cc=blinux-list@redhat.com \
    --cc=lark@world.std.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 read-only IMAP folder(s) and NNTP newsgroup(s).