From: jmk@plan9.att.com jmk@plan9.att.com
Subject: differences between cdrom and pcdist
Date: Tue, 26 Sep 1995 10:08:09 -0400 [thread overview]
Message-ID: <19950926140809.wtoF4TQ2ia0sinARjStgRoylwRiu0ilS_6-RCgypz-E@z> (raw)
not all changes have make it out, the important ones have.
the pcdist binaries come from the running system.
there are no systems using the 29000, there was interest at one time
in writing some code for an embedded product.
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Tue Sep 26 00:42:37 EDT 1995
Received: by colossus.cse.psu.edu id <78453>; Tue, 26 Sep 1995 00:26:47 -0400
Received: from cannon.ecf.toronto.edu ([128.100.8.5]) by colossus.cse.psu.edu with SMTP id <78446>; Tue, 26 Sep 1995 00:26:31 -0400
Received: by cannon.ecf.toronto.edu id <1013>; Tue, 26 Sep 1995 00:26:21 -0400
From: Steve Kotsopoulos <steve@ecf.toronto.edu>
To: 9fans@cse.psu.edu
Subject: differences between cdrom and pcdist
Message-Id: <95Sep26.002621edt.1013@cannon.ecf.toronto.edu>
Date: Tue, 26 Sep 1995 00:26:21 -0400
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
I noticed that /386/bin/ar /386/bin/ftpfs and /386/bin/sed are different
between the cdrom and pcdist, but couldn't find any mention of bug fixes
or other changes in the errata or updates area. Are there source patches?
Also, /sys/include/a.out.h and /sys/include/mach.h include definitions
for an AMD 29000 platform. Which systems use that processor?
next reply other threads:[~1995-09-26 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-26 14:08 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-26 4:26 Steve
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=19950926140809.wtoF4TQ2ia0sinARjStgRoylwRiu0ilS_6-RCgypz-E@z \
--to=jmk@plan9.att.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 NNTP newsgroup(s).