The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: ACM opens up much of its archives
Date: Thu, 26 May 2022 16:13:05 -0500	[thread overview]
Message-ID: <c3501df1-d85f-d072-4678-840c795505a6@technologists.com> (raw)
In-Reply-To: <CAC20D2NECzfE1fE5X_PAmqsFbW2Qz5zjiPCtLU7+pf-N9XH2_Q@mail.gmail.com>

It is disappointing that the SOSP versions are not available, but I 
suspect the real problem here is publication protocol at the time. It 
was often the case that when conference papers were headed for CACM the 
conferences only published the abstracts in the proceedings.

I long abandoned my paper archives that might have included these, so I 
don't know for sure whether the paper proceedings would have had the 
full papers or not.

However, for both the UNIX & Popek/Goldberg papers, the full CACM 
versions do seem to be freely available, with the expected annotation 
"This is a revised version of a paper presented at the Fourth
ACM Symposium on Operating Systems Principles, IBM Thomas
J. Watson Research Center, Yorktown Heights, New York, October
15-17, 1973."

https://dl.acm.org/doi/pdf/10.1145/361011.361061
https://dl.acm.org/doi/pdf/10.1145/361011.361073

On 5/26/2022 3:53 PM, Clem Cole wrote:
> Awe are a little drifting from core UNIX but FWIW:  With the noise made 
> about the ACM DL is more freely available and the 'advertisement' they 
> sent saying the earliest UNIX paper was now there for anyone to examine 
> (from the 1973 SOSP), I just tried to download both without signing in 
> and with -- I got the same result.   You get the abstract - not the 
> paper which was a tad disappointing.  FWIW: from the SOSP was Jerry 
> Popek's famous paper on requirements for VM -- same result.
> 
> I understand the problem, (USENIX also has the same one) but it seems 
> like if they are going to scan things, scan all of it, not just the 
> abstract.
> ᐧ
> 
> On Thu, May 26, 2022 at 4:40 PM Douglas McIlroy 
> <douglas.mcilroy@dartmouth.edu <mailto:douglas.mcilroy@dartmouth.edu>> 
> wrote:
> 
>      >> If you’re a *current* member of these societies then you should
>     have good access to journal content.
> 
>      >I believe this is true for ACM, but for IEEE not so much. You have
>     to pay for a digital library membership _in addition to_ your
>     standard membership
> 
>     ACM is the same.  At $99/year membership is a bargain by ordinary
>     professional society standards. But they charge an additional $99 for
>     access to 21st-century Digital Library.content.
> 
>     Doug
> 

-- 
voice: +1.512.784.7526       e-mail: sauer@technologists.com
fax: +1.512.346.5240         Web: https://technologists.com/sauer/
Facebook/Google/Twitter: CharlesHSauer

  reply	other threads:[~2022-05-26 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 20:39 [TUHS] " Douglas McIlroy
2022-05-26 20:43 ` [TUHS] " Dan Cross
2022-05-26 20:53 ` Clem Cole
2022-05-26 21:13   ` Charles H Sauer (he/him) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-24 23:29 [TUHS] " arnold
2022-05-25 15:53 ` [TUHS] " Clem Cole
2022-05-25 16:00   ` Richard Salz
2022-05-25 16:01     ` Clem Cole
2022-05-26  1:54   ` Larry McVoy
2022-05-26 17:09   ` Henry Mensch
2022-05-26 17:13     ` Dan Cross
2022-05-26 19:49       ` Stephen Kitt

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=c3501df1-d85f-d072-4678-840c795505a6@technologists.com \
    --to=sauer@technologists.com \
    --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).