The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: <b4udv8@comcast.net>
To: <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIXabilia
Date: Thu, 15 Dec 2022 15:02:48 -0800	[thread overview]
Message-ID: <03d301d910d9$5e463f70$1ad2be50$@comcast.net> (raw)
In-Reply-To: <7786c188-8acf-ecc5-f128-7ee2afface16@ucsb.edu>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

I will PROUDLY take The C Programming Language book off your hands!

 

PayPal ok?

 

Cheers!

 

Don Harrison

 

From: James Frew <frew@ucsb.edu> 
Sent: Thursday, December 15, 2022 2:14 PM
To: tuhs@tuhs.org
Subject: [TUHS] UNIXabilia

 

Having recently emeritated, I'm clearing out my university office and giving away hundreds of books. It occurs to me that some of them may be of interest to some of the folks on this list. (Before you ask, no, you can't have my original printed-on-Kleenex versions of the Lions notes...)

Most of the books are listed here: https://www.librarything.com/catalog/james.frew . They're (alas) utterly uncategorized, but include a fair amount of UNIX, C, and general CS stuff.

I also have some manuals and USENIX conference proceedings even LibraryThing couldn't locate; they're listed in the attached Markdown file. None of these proceedings are online at usenix.org, so I'd be stoked if someone volunteered to scan them.

If you want any of them, let me know, and we'll figure out some way to reimburse me for shipping them. (No charge for the "content".) Or if you're close enough to Santa Barbara, come and get 'em.

Cheers,
/Frew <https://purl.org/frew> 


[-- Attachment #2: Type: text/html, Size: 3296 bytes --]

      parent reply	other threads:[~2022-12-15 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 22:13 [TUHS] UNIXabilia James Frew
2022-12-15 22:41 ` [TUHS] UNIXabilia segaloco via TUHS
2022-12-15 23:37   ` G. Branden Robinson
2022-12-15 23:02 ` b4udv8 [this message]

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='03d301d910d9$5e463f70$1ad2be50$@comcast.net' \
    --to=b4udv8@comcast.net \
    --cc=tuhs@tuhs.org \
    /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).