sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: bobf@plan9.research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Sun, 25 Dec 1994 13:13:05 -0500	[thread overview]
Message-ID: <94Dec25.131410est.24152@hawkwind.utcs.utoronto.ca> (raw)


I have a couple of announcements.

First, we have reorganized our distribution directory
and the location of the sam release has changed.
It can now be found at

	ftp://netlib.att.com/netlib/research/sam.msg.Z

or, equivalently

	ftp netlib.att.com
	cd netlib/research
	get sam.msg.Z

The old release location now contains a pointer to this directory.

Second, a new distribution of sam is now available.  It contains
a couple of minor bug fixes and two changes: scrolling menus
and protocol modifications to support processors with 64-bit
addresses.  Dave Hanson not only removed the 32-bit dependencies
from the protocol but also graciously tested the code after it was
integrated into our master version.  He deserves the thanks of Alpha
owners everywhere.

Although the protocol now accommodates 64-bit addresses, some
alignment dependencies remain.  If you are planning to install
sam on a 64-bit processor, please read the paragraph in the README file
(at approximately line 160) that describes the nature of these
dependencies.  No modifications should be needed for 32-bit processors.

The protocol change makes the new sam incompatible with the
previous version.  This should only make a difference if you do
a `sam -r' to a machine running an incompatible version.  If you are
maintaining sam on several systems, I recommend that you update
all of them simultaneously.  Finally, the protocol works for a remote
sam when one processor is 32-bit and the other is 64-bit.


                 reply	other threads:[~1994-12-25 18:14 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=94Dec25.131410est.24152@hawkwind.utcs.utoronto.ca \
    --to=bobf@plan9.research.att.com \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /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).