From: Ken Perry <whistler@blinksoft.com>
To: blinux-list@redhat.com
Subject: Books
Date: Wed, 11 Dec 1996 13:59:45 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.3.95.961211135413.24455H-100000@blinksoft.com> (raw)
I just want to rave about the support I am getting from a publisher. This
does fit this mailing list cause it gives good programing information on
unix and linux. This publisher has two books they are named as follows
Begining Programing in Linux
Instant Unix.
I found the books on a web page with an addy of:
http://www.wrox.com
I wrote the author and he say he will be more than happy to put the books
into a text format and sell them to me that way! So incase any of you
MsDos C programmers who want to learn all about Linux programming are
having as much trouble finding true docs on all the little things like
Socket programming forking and yes this book even has a chapter on TCL
(what emacs speak runs on) Go check out the web page and don't be affraid
to write the author and ask for them in text format I just thought I would
let you know there are some people out there with a clue grin.
Ken /whistler
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.3.95.961211135413.24455H-100000@blinksoft.com \
--to=whistler@blinksoft.com \
--cc=blinux-list@redhat.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).