From: "Brian L. Sellden" <Brian@henge.com>
To: sholmes@primenet.com
Cc: lark@world.std.com, blinux-list@redhat.com
Subject: Re: Linux Documentation accessability
Date: Wed, 27 Nov 1996 17:26:13 -0700 [thread overview]
Message-ID: <199611280026.RAA00433@zygote.ivory.com> (raw)
In-Reply-To: <329cc278.2574664@mailhost.primenet.com> (sholmes@primenet.com)
Hello,
Most (all?) of the LDP manuals are already available
in html format. You can get them from:
http://sunsite.unc.edu/mdw/linux.html
>From this site, you can get the Installation and getting
Started Guide, the System Administrator's Guide,
the Network Administrator's Guide, Kernel Hacker's guide,
Regards,
Brian.
--
---------------
Brian L. Sellden - brian@henge.com, brians@usa.net
User of Emacspeak 4.0, making Unix talk.
http://www.henge.com/~brian
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Lar Kaufman
` Steve Holmes
` Peter Nilsson
` Brian L. Sellden [this message]
` Luke Davis
` Alexandre Khalil
` Steve Holmes
` Lar Kaufman
-- strict thread matches above, loose matches on Subject: below --
Steve Holmes
` Burchard Steinbild
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=199611280026.RAA00433@zygote.ivory.com \
--to=brian@henge.com \
--cc=blinux-list@redhat.com \
--cc=lark@world.std.com \
--cc=sholmes@primenet.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).