Ah, silly of me. If I used FTP, that could have saved a couple wasted
hours compiling v6on286 :)
--
Maciek (macbiesz(a)optonline.net)
-----Original Message-----
From: Warren Toomey [mailto:wkt@tuhs.org]
Sent: Tuesday, July 08, 2003 8:25 PM
To: Maciek Bieszczad
Subject: Re: [TUHS] v6on286
?! It's still here at ftp://minnie.tuhs.org/UnixArchive/Other/V6on286/
but I'm not sure why Apache hides the README when the same directory
is viewed with http://www.tuhs.org/Archive/Other/V6on286/, I'd better
check that out.
Warren
> From: "Joel Martinez" <president(a)coherent-logic.com>
> To: <tuhs(a)minnie.tuhs.org>
> Subject: Re: [TUHS] OT: Patternless Encryption
> Date: Tue, 8 Jul 2003 11:35:24 -0600
>
> Is it possible to do this with a fixed length key?
>
> > Such a thing exists, it is called a one-time pad. Generate a
> > completely random key as long as the plaintext, and then XOR each
> > successive bit of the key with the corresponding bit of the plaintext.
> > The result is indistinguishable from random noise; only someone with
> > an identical copy of the key can decrypt it (using precisely the same
> > method of course).
For various degrees of security, depending on the length of the key.
Keys are not used directly for encryption, but are used to generate
cryptographically secure pseudo-random sequences.
As a starting point, look at
< http://www.mindspring.com/~schlafly/crypto/faq.htm >
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
> X-From: mirian(a)trantor.cosmic.com (Mirian Crzig Lennox)
> Subject: Re: [TUHS] OT: Patternless Encryption
> Date: Tue, 8 Jul 2003 16:29:59 +0000 (UTC)
>
> On Tue, 08 Jul 2003 15:31:08 GMT, John P. Willis <jwillis(a)coherent-logic.com> wrote:
> >
> >Just curious to hear the opinions of the many wise people here...
> >What is the likelihood of an encryption system in which the resulting data
> >has no pattern,
>
> Such a thing exists, it is called a one-time pad. Generate a
> completely random key as long as the plaintext, and then XOR each
> successive bit of the key with the corresponding bit of the plaintext.
> The result is indistinguishable from random noise; only someone with
> an identical copy of the key can decrypt it (using precisely the same
> method of course).
>
> > and one character of encrypted data may stand for many
> >different characters when decrypted?
>
> Assuming you mean "one character of encrypted data might represent any
> one of several different characters of plaintext" (not "one
> character's worth of encrypted data represents multiple characters
> worth of plaintext), this is indeed the effect of a one-time pad.
> Just don't ever reuse that key; promptly destroy both copies after
> use.
>
> --Mirian
This is hardly the place for a long discussion on such topics, but
one might want to look at the FAQ for the net news group sci.crypt.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
Just curious to hear the opinions of the many wise people here...
What is the likelihood of an encryption system in which the resulting data
has no pattern, and one character of encrypted data may stand for many
different characters when decrypted?
>From: Maciek Bieszczad <macbiesz(a)optonline.net>
>Sent: Tue, 08 Jul 2003 11:07:48 -0400
>To: tuhs(a)minnie.tuhs.org
>Subject: RE: [TUHS] v6on286
>This might help:
>http://nibbly.york.ac.uk/mirrors/TUHS/Other/V6on286/README
>(I'm not sure why it was removed from TUHS)
I did read it. (Hence, my knowledge to use BC3) :)
I was aware of the / bug and didn't even make it that far. I was
hoping (still am) that someone did build it and make it that far.
-uso.
kirei-na pinku-na E-MAIL-saito
___________________________________________________________
Get your own Web-based E-mail Service at http://www.zzn.com
On Tue, Jun 24, 2003 at 04:36:02PM -0400, Latisha Vernon wrote:
> I would like to obtain a CD of the pups archive of UNIX. I have tried to
> access the link provided by the pups website, but was told the site no
> longer existed. If possible, please provide information on how I might
> obtain the CD.
I'll forward this to the mailing list; perhaps someone there might help
you. Can you tell us where you live?
Warren
I already had some ideas, and when I saw something called "v7upgrade", a weird thought came to my head...
I'm wondering if any gurus out there would be able to point me in the general direction, as far as getting V7 stuff running on an 8086,
perhaps a full V7 system. Something like v7upgrade but including a kernel and bootloader. I don't know. Just musing...
My only experience with a "real" UNIX is either SunOS via telnet or PicoBSD. I use RH8 Linux, FreeDOS ODIN 0.31 and Win98SE at
home. It would be interesting to play with V7 on one of my computers. :)
BTW I do have v7upgrade running on my Linux box - sweet! :}
-uso.
kirei-na pinku-na E-MAIL-saito
___________________________________________________________
Get your own Web-based E-mail Service at http://www.zzn.com
To clean up some of the questions:
We (in our group) owned successively two photographic
typesetters:
The original Graphics Systems
C/A/T, which was used to render the camera-
ready copy for several editions of the manual,
also the first edition of K&R as well as
other books. This exposed characters
by flashing a Xenon lamp through a spinning
cylinder with the character images arranged
around the axis; the character was imaged
onto a fiber-optic bundle, which moved
horizontally with respect to the paper. The paper
was moved vertically.
The Linotron 202; it had a CRT on which lines
of characters were drawn, with an unmoving,
line-wide fiber bundle. Rollers moved the paper
vertically.
Both of these were managed by us (including
the hardware connection, via DR11-C; it stood
in for the paper tape that the manufacturers
had intended).
These used chemical processing to develop
the paper. This was messy and (especially
for the C/A/T version) smelly, so we were
glad when the local Comp Center began offering
service on an Autologic APS-5, a machine similar
in design to the 202, but better engineered,
and the comp center managed the chemistry.
This was used for the second edition of K&R,
for example. I think what we sent was troff output
which the CC converted to Postscript.
Later this service was outsourced, then dropped.
In recent years laser printers have become
good enough that decent camera-ready copy
can be generated using them (e.g. for
Kernighan and Pike, The Practice of Programming).
As for the system aspects: K&R 1 (1978) was done on
what would soon be 7th edition Unix, on 11/70;
K&R 2 (1988) using 9th edition on VAX 8550.
Kernighan and Pike's Unix Programming
Evironment (1984) used 8th edition
on VAX 11/750.
About the releases (or pseudo releases) that
Norman mentions: actually 8th edition was
somewhat real, in that a consistent tape
and captured, probably corresponds fairly
well with its manual, and was educationally
licensed for real, though not in large quantity.
9th and 10th were indeed more conceptual in that
we sent stuff to people (e.g. Norman) who asked,
but they weren't collected in complete and
coherent form.
Dennis
Fear not, Gregg; no twists intended or assumed. It could well be
that there was an earlier print run of The UNIX Programming Environment
that got it wrong and claimed to be done with V7 on an 11/750. But
I've never seen it (which is why I specified the exact edition and
printing I was quoting); and if it said that it was an error or a fib.
So far as I know nobody ever did a port of straight V7 to a VAX.
TUPE was written just before I arrived at the Labs; it's possible
that the 11/70 was still around during the writing, though it was
gone before I came. I don't know whether the name V8 was coined
before the 11/70 was retired. Maybe Dennis remembers more.
The original edition of The C Programming Language was certainly
done on an 11/70; it may have been published before the VAX hardware
existed in the field, and certainly before that part of Bell Labs
had one. My beat-up paperback copy (copyright 1978, third printing)
credits Graphic Systems for the typesetter, the 11/70 for the system
hardware, but just says UNIX--no version stated--for the OS.
Norman Wilson
Toronto ON
Look again. The colophon in my copy of The UNIX Programming Environment
(first paperback printing of the first edition) says
This book was typeset in Times Roman and Courier by the
authors, using a Mergenthaler Linotron 202 typesetter driven
by a VAX-11/750 running the 8th Edition of the UNIX operating
system.
I don't have a copy of the latter-day (now contains ISO) C book, but
if I recall correctly when it was written, it was probably typed in
on a VAX 8550 running the 9th edition system. Probably it was the
latter-day 9th, which had crept along quite a bit beyond the hasty
9/e manual. After I made some radical changes to the way device
drivers plugged into the kernel, I changed it to print `9Vr2' when
it booted, partly to distinguish the old system from the newer one
and partly to annoy enough people to reach critical energy to produce
a 10/e manual. The tactic took a while but was ultimately successful.
For those who don't know the historic chain, the systems loosely
called V8, V9, and V10 were never real releases in any sense; they
were just names hung on the continuously-evolving system we ran in
the 1980s in the Computing Science Research Center at Bell Labs.
Brian and Dennis and Rob (and, for six years, I) used that system
for everyday work as well as as a sandbox for systems work; hence
the credit in the books. There were tapes called V8 and V9 issued
to a few specific places under special on-off letter agreement, but
they correspond only approximately to the like-numbered manuals.
Norman Wilson
Toronto ON
(which feels a lot like New Jersey this evening)
