I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Seventh Edition:
http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
Greetings all.
A few weeks ago, in a fit of nostalgia, I decided to gather together
a personal copy of the various Usenet source groups as still available
at places like gatekeeper.dec.com and ftp.uu.net. The result is
a collection of six newsgroups, net.sources, and then
comp.sources.{games,misc,x,unix,reviewed}.
I removed duplicates and fixed a few other archiving goofs as well.
The result is about 700M, uncompressed. It just fits on one CD. :-)
I have made a tarball available, it's about 145M, if anyone wants it.
URLs:
http://www.skeeve.com/Usenet.tar.bz2ftp://ftp.freefriends.org/arnold/upload/Usenet.tar.bz2
Only one compression format; the .gz file is almost 180M.
Enjoy,
Arnold
Hi!
I would like to know which licence the files at
http://medialab.dyndns.org/~martin/tape/stuff/ditroff/
are under.
If it's http://www.tuhs.org/Archive/Caldera-license.pdf
that would be nice, if not, is there any way to find
out whose (c) is on the files, and how to contact them?
Reason: I'm developer of a BSD offspring and already
integrated 4.4BSD-Alpha nroff, neqn, tbl etc. under the
Caldera licence above into our operating system in order
to get rid of the less free, written in C++, GNU groff.
With success. Now I'm lacking postscript output.
Thanks in advance,
//mirabile
"=?ISO-8859-15?Q?Jos=E9?= R. Valverde" <jrvalverde(a)cnb.uam.es> wrote:
> While working at the Biomedical Research Institute (Madrid, Spain) I got a
> quote from DEC for access to Ultrix source code. As I remember it, it wasn't
> that expensive (~1000$ for an academic license) and I mused bout acquiring=
> =20
> it for some time. My na=EFvete at the time prevented me from ordering it (t=
> hat
> and the availability of BSD sources).
Ultrix-32 sources can be found on ifctfvax.Harhan.ORG in
/pub/UNIX/thirdparty/Ultrix-32/sources available via anonymous FTP.
MS
Jose R. Valverde <jr(a)cnb.uam.es> wrote:
> But I understood the orioginal post to refer to other Ultrix sources.
> Ultrix had a long -and interesting- life after 32V. It was ported to
> MIPS machines,
By Ultrix-32 I didn't mean AT&T 32V, I just say Ultrix-32 to distinguish
it from Ultrix-11. Ultrix-32 was DEC's product for VAX and MIPS. On my
FTP site I have pirate sources for Ultrix-32 V2.00 and V4.20. The lalter
runs on all VAX models DEC ever supported Ultrix on and on MIPS.
MS
It's not a question of it being lost, but rather making sure it doesn't
become lost. My first order of business is for the product that was the
reason for Manalapan's existence -- VAX System V.
The Manalapan, NJ site, after two mergers, is still today known as UNX
because of it initial charter to port AT&T Unix to VAX. This dates back
to the old DEC days where all sites had a 3 character identifier. I guess
someone was a private pilot and modeled it after airport designations.
Anyway, Manalapan was also frequently used as a hub in a lot of uucp
activity -- just look for UNXA in the path.
Enough history for today.
Pat
> On Fri, 01 Oct 2004 06:09:19 -0400
> Pat Villani <patv(a)monmouth.com> wrote:
> > Don't know about a TCP/IP stack, but I'm sorry to tell you that Ultrix
> > is still proprietary and now owned by hp.
> >
> > The source is in danger of being lost unless I'm successful over the
> > next six months. The Manalapan, NJ site where a great deal of Ultrix
> > work was done will be closing soon and employees moved to other
location>
> > and otherwise. I volunteered to take the old tape archives and
transfer>
> > the source code to CD-ROM for preservation. I don't know if there are
> > any other copies in Nashua, NH, where the remainder of the work was done.
> >
> > Pat
> >
> While working at the Biomedical Research Institute (Madrid, Spain) I got a
> quote from DEC for access to Ultrix source code. As I remember it, it wasn't
> that expensive (~1000$ for an academic license) and I mused bout
acquiring>
> it for some time. My naïvete at the time prevented me from ordering it
(t> hat
> and the availability of BSD sources).
>
> But I'd feel pretty sure that at that price many source licenses must have
> been sold. Maybe there are still copies lying around and you can find
> someone to send you a copy back.
>
> Sure, it would be nicer to maintain the whole development log and versions.
>
> j
> --
> These opinions are mine and only mine. Hey man, I saw them first!
>
> José R. Valverde
>
> De nada sirve la Inteligencia Artificial cuando falta la Natural
>
---------------------------------------------
This message was sent using Monmouth Internet MI-Webmail.
http://www.monmouth.com/
Hi, all!!!
Are there any old TCP/IP implementations like these to work on V7 or V6,
freely accessible in source form?
It could be very nice thing to learn from.
And possibly offtopic question - if I want ULTRIX (RISC) source license,
where should I get it from? (mostly interested in newest source) :)
All the best,
S.
Greg Lemis wondered,
> On page 182 of K&R 1st edition there's a reference to an
> implementation of C on the Honeywell 6000, with 9 bit bytes. There's
> no mention of whether it was running UNIX.
That one was a C implementation under GCOS. There
was another 9-bit one for the PDP-10 (not using Unix).
There was a 4x9 bit version of Unix for the Univac 1100
series, which ran Unix as a guest system over the
native EXEC OS.
The most exotic version was the BBN C-machine, which
had 20-bit words, 10-bit bytes.
Dennis
> Subject: Re: [TUHS] 6-bit, 7-bit and 9-bit byte UNIXes
> From: Norman Wilson <norman(a)nose.cs.utoronto.ca>
> To: tuhs(a)tuhs.org
> Date: Thu, 30 Sep 2004 20:47:22 -0400
>
> The very first UNIX ran on the PDP-7, which had 18-bit words.
>
> I happen to have the assembly-language source code to parts
> of that system. Many programs contain error-handling code
> that does something like this:
>
> lac d1
> sys write; 1f; 1
> jmp somewhere
>
> 1: 077012
>
> ...
>
> d1: 1
>
> Evidently the system thought in words in those days
> (the second argument to sys write is presumably a word
> count), but the single word written is a strong clue
> that 9-bit bytes were used, and that a certain concise
> error message that people love to complain about was
> there from the beginning (and why not?).
?
I would say "the PDP7 computer was word-addressable". In this
context, characters seem to have been packed as 9-bit half-words
in a big-endian fashion. No 'bytes'.
Maybe tomorrow I will be near my DEC literature archives, and see
if I can find some clues about PDP7 instructions that might deal
with half-words. If it's anything like the PDP8 of similar vintage,
there aren't any. Late in its life the PDP8 got a BSW "byte swap"
instruction to swap the half-words in the AC register. 6 bits,
of course.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
The very first UNIX ran on the PDP-7, which had 18-bit words.
I happen to have the assembly-language source code to parts
of that system. Many programs contain error-handling code
that does something like this:
lac d1
sys write; 1f; 1
jmp somewhere
1: 077012
...
d1: 1
Evidently the system thought in words in those days
(the second argument to sys write is presumably a word
count), but the single word written is a strong clue
that 9-bit bytes were used, and that a certain concise
error message that people love to complain about was
there from the beginning (and why not?).
Norman Wilson
Toronto ON
