(For reference ... I am writing a detailed history of Berkeley Unix ...)
Does anyone have a copy of and the story about the Univ. of Toronto
license used for their tape distributions around 1977?
In an interview in Linux Magazine, Volume 1, Number 6, in November
1999, Joy said he just took a license from the University of Toronto
and modified it a little bit and started using that for his BSD.
It was a one-page license.
I have a copy of an early one page license (from AUUGN newsletter V01.3,
Feb/Mar 1979) which was used for the Pascal and Ex release, but it says
"(first) Berkeley Software Tape" on it which seems odd to number the
real first distribution. Also the copy of the license I have is for $60,
but the first distribution tapes were $50; these amounts are both
documented in various places for 2BSD and 1BSD respectively. Since maybe
the one page license says "(first)" and "$60", maybe there is a
different earlier license?
I also tried Googling for some of the terminology but didn't find any
hits.
So does anyone have a copy of the license for the Univ. of Toronto tape
distribution from the mid 1970's?
On that note, can anyone tell me about the story of the Toronto Unix
distributions? I understand in late 1978, the Univ. of Toronto Computing
Services group and some other Toronto-area installations were providing
their own Unix distributions for standardization of their commonly used
commands and were forming the "Toronto Distribution Centre" (mentioned
by Gregory Hill, see AUUGN V01.2, Dec-78 / Jan-79). But within a few
years, the UTCS was using BSD.
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'
Hi, all!
Sorry for slightly off-topic question, but do anybody have a copy of
original circa 1969 RS232C standard? I need it to resolve conflict with me
and my customer regarding if RS-232C REQUIRES the use of DE-25M connector
or just
RECOMMENDS it? It seems that there is a lot of interpretations of this
standard, but
no original document anywhere :(
I know it might cost $$$, but I will pay all needed fees.
All the best,
S.
> Hi all,
> I am hoping this list is still alive, since I'd like to find out a bit
more info about this backplane.
> It's part of an 11/23 system (based on CPU) that is made by Netcom. It
had
> standard DEC
> cards in it DLV11, M8021 bootstrap board etc. Apparently the system ran
a
> few years back
> before it was put in storage.
I have a few Netcom boxes at home. I'll try to remember to look
at what models when I go home.
> I aquired it, in the hopes of bringing it
> back to life and getting
> it to successfully display a login: prompt.
That would depend on the OS more than the hardware. :-)
> I have read through the archives, esp. a post from Michael Sokolov back
in
> 98, where he describes
> the different types of QBus'es. Q/Q, Q/CD etc.
> It looks like the backplane that I have (according to some documents
written at SLAC in late 70's)
> is a serpentine or sinusoidal.
> A diagram on the cardcage describes as follows:
> A B C D
> ------------>
> <-----------
> ------------->
> <------------
> There is also a blurb about slot 2/CD being wired differently. Two slots
on the diagram are pre-printed for RL controllers.
There were backplanes like that for the two card RL controller.
> My CPU card is a later rev. D so it can do 22bit addressing. I'd like if
possible to run 22bits, since this would allow
> me at a later time to put in a 11/73 cpu that would run 2.11.
I may be wrong (but I am sure someone here will correct me) but if the
backplane is designed for the two card RL controller I think it will be 18
bit and not capable of 22 bit.
> How would I go about checking if the backplane is wired for 22bits or
not.
> I seem to remeber the standard qbuses had the W1-W4 pins (?)
> that you could wirewrap to change from 18to22, but this backplane has
nothing like that.
I would guess you could look at it and see how many bits are wired thru.
And, if you have a clear view of the wirewrap side you should be able to
see if it has two A-B-C-D slots in the middle. Difference in wirewrap
pattern will be obvious. :-)
> Also, in the present configuration, with an 11/23 and 128Kw, could I run
v6 or v7 (assuming I can get some form of supported disk storage)? At
present
> I only have a floppy controller and a bunch of 8" Shugart 801 drives..
What floppy controller? Dec didn't use the standard Shugart 8" inteface
for RX01/RX02 disks. If it is like the Terak which also used 801's you
are going to need to find drivers for what OS you decide to use. Good
luck with that.
> thanks in advance for any replies.
You might try asking on alt.sys.pdp11 as there are a lot much more
knowlegable people than I active over there.
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill(a)cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
Ian,
Thanks for the response and the pointer to the web page. Looks like I can run 2.9 on the machine - I just have to find myself some RL's 8-)
Did some digging around on QBus, and think i found enough info, that coupled with some contiuity tests should allow me to figure out exactly how the backplane is laid out.
regards
alex
----- Original Message -----
>From: "Ian King" <IanK(a)LivingComputerMuseum.org>
>To: "azd30" <azd30(a)telus.net>, pups(a)minnie.tuhs.org
>Sent: Wednesday, October 23, 2013 11:47:19 AM
>Subject: RE: Netcom HV-1148 QBus Backplane
>You would probably be better served on the ClassicCmp mailing list. This list is primarily about software, specifically Unix on the PDP-11.
>I'd have to dig to answer your question, and there's probably someone on ClassicCmp who can do so off the top of his/her head. (And I already have my hands full: I'm at work looking at bringing up an IFS to talk to a Xerox Alto.)
>Take a look at the PUPS webpage for more information on installing e.g., V6 or V7 on various machines. My recollection is that these versions have requirements in hardware, such as the switch register, that may make them unsuitable for a Qbus machine - but the PUPS page >has a section that can answer definitively. -- Ian
Hi all,
I am hoping this list is still alive, since I'd like to find out a bit more info about this backplane.
It's part of an 11/23 system (based on CPU) that is made by Netcom. It had standard DEC
cards in it DLV11, M8021 bootstrap board etc. Apparently the system ran a few years back
before it was put in storage. I aquired it, in the hopes of bringing it back to life and getting
it to successfully display a login: prompt.
I have read through the archives, esp. a post from Michael Sokolov back in 98, where he describes
the different types of QBus'es. Q/Q, Q/CD etc.
It looks like the backplane that I have (according to some documents written at SLAC in late 70's)
is a serpentine or sinusoidal.
A diagram on the cardcage describes as follows:
A B C D
------------>
<-----------
------------->
<------------
There is also a blurb about slot 2/CD being wired differently. Two slots on the diagram are pre-printed for RL controllers.
My CPU card is a later rev. D so it can do 22bit addressing. I'd like if possible to run 22bits, since this would allow
me at a later time to put in a 11/73 cpu that would run 2.11.
How would I go about checking if the backplane is wired for 22bits or not. I seem to remeber the standard qbuses had the W1-W4 pins (?)
that you could wirewrap to change from 18to22, but this backplane has nothing like that.
Also, in the present configuration, with an 11/23 and 128Kw, could I run v6 or v7 (assuming I can get some form of supported disk storage)? At present
I only have a floppy controller and a bunch of 8" Shugart 801 drives..
thanks in advance for any replies.
--
alex
How to to extract a ".tap" file? What tools?
I found http://man.cat-v.org/unix-1st/1/tap manual but I haven't found
corresponding tool (even in tuhs source code archive).
The file I am trying to extract is
http://bitsavers.trailing-edge.com/bits/BSD/BSD4.1_bootable.tap.gz (12
MB). I can view some of the plain text in it.
I tried historical ar (which I have used for some other 1970's images),
restore, and tar. file(1) says it is a "Maple help database".
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'
PRESS RELEASE - PLEASE COPY AND SHARE!
APPLE 1
FRIDAY, Sept. the 13th
at the "Museo dell'Informatica Funzionante" Computer Museum
Via Carnevale 17, 96010 Palazzolo Acreide (SR) - ITALY
http://museo.freaknet.org/en/presentazione-progetto-apple-1/
The APPLE 1 marked the start of the era of "personal computing",
a computer that people could keep at home on their desks, a
pioneer vision at that time, that opened the way for the future
of human-machine interfaces. Born from the genius of Steve
Wozniak, it transformed Apple into today ‘s success, thanks also
to the entrepreneurial audacity of Steve Jobs.
At that time only about 200 pieces were produced; today only
about 50 of them survived, of which only a dozen are fully
working. The APPLE 1 was an open project since its birth: he
schematics and instructions were already circulating among fans
well before the creation of Apple as a company. From this early
computer, Steve Wozniak created the legendary APPLE 2, a
colossal success that transformed him and Steve Jobs into
billionaires.
We started this adventure almost two years ago at the "Museo
dell'Informatica Funzionante" Computer Museum: to rebuild from
scratch, starting from a completely blank electronic card, a
working APPLE 1, using tools and components dated exactly or
before its creation: 1976.
A year and a half was spent searching for integrated circuits,
connectors, electronic components of various types, bought new
or second-hand, found in various parts of the world, but all
identical to the originals, with the right features and from the
same historical period. The project, managed by a local team,
involved fans and professionals from all the world.
So we present today our creation, made entirely in
Sicily, Palazzolo Acreide, Italy: a specimen of APPLE Computer
1, fully functional, rebuilt with attention to every detail and
using only original components at the best of our possibility!
With this release we intend to invite everyone to the event of
his first start, in person or remotely via our live streaming.
Friday, September 13, 2013:
19:00 - Presentation of the APPLE 1 project and the computer
19.30 - Booting up the rebuilt APPLE 1 Computer, and operational
demo
20:00 - Aperitif
Remote presence:
Via live chat on IRC: https://irc.dyne.org, channel #museo
Live video streaming: http://bambuser.com/channel/musif
On Twitter: follow @FreaknetMuseum
All people in Palazzolo Acreide can also have a guided tour of
our exibithion "Apple, il genio di Steve Wozniak", dedicated to
the genius of Steve Wozniak and his creations, with working
Apple computers and memorabilia from 1978 to 1999.
For more information, press kits and interviews please write to
museo(a)freaknet.org
Spam detection software, running on the system "www.oztivo.net", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview: ÀÎÁõÆäÀÌÁö½Ã¾È1 [...]
Content analysis details: (6.0 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[211.32.24.57 listed in bb.barracudacentral.org]
0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
1.1 URI_HEX URI: URI hostname has long hexadecimal sequence
0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP
0.4 HTML_IMAGE_RATIO_02 BODY: HTML has a low ratio of text to image area
0.0 HTML_MESSAGE BODY: HTML included in message
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
0.7 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
0.0 T_REMOTE_IMAGE Message contains an external image
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
> CB/UNIX was developed to address deficiencies inherent in Research Unix,
> notably the lack of interprocess communication and file locking
CB/UNIX was one of several versions in various divisions of Bell Labs
to implement IPC facilities beyond pipes and signals. Top management
in a division would declare that they wanted to use Unix, but needed
some particular IPC mechanism: semaphores, events, message passing, etc.--
and needed it right away. I always believed that these demands stiffer
as they percolated up through channels to the point that no alternative
mechanism would do. We in research would have preferred to seek a
general solution that would suffice to serve the various demands.
Besides, anything that we produced but didn't use ourselves would
automatically be suspect. We were very wary of featuritis.
Roughly speaking, each demand led to a different local flavor of
Unix, each (I like to think) reflecting the particular variant of
IPC with which one of its system designers worked in graduate
school. Somewhere between the wariness of research Unix, where
an ethos of generality ruled, and Linux, which offers a dozen ways
to do anything, there must lie a happy medium--a medium that I
believe would be much closer to Unix than Linux. That, alas, has
not proved to be the way of open source.
All, I'll be moving house sometime in the next few months, so I thought
I would start scanning in the paper documents that I've got. I've just
completed the scan of the CB/UNIX manuals that Larry Cipriani sent in
a while back. You can find them here:
http://www.tuhs.org/Archive/PDP-11/Distributions/other/CB_Unix/
and here is the blurb I put in there.
Cheers,
Warren
CB/UNIX was a variant of the UNIX operating system internal to Bell
Labs. It was developed at the Columbus, Ohio branch and was little-known
outside the company. CB/UNIX was developed to address deficiencies
inherent in Research Unix, notably the lack of interprocess communication
and file locking, considered essential for a database management
system. Several Bell System operation support system products were
based on CB/UNIX such as Switching Control Center System. The primary
innovations were power-fail restart, line disciplines, terminal types,
and IPC features similar to System V's messages and shared memory.
So far we have a scanned copy of the CB/UNIX manuals which were donated
to TUHS by Larry Cipriani. Copies of the binaries and source code would
be much appreciated. There were two volumes of manuals. The first volume
held cbunix_intro, cbunix_man1 and cbunix_man1L. The second volume held
the remaining sections. The 'L' in the scans indicates local sections of
the manuals, i.e. those elements created and maintaned at Columbus.
In an e-mail from Larry, he asked a retired CB/UNIX developer about the
major features that were added to UNIX by CB/UNIX. Was it primarily messages,
semaphores, named pipes, shared memory? The developer replied:
Other things that immediately come to mind that we added first
in Columbus Unix were power-fail restart (myself and Jim McGuire did the
initial work) and line-disciplines and terminal types (Bill Snider did
the initial work). Hal Person (or Pierson?) also rewrote the original
check disk command into something that was useful by someone other than
researchers. Bill Snider and Hal Pierson were really instrumental in
taking UNIX from research and applying it to SCCS (Switching Control
Center System). I worked with them when I first hired on. When we
first used UNIX on an 11/20 with core memory it was written in assembler
(1974). It quickly went through "B" and we started using the C version
in early 1975 as I recall. We also did some enhancements to the scheduling
algorithms in UNIX to make them more "real-time" capable.
On Jul 24, 2013, at 7:00 PM, tuhs-request(a)minnie.tuhs.org wrote:
> What parts are missing from the archive mentioned by Poul-Henning Kamp?
>
> http://www3.alcatel-lucent.com/bstj/
>
> It has 1922 to 1983. I was assuming that missing issues like 1942 issues 2
> through 4 were not ever published.
I've got Vol 68, No. 8 October 1984, the second 'Unix System' edition of the BLTJ.
Additional articles on all things Unix:
Evolution of the UNIX Time-sharing system
Program Design in the UNIX System Environment
The Blit: A Multiplexed Graphics Terminal
Debugging C programs with the Blit
UNIX Operation System Security
File Security and the UNIX System Crypt Command
The Evolution of C - Past and Future
Data Abstration in C by B. Stroustrup - The first C++ mention that I know of in the Journal
Multiprocessor UNIX Systems
A UNIX System Implementation for System/370
UNIX Operating System Porting Experiences
The evolution of UNIX System Performance
Cheap Dynamic Instruction Counting
Theory and Practice in the Construction of a Working Sort Routine
The Fair Share Scheduler
The Virtual Protocol Machine
A Network of Computers Running the UNIX System
A Stream Input-Output System (D M Richie) - SYS V streams implementation description
David
Ken Thompson has famously said that the only thing he'd do
differently if he were to do Unix afresh would be to spell
"create" with a final e. The BSTJ cameo (or product placement?)
reveals another example: he'd spell Unix as an ordinary proper
name. Once the marketers had glommed onto "UNIX" as a trademark,
we were regularly badgered when when we tried to naturalize
the name. References to "Unix" in internal documents were
scrubbed to "UNIX" for external consumption. I'd like to think
that by exhibiting "Unix" in an image Netravali et al
intentionally cocked a snook at corporate orthodoxy.
Incidentally, the online BSTJ is complete. A new publication,
the AT&T Technical Journal took its place after 1983, with
a new format and quite different content. The replacement
publication was a house organ, not a research journal.
Doug
All, I got this interesting e-mail from Poul-Henning a few days ago.
Warren
----- Forwarded message from Poul-Henning Kamp <phk(a)phk.freebsd.dk> -----
Date: Sat, 20 Jul 2013 13:27:27 +0000
From: Poul-Henning Kamp <phk(a)phk.freebsd.dk>
To: wkt(a)tuhs.org
Subject: A cameo by UNIX in BSTJ
Some months ago I faced a flight from Denmark to NZ and back again,
so I bought a Kobo eBook reader and reformatted the entire BSTJ to fit
the screen.
That gave me about 100k "pages" to read, plenty for my NZ-flights
and a large number of otherwise wasted moments since then. Highly
recommeded.
Recently I came over what I belive is the first mention of UNIX in BSTJ.
We all know about the v57i6, July-August 1978 "UNIX Time-Sharing System"
issue, but it transpires that UNIX made a cameo two years earlier
in an article about compression-schemes for TeleFax:
www3.alcatel-lucent.com/bstj/vol55-1976/articles/bstj55-10-1539.pdf
Enjoy,
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk(a)FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
----- End forwarded message -----
My apologies if some find this as spam, but I suspect this group might
also find this a worth while read.
Full discloser, I have known John since 1983 or 1984 (I do not remember
when we were co-worked at the firm he talks about in
the article [Masscomp]. I have also read of number of his books and liked
them. In my role as President of USENIX, I allowed John to hawk his books
at some of our conferences, but other than buying his books, I have
never given him $s.
http://my-thoughts-exactly.wetmachine.com/the-meme-hustler-hustler-evgeny-m…
Clem
Note: I predated John at Masscomp (and I think he left for Sun before I
left for Stellar).
Many of you know that MSCP
was an early 1980s a start up with a lot of ex-VMS/VAX guys (that
predated Sun and actually did $20M in business the year Sun did it's first
$1M).. Tim, Janet and I shared a card table as our first desk. I think
John and Steve did get hired until we expanded to the 2 bldg in Littleton
and kicked SW out. Everything in the piece WRT to Masscomp I will valid
as true, and like John; when I have run into Tim in the past few years I'm
not sure he recognized me either [although unlike John, I do still exchange
christmas cards with Steve Talbot and just two weeks ago got an email from
Tim about something else].
I completely agree with John's point about about Eric Raymond too BTW. And
John makes a side bar, that "open source" being co-opted from the 60s.
He's stumbled on that right. I have always said the "father" of Open
Source was the late Prof Donald O. Peterson (aka dop) from what he did in
the late 1960s. But that's a story for another time.
I fear a sad part of this slide show is that many of us remember and were
part of it all. Some of us programmed these machines (I admit that I
still have some of these pieces in my basement). I was disappointed they
did not show a "stinger tap." The picture of the Alto shows the first mouse
– the Hawley Labs mechanical mouse (which I miss for its feel). Check out
the picture of the first Cisco router using Intel Multibus (with a Motorola
68k in it) looking so awkward.
http://www.eweek.com/networking/slideshows/ethernet-marks-40-years-linking-…
Larry McVoy said:
On Apr 28, 2013, at 7:00 PM, tuhs-request(a)minnie.tuhs.org wrote:
> We build source management systems and we still drop into assembler for
> some stuff. For example, we want to give ourselves a stack traceback
> when something dies. Another example is inner loops that are performance
> critical, we stare at the assembler.
I don't mind staring at the assembly, I just don't want to hand crank it any longer. :-/
I'll spend quite some time fussing with the compiler and optimization flags to get loops to run at maximum speed before I'll take the assembly in hand to 'make it right.'
For stack traces, I've found the GNU compiler support for stack tracing quite handy and for my company it works quite well.
On the discussion of x86 assembly, I have to agree that it is horrific. I'll take ARM (and I have done context switchers and trap handers in ARM) any time.
David Barto
/my name in your iPhone, it is more likely than you think.
About two queries on the topic.
Yes, L. L. Cherry is Lorinda Lillian Cherry.
Rudd Canaday was in on building the foundation, but not the
ground floor. When the Thompson/Ritchie/Canaday (and independently
Strachey/Stoy) file system came to be built, Rudd had completed
his visiting assignment in Computing Science Research. When he
did get a login, he was rhc, but his UID was not among the
single-digit set.
Doug McIlroy
rudd canaday?
> From: tuhs-request(a)minnie.tuhs.org
> Subject: TUHS Digest, Vol 102, Issue 1
> Date: March 31, 2013 9:00:01 PM EDT
> To: tuhs(a)minnie.tuhs.org
> Reply-To: tuhs(a)minnie.tuhs.org
>
> Send TUHS mailing list submissions to
> tuhs(a)minnie.tuhs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://minnie.tuhs.org/mailman/listinfo/tuhs
> or, via email, send a message with subject or body 'help' to
> tuhs-request(a)minnie.tuhs.org
>
> You can reach the person managing the list at
> tuhs-owner(a)minnie.tuhs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of TUHS digest..."
>
>
> Today's Topics:
>
> 1. Login names of early Unix contributors (Doug McIlroy)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 31 Mar 2013 10:44:11 -0400
> From: Doug McIlroy <doug(a)cs.dartmouth.edu>
> To: tuhs(a)minnie.tuhs.org
> Subject: [TUHS] Login names of early Unix contributors
> Message-ID: <201303311444.r2VEiBjR027109(a)stowe.cs.dartmouth.edu>
> Content-Type: text/plain; charset=us-ascii
>
>> Does anyone have a record or pointer regarding the login names of the
>> early Unix contributors?
> [...]
>> In particular I'm interested in the login names of following people:
>> S. R. Bourne
>> D. Haight
>> S. C. Johnson
>> J. F. Maranzano
>> L. E. McMahon
>> S. I. Feldman
>> J. F. Ossanna
>> M. E. Lesk
>> R. H. Morris
>> D. A. Nowitz
> [...]
>
> Your correspondents have done a good job of reconstructing the
> old list. Alas, I can't remember the only missing entry, Dick
> Haight's login. The above list, however, wants one small
> correction. Robert Morris did not have a middle name, the
> "h" was a figment for filling in forms that wanted a middle
> initial.
> Another important name is
> L. L. Cherry llc
>
>
> ------------------------------
>
> _______________________________________________
> TUHS mailing list
> TUHS(a)minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
> End of TUHS Digest, Vol 102, Issue 1
> ************************************
> Does anyone have a record or pointer regarding the login names of the
> early Unix contributors?
[...]
> In particular I'm interested in the login names of following people:
> S. R. Bourne
> D. Haight
> S. C. Johnson
> J. F. Maranzano
> L. E. McMahon
> S. I. Feldman
> J. F. Ossanna
> M. E. Lesk
> R. H. Morris
> D. A. Nowitz
[...]
Your correspondents have done a good job of reconstructing the
old list. Alas, I can't remember the only missing entry, Dick
Haight's login. The above list, however, wants one small
correction. Robert Morris did not have a middle name, the
"h" was a figment for filling in forms that wanted a middle
initial.
Another important name is
L. L. Cherry llc
I was trying to generate PDFs of some PWB
manual pages but they use V6 macros.
I have found tmac.an6 which generates somthing
readable but stamps each page with:
THIS MANUAL ENTRY NEEDS TO BE CONVERTED - SEE mancvt(1) and man(7)
Anyone know of mancvt, I cannot find it.
-Steve
Ok,
another trivia question.
where did xargs come from? I started with Edition 7 (Perkin Elmer
V7 + bits of BSD 2.1) and I am pretty sure it wasn't there.
I have a feeling it was printed in a book as shell script, somthing
like Bourne's book, or Kernighan and Pike but I'am not sure.
Anyone remember?
-Steve
Thanks for this alert
Sheila
-----Original Message-----
From: tuhs-bounces(a)minnie.tuhs.org [mailto:tuhs-bounces@minnie.tuhs.org] On Behalf Of tuhs-request(a)minnie.tuhs.org
Sent: Wednesday, February 20, 2013 8:00 PM
To: tuhs(a)minnie.tuhs.org
Subject: TUHS Digest, Vol 100, Issue 12
Send TUHS mailing list submissions to
tuhs(a)minnie.tuhs.org
To subscribe or unsubscribe via the World Wide Web, visit
https://minnie.tuhs.org/mailman/listinfo/tuhs
or, via email, send a message with subject or body 'help' to
tuhs-request(a)minnie.tuhs.org
You can reach the person managing the list at
tuhs-owner(a)minnie.tuhs.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of TUHS digest..."
Today's Topics:
1. opensolaris.org will be close soon (Cyrille Lefevre)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Feb 2013 05:15:37 +0100
From: Cyrille Lefevre <cyrille.lefevre-lists(a)laposte.net>
To: tuhs(a)tuhs.org
Subject: [TUHS] opensolaris.org will be close soon
Message-ID: <51244DE9.2060901(a)laposte.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Hi,
FYI, as seen on opensolaris.org :
ATTENTION: This website and all services within the opensolaris.org domain will be unavailable after March 24, 2013.
at least, http://hub.opensolaris.org/ and http://dlc.sun.com/osol/ will be available at :
http://web.archive.org/web/*/http://hub.opensolaris.org/http://web.archive.org/web/*/http://dlc.sun.com/osol/
but not http://src.opensolaris.org/source/ due to robot.txt
any other subdomain to check ?
Regards,
Cyrille Lefevre
--
mailto:Cyrille.Lefevre-lists@laposte.net
------------------------------
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
End of TUHS Digest, Vol 100, Issue 12
*************************************
Hi All.
Mike Lesk sent me the paper and gave me permission to send it out.
See attached.
Warren, please find a spot for this in the archives.
Thanks!
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381
Nof Ayalon
D.N. Shimshon 9978500 ISRAEL
Does anyone have a record or pointer regarding the login names of the
early Unix contributors? A few (aho, dmr, bwk, doug) are listed in
http://www.cs.bell-labs.com/who/, but many others seem to be missing.
In particular I'm interested in the login names of following people:
S. R. Bourne
D. Haight
S. C. Johnson
J. F. Maranzano
L. E. McMahon
S. I. Feldman
J. F. Ossanna
M. E. Lesk
R. H. Morris
D. A. Nowitz
I guess the /etc/passwd file from a Bell Labs system of the mid 1970s
would be ideal, but even partial recollections would help me.
Adding the TUHS people...
In article <3b6a67956d8b807d3d3319a395892b67(a)9srv.net> you write:
>Does anyone on the list have a copy of or pointer to
>"Electronic Mail Without Aliases", by Elliott and Lesk?
>It's referenced in the 8th Edition Unix manual, but
>I've never read it (and only have vol1 of the manual).
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381
Nof Ayalon
D.N. Shimshon 9978500 ISRAEL
While the subject of historical stuff has been brought up, anyone thought about going another round with Attachmate to see if they'd extend the Ancient UNIX License to include v10, v9, and v8? Attachmate is the current owner these days, aren't they?
I'm sure they, Novell, AT&T, and Lucent all don't care. But someone's still got to sign the line. I'm really hoping to see v10x86, like v7x86 someday!!
I've got a copy of v8 I'd love to make available some day, and I know there are at least one or two copies of v10 still in existence. last I heard, there was no v9.
Anyone here know anybody at Attachmate?
Many thanks!
-Ben
Armando Stettner:
> decvax!aps
Larry McVoy:
...!uwvax!lm
=====
Well, if we're going to play the one-up game:
research!norman
though for a few years before that it was
research!cithep!norman
Norman Wilson
(now) Toronto ON
Herr Doctor Wkt:
Does anybody have a PDF of the 1974 Unix CACM paper, I seem to have
misplaced my copy.
=======
It appears to be generally available via the ACM Digital Library,
of all places. (No, I'm not so smart: Google pointed me there.)
http://dl.acm.org/citation.cfm?id=361061
It appears to be the genuine 1974 version, though my paper copy
of that issue of CACM is buried behind too many boxes right now
for me to dig it out and check. Disk storage for `The PDP-11/45
on which our UNIX installation is implemented' is as Warren
describes for the 6th Edition update: 1MB fixed-head disk,
four 2.5MB removable-cartridge drives, and a single 40MB
removable-pack drive.
Norman Wilson
Toronto ON
I have heard the story a few times about sbin split is due to disk
space, such as told at
http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sb…http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
But I don't see any mention of it in 32V and not in BSD until around
Net2 (like in 1991 src.README said ``... there has been a major
reorganization of the file system. (You may have seen similar
reorganizations on systems shipped by Sun Microsytems [sic] and Digital
Equipment Corporation, among others.) ... /sbin same as /bin, but
binaries for the root user''. The slides from Feb. 1988 for a BSD BOF at
USENIX mentioned this sbin reorganization.
Looking at "Unix Text Processing" (1987) and "Life with Unix" (1989) I
didn't see any use of sbin/. (I didn't look at my other old books.)
>From searching old 1980 usenet archives I only saw a few mentions (like
/usr/brl/sbin/...).
When did some (non-BSD) systems ship and document /sbin, /usr/sbin?
Is the common story (liked linked above) the right story?
Jeremy C. Reed
echo uggc://errqzrqvn.arg/obbxf/ofq-uvfgbel/ | \
tr "noqruvxzabcefgl" "abdehikmnoprsty"
Ronald Natalie <ron(a)ronnatalie.com> wrote:
> I suspect strcpy arrived with the "portable I/O library", an abomination
> that eventually evolved into the stdio library and to this day is still
> stinking up the standard C language.
What's so bad about stdio? That's a genuine question - I've never had
a reason to dislike stdio...
SF
Museo dell'Informatica Funzionante
Computer Museum in Palazzolo Acreide, Italy
http://museum.freaknet.org
Just a few lines to announce that some of our historical
computers are back online 24/7 for free use!
We have 2 VAX/VMS systems and an emulated PDP-11/34 running
RT-11 (that's the exact copy of our physical RL01 boot disk)
Have a look here, and enjoy! :)
http://museo.freaknet.org/en/computer-storici-vaxvms-nuovamente-online/
Hi. I have two QIC 6250 tape cartridges that have been in (I hope) dry
boxes for over 15 years. I suspect they're still usable but have no
equipment with which to test them or try to read them.
It'd be nice to get a CD back with copies of what's on them if that's
possible, but that'd be icing on the cake.
Drop me a note and we'll see if we can figure something out for mailing
them.
Thanks,
Arnold
On another list I am on, a discussion about the history and purpose of
strncpy has arisen. The only reference I have found to it is <
http://lwn.net/Articles/507432/>:
The original reason for strncpy() was when directory names were limited to
14 chars. The other two bytes contained the inode number. For that
particular case, strncpy() worked quite well.
Is that really the reason it came into being?
Just a bit curious,
--
Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> (847) 691-1404
Hi all,
Arnold Robbins has donated a couple of OpenLook CDs to the Unix
Archive. I've put them into Applications/OpenLook.
Here is his note:
I have a CD from ian(a)darwinsys.com dated 9/2005 with
OpenLook-XView-1.0e on it, and what looks like another one with
the same date with version 1.2. I'm still extracting the first
one onto disk; it's in the 550+ Megabyte range. Files are dated 1995.
Right now it's only on minnie until the mirrors pick it up:
http://minnie.tuhs.org/Archive/Applications/OpenLook/
Cheers & thanks Arnold & Ian,
Warren
Hi guys, new SIMH (and Research Unix) user here coming from the future
(Linux), haha. Well, as the mail subject says, I have a problem.
After creating a bootable disk from a virgin Unix v7 distribution tape by
following this guide, http://homepages.thm.de/~hg53/pdp11-unix/, and after
umounting the usr file system and halting the machine, SIMH returns:
HALT instruction, PC: 000002 (HALT)
after running the command:
pdp11 run.conf
and I cannot boot my 87,9 MB 'system.hp' disk.
I thought the problem was on the final line of 'run.conf':
run 2002
But when I use SIMH without .conf files and by manually typing the
following commands:
set cpu 11/45
set cpu 256k
set rp0 rp04
attach rp0 system.hp
boot rp0
I see the same HALT message too.
I'm currently unning SIMH from Debian/Ubuntu package 3.8.1-5build1. Should
I update to a newest one? Or did I make a mistake when creating my bootable
disk?
Hi,
Don't remember if this was already posted to this list, so, just in case
it wasn't...
The UNIX System: Making Computers More Productive
http://techchannel.att.com/play-video.cfm/2012/2/22/AT&T-Archives-The-UNIX-…
In the late 1960s, Bell Laboratories computer scientists Dennis Ritchie
and Ken Thompson started work on a project that was inspired by an
operating system called Multics, a joint project of MIT, GE, and Bell
Labs. The host and narrator of this film, Victor Vyssotsky, also had
worked on the Multics project. Ritchie and Thompson, recognizing some of
the problems with the Multics OS, set out to create a more useful,
flexible, and portable system for programmers to work with.
What's fascinating about the growth of UNIX is the long amount of time
that it was given to develop, almost organically, and based on the needs
of the users and programmers. The first installation of the program was
done as late as 1972 (on a NY Telephone branch computer). It was in
conjunction with the refinement of the C programming language,
principally designed by Dennis Ritchie.
Because the Bell System had limitations placed by the government that
prevented them from selling software, UNIX was made available under
license to universities and the government. This helped further its
development, as well as making it a more "open" system.
This film "The UNIX System: Making Computers More Productive", is one of
two that Bell Labs made in 1982 about UNIX's significance, impact and
usability. Even 10 years after its first installation, it's still an
introduction to the system. The other film, "The UNIX System: Making
Computers Easier to Use", is roughly the same, only a little shorter.
The former film was geared towards software developers and computer
science students, the latter towards programmers specifically.
The film contains interviews with primary developers Ritchie, Thompson,
Brian Kernighan, and many others.
While widespread use of UNIX has waned, most modern operating systems
have at least a conceptual foundation in UNIX.
Release date: 02/22/2012
http://wpc.5C42.att-acdn.net/005C42/techchannel/10959/videos/10959_AA11180_…
Regards,
Cyrille Lefevre
--
mailto:Cyrille.Lefevre-lists@laposte.net
All, I've had to move my machine minnie.tuhs.org out from where I work
at Bond University. The new IP address is 65.49.60.197. I've updated the
A and MX DNS records but they are still propagating. If you have any
future troubles sending e-mail to tuhs(a)tuhs.org, contact me at wkt(a)tuhs.org.
And if that fails, try my Gmail account "warren.toomey" :)
Cheers,
Warren
Hi All.
Thanks for the responses! I have someone who replied first, so he gets
the manuals. It's nice to know there are people who can give these things
good homes. :-)
Arnold
Hello All.
I'm trying to clean up my basement. I have the following:
USENIX 4.2 BSD manuals - 4 volumes
USENIX 4.3 BSD manuals - 6 volumes
USENIX / O'Reilly 4.4 BSD manuals - 5 volumes + CD-ROM companion
They are all in excellent shape - close to new actually.
First come first serve, if you're willing to pay postage from Israel.
I also have a copy of "Concurrent Euclid, Tunis, and the Unix system" which
I suspect is a fairly historic book that I'd like to send to a good home.
Please reply directly to me without bothering the list.
Thanks!
Arnold
As I told Phil off-line, I wold ask around the DEC Unix alumni and see what
I could find out.
On Mon, Oct 22, 2012 at 5:02 PM, Richard Schedler wrote:
> Before leaving HP Labs, I moved the Gatekeeper Archives over to
> apotheca.hpl.hp.com . I just checked and was pleasantly surprised to see
> that they're still around.
>
> --Richard
>
HP Labs FTP Server
This is the FTP server for Hewlett-Packard Laboratories. It replaces the
following servers:
- ftp.hpl.hp.com
- gatekeeper.hpl.hp.com
- gatekeeper.research.compaq.com
- gatekeeper.dec.com
This system is not for file storage nor any other use without express
authorization from the Hewlett-Packard Company.
All logins and file transfers on this system are logged and monitored.
Please use the feedback link below to report problems or ask questions.
*Repository Services*
- *Access the repository via FTP* <ftp://apotheca.hpl.hp.com/>
- *Access the repository via HTTP* <http://apotheca.hpl.hp.com/ftp/>
*Other Information*
- *What happened to
gatekeeper.dec.com?*<http://apotheca.hpl.hp.com/what-happened-to-gatekeeper.html>
Hello All.
This is a bit off topic, but I figure people on this list may have the
experience and also the knowledge I need...
I have an HP Laserjet 6MP printer; it is 16 years old but still going
strong. It has a level 2 Adobe Postscript interpreter and a whopping 3
Megs of memory.
It is attached to an ethernet-to-parallel port thingy that lets me spool
to it over the network; I am printing from Linux systems running CUPS. Here's
the problem:
No matter how I have the printer settings set for the paper source, when I
use tiff2ps to convert a TIFF file into PostScript:
1. If I use the 'make level 2 postcript' option to tiff2ps, I get a much
smaller file, but the printer decides it wants paper to come from the
manual feed paper tray. The problem is that this paper tray usually
doesn't have paper in it, so I have to go to the basement and put paper in.
2. OTOH, if I use the default which makes level 1 postscript, I get a file
that is 10 times bigger, but the printer then decides it will take paper
from the tray, like it's supposed to.
I keep the postscript file around for easy reprinting. I don't care for
big files, and they take longer to send, too.
Googling has not helped.
If anyone knows what kind of magic string to add to the generated level 2
postscript to make it choose a paper source, or has any other ideas, I
would love to hear from you.
Thanks!
Arnold Robbins
Hi,
Does anyone have a mirror of the old ftp site gatekeeper.dec.com? I have
only a small fragment of it, but I'd very much like a full copy. I believe
I have a full copy of ftp.uu.net from October 2003, if anyone's interested.
Also, I apologize if this question is considered inappropriate here, but
did anyone manage to snag a full copy of the titor-special torrent?
Thanks,
Phil Garcia
I had a look at OSNews.com and found a story about a nifty little
terminal and its OS called Blit.
http://www.osnews.com/story/26315/
Blit_a_multitasking_windowed_UNIX_GUI_from_1982
I suspect getting hold of it would be like getting blood from a
stone, much like getting the Research Unix source trees ... but still
it would be interesting to look at if at all possible.
Wesley Parish
After a 10-year quest, the Computer History Museum has convinced IBM to make the source code for APL\360 available to the public. The license terms are for personal use only, no copying allowed.
The code itself is quite entertaining to read in some areas :-) About 37K lines of 360 macro assembler, which includes most of an interactive time-shared terminal OS environment upon which to run the APL interpreter.
http://www.computerhistory.org/atchm/the-apl-programming-language-source-co… has lots of background material, and the link to the download page. Note that the links in the bibliography section on that page are broken – the all contain a spurious '.' at the end of the URL anchors.
--lyndon
All, as I have to move office at the end of the year, I have a few old
DEC books which I'd like to re-home to good families. I am happy to give
them away, but I would like to be reimbursed for postage and packing.
I've put up the details of the books at this link:
http://minnie.tuhs.org/DECBooks/
Feel free to pass this on to anybody else who might be interested.
Cheers,
Warren
So I was digging around some time back, and noticed these lines in the
*BSD "Computer" calendar file:
06/30 First advanced degree on computer related topic: to H. Karamanian,
Temple Univ., Phila, 1948, for symbolic differentiation on the ENIAC
Since I'm attending Temple, this caught my attention. However, a
search for "H. Karamanian" didn't turn up anything, so I gave up.
Recently, I tried again and found this:
http://diamond.temple.edu/record=b1850797
In short, the name in calendar.computer is misspelled, and the date is
wrong too! The correct year is 1953, at least according to that
record. (I haven't looked at the actual thesis yet.)
Whether this is indeed the "First advanced degree on computer related
topic" is something I'm not sure about — a cursory search didn't turn
up any others that predate this one, but I didn't search very far.
--David R
i happened across this cute document in my archives...
----
*na Bblisa-Announce-Owner(a)cs.umb.edu Tue Dec 28 14:10:50 1993
*to bblisa-announce(a)cs.umb.edu
*su Some notes from December 1, 1993 meeting
*fr "John P. Rouillard" <rouilj(a)terminus.cs.umb.edu>
*se Bblisa-Announce-Owner(a)cs.umb.edu
*da Tue, 28 Dec 1993 12:42:01 -0500
*mi <199312281742.AA17997(a)cs.umb.edu>
*re from cs.umb.edu (daemon(a)cs.umb.edu [158.121.104.2])
by argali.opal.com (8.6.4/jr2.9) with SMTP
id OAA27752; Tue, 28 Dec 1993 14:10:43 -0500
*re by cs.umb.edu id AA18007
(5.65c/IDA-1.4.4 for bblisa-announce-outgoing); Tue, 28 Dec 1993
12:42:08 -0500
*re from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA17997
(5.65c/IDA-1.4.4 for <bblisa-announce(a)cs.umb.edu>); Tue, 28 Dec 1993
12:42:01 -0500
*ex Precedence: bulk
*tx
Here are the notes from the December 1, 1993 meeting. Names have been
deleted to protect the innocent. The topic was:
UNIX Horror Stories (Actually Computer Horror Stories)
and away we go.
Story 1:
A new user I knew was trying to clean out some old accounts on a system
he was given. As root, he changed directories to one of the old user
directories, and then did 'rm -r *' but noticed it left a directory
called .X11 behind. To get rid of it, and to be sure it wouldn't fail,
he did 'rm -rf .*'. Sad to say he didn't realize that '.*' could and
would expand into '..', and it would continue to do so recursively.
I thought this was better than the 'garden variety' 'rm -rf' scenario.
The guy though, worst case, he'd blow away the old user accounts,
but got the entire disk instead!
Needless to say, it was time for the install disketts (yes, diskettes,
about 30 of them...).
Story 2:
SunOS 4.0 NFS server configured with IP address 192.9.200.0
by suninstall (default - a suninstall bug) and rebooted after
OS installation... (nice DECnet meltdown)
Story 3:
/etc/reboot - then noticing you were in the wrong window...
Story 4:
Coming in at 7:00AM Saturday to upgrade to Ultrix 2.2, then
5 hours later having the other guy type in rm -rf - then
realising he forgot to cd out of /etc...
Story 5:
Having a user request some files to be restored - but forgetting
when they existed except that it was "sometime around a
year or so ago"...
Story 6:
Would you all be interested in the time a workman disassembled the cubicle
containing my NIS master and dropped a 1.3 gig disk several feet to the
floor ...? (Prior to telling me he was taking it apart of course ...)
Story 7:
talking to an end-user who just called in over the phone
my root filesystem filled up, so I looked around; I found & removed vmunix
and boot, and that seems to have fixed things, so I typed fastboot.
Story 8:
Back in the days when UNIX V6 was new, we installed it on a PDP 11/44
in the CS lab. It ran fine. We allowed students on it. It ran fine.
People started using it for real work, albeit tentatively. It ran fine.
It was a bit slow if several people were on -- what do you expect for
a PDP11/44 -- but, it ran fine.
Then occasioanlly, we started noticing that troff would go wrong and
it would mis-format some portions of a document. Funnily enough,
when you re-ran the job, it ran fine. We opened up the CAT. Have
you ever been inside a CAT? These were serious phototypesetters.
And, we could find nothing wrong with ours. After a few days of
frustratedly looking for problems with the CAT, and the wiring, and
the troff config, it seemed to start working OK again, so we closed
it all up, and forgot about the problem.
About 12 weeks later, students working on simulation class assignments
started complaining that if they came in and ran their programs during
the day, the programs would give the wrong results. But, if they ran
the SAME programs in the evening, they'd be fine. Thinking to ourselves
that students are a real pain in the ass, we took a look. Thing is,
they were right. The programs DID indeed give different results
depending on when you ran them. Mostly, they were OK, but occasional
daytime runs were flaky. Problem with the core (yes, we had core
storage on that system)? We swapped core boards. No change. We
swapped CPU boards. No change. We practically swapped every board
and the bus and built a new machine. No change. Of course, the
number of failures were few -- the programs ran OK MOST of the time,
so pinning this down was a slow process. Eventually, the students
all got their assignments done, and they went on to other exercises,
and we didn't have any more problems, so we got on with our lives,
and forgot about it.
Another 12 weeks go by. We were all happy. Life was good. The 11/44
is still running fine. Until... Aaargh! Someone using the dc calculator
reported errors in the results... sometimes! And, at the same time,
someone using troff reported mis-set pages. We took the machine down
to single user. We ran all the programs. We turned on all sorts of
debugging and tracing. Everything was fine. Nothing went wrong.
We pulled our hair out! We went back multi-user. Everything was
fine. We'd run dc. It was fine. We'd troff the document. It was
fine. We'd go to the bar. The users would come and find us and
show us printouts of their dc and troffs that had gone wrong!!
Aaaargh!
Well, this was one of those problems. Eventually, we made an observation.
Dc works fine. Troff works fine. The simulation assignment program
works fine. But... run any of them at the same time...!!!! That
was it! It turned out, that these three programs used the floating
point hardware. They were the ONLY programs that used the floating
point hardware. Our machine had floating point hardware; the one
at Bell Labs did not have. UNIX V6 was not saving the floating
point registers on context switching. If you were the only floating
point program on the system, this did not matter -- you context
switched out, and when you switched back in, your registers were
all there as you left them. But, if there was another floating
point program around, your registers were corrupted!
Over 8 months to diagnose the problem. Just 2 minutes to fix it!
Story 9:
I received umpty-three million requests at LISA, from people
that wanted me to e-mail them the text of NET's infamous
"Eng_Adm Get List" T-shirt. So here it is, even if you
didn't want it. :-)
(Eng_Adm is our systems administration mail alias)
FRONT
* I didn't touch a thing. * Why can`t you give me the root password? * I
want
more disk space, now! * It was working fine a minute ago. * I typed rm -rf,
but I didn't really mean to. * How come SPARC binaries won't work on my
3/50?
* I just turned it off and on a couple of times. * What's an alias? * It
must
be a hardware problem. * This will only take you a minute. * Can you restore
/tmp/junk from February of 87? * X Windows isn't working on my VT100! * I
didn't realize the type of coax made any difference. * How do I post an
article to alt.sex.bondage? * I just plugged my RS-232 port into my phone
jack. * Is the unix broken? * My bin directory is missing! * Someone
spilled
coffee on my keyboard. * I need to be the owner of all of the files in
/usr/kvm. * How can I send mail to my friend on BITNET? * What makes you
think
it is my software? * My Mac is much easier to use. * Why is her disk quota
bigger than mine? * What jumpers? * I can't login to my ethernet. * Don't
you
know where I put my source code? * I need to borrow your CD-ROM for 2
months. *
Where can I find all of those GIF files? * Honest, it just stopped working.
*
But I like the old OS a lot better. * Can you read this TK50 VMS tape onto
my
Sun? * I can do it... I used to be a Systems Administrator. * Can`t this be
done after I go home? * It says, "Run fsck manually". * I need you to
reboot
my floppy drive. * What does RTFM mean? * How hard can it be to do a simple
upgrade? * My system just crashed. * Now how did that file get in there? *
But
the vendor says this should be, "Plug and play". * This is going to cost us
how much!? * A System Administrator doesn't do hardware. * My machine needs
more memory. * Is my monitor suppose to smoke? * Just stay late. * It was
fine,
until I moved the disk drive over to there. * I can guarantee you that my
program is flawless. * Oops... *
-----------------------------------------------------------------------------
BACK
Eng_Adm "Get List"
[X] A Clue
[X] A Life
[X] Lost
Remember... just send mail.
Copyright ) 1992 Network Equipment Technologies, Inc. All rights reserved.
Story 10:
A Dec F/S rep in to service a line printer managed to trip on the power
cord to a DEC 11/750. An operator trying to be helpful immediately (no
intermediate steps) plugged the power back in, faulting the system.
Upon the F/S rep's request to hit the reset, a second operator
hit the reset on the wrong 11/750. All mail, printing and a
substantial number of other services at a small but busy academic
site to came to an abrupt mid-day halt.
Story 11:
A system administrator logged in to a fileserver from home after two
days of vacation to find her environment not working as expected.
Some poking around revealed that the filesystem supporting /usr/local
had been unmounted after disk problems. A call to the night
operator to see if more info was available yielded the message "the
system was down" waiting for F/S. The systems administrator's
manager was shocked to find her in early next morning using the "dead"
system's console to distribute alternate /usr/local mount
configurations to the 15 desktops that received it from the server.
Back tracking of the problem revealed that the system was probably
pronounced dead after help desk/operations staff could not login using
a non-standard shell found in /usr/local. No evidence could be found
that a software support person had been consulted or that anyone other than
users had actually looked at the physical system. A user was
determined as being the person responsible for removing /usr/local from
mount configurations and bringing the system up multiuser.
Story 12
After testing a new nfs patch on a few test cases, an administrator
began batch kernel installation and system reboots on 5 Sun Servers,
~50 clients, ~15 diskful desktops. One server on which the others
had the several dependencies failed to reboot. This server was also the
only one with a spare client slot. It had the only tape drive that
could support the SunOS install tapes for it's architecture that was
immediately accessible to the administrator. The system administrator
determined the server could not be fixed in single user. It was not
going to be possible to borrow a tape drive off hours. The
administrator proceded to juggle filespace on another server to setup a
client slot for booting over the net.
About this time, numerous nfs woes surfaced. The administrator
proceded to address references to the down server. After these
had been addressed (including a few reboots), the administrator
realized that the test cases hadn't determined the nfs patch would
cause more problems than it solved. Life was going to be miserable
until it was removed. The distribution mechanisms then in use were
partially dependent on nfs, so the patch had to be backed out manually
on systems that had come up. [Fortunately, the practice was to halt
diskless clients and distribute nfs/lockd patches to /export/root on
the servers after the servers came up using the new patch. None of
the diskless clients had yet been rebooted.]
Once the patches were backed out and the dead server was finally
booted over the net, examination of the root filesystems revealed that
a *well intentioned* person had, without informing the administrator,
very recently resolved a root overflow problem by making the
contents of /sbin links to /usr.
-- John
John Rouillard
Special Projects Volunteer University of Massachusetts at Boston
rouilj(a)cs.umb.edu (preferred) Boston, MA, (617) 287-6480
===============================================================================
My employers don't acknowledge my existence much less my opinions.
The recent FOSS release of CDE has got me thinking of other Unix GUIs
from the "golden age" of workstation Unix. Obviously, stuff like
SunView and OpenWindows from Sun and 4DWM/Indigo Desktop from SGI are
pretty well known, but I've always wondered what else was out there.So
far, I've come across Looking Glass, DECWindows and HP VUE. Is there
anything else of any importance/interest out there?
Mike
Though Apollos were much more Unix-like than actual Unix, the DM
environment (display manager?) on Apollo Aegis, Domain/IX, and
Domain/OS workstations was pretty interesting, most notably for the
sophisticated interaction between the command-line and GUI. The DM was a
lot like the Moxie carbonated beverage - you either liked it or you
really wanted to spit it out. Apollo systems also ran various versions
of the X Window system, but the unique stuff was in the DM.
Site such as Toastytech's GUI Timeline
(http://toastytech.com/guis/guitimeline.html) and Typewritten Software's
Retrotechnology Media page (http://www.typewritten.org/Media/) have many
screen shots of old GUIs and apps, many on Unix or Unix-like systems.
Bill
Werner Losh:
However, the complicating factor here is, I think, that SYS V uses a
lot of code from the later editions of Unix, so relicensing the newer
research versions might cut into the license streams from them in
some way. At least that was reported at the time of the only through
7th edition licensing.
=======
I'm not sure who would have reported that `System V uses a lot of
code from [post-7th] editions of UNIX.' I may be misled by having
had my hands and eyes mainly on the kernel and the most-basic commands
like the shell, but offhand I can't think of any System V code at all
that was adopted directly from the Research systems in the 8th, 9th,
or 10th Edition eras.
There were certainly ideas that were picked up, mulled over, and
re-implemented in changed form by the System V people, sometimes
better and sometimes worse than the original; but not straight
code transplants. The systems had diverged far too much for that
to be easy.
If anything, the licensing problem runs the other way: System V
code taken in by the Research system. For example, the C compiler
we used most was based on pcc2, developed on the System V side of
the company after Steve Johnson moved there. I think our version
of make may have been based on a System V version as well. I'm
sure there are other (mainly smaller) examples, though since we
used no source-code control mechanism, tracing the details is
non-trivial.
None of which invalidates the basic point: there's certainly
plenty of entanglement, whether because 10/e includes ideas that
were used commercially in System V and whose mutant descendants
are still present in Solaris, or because 10/e includes some
source code directly descended from System V.
It's a shame we didn't get the several companies whose lawyers
might care to agree that there's nothing of commercial value in
the latter-day Research systems back when it was simpler to figure
out who those companies were. As I've reported here before, there
was actually some thought by certain persons here (and one who is,
alas, no longer able to be here) of doing that, some years back,
but a certain irksome legal circus about UNIX IP got going too
quickly for that to happen, and left us with the confused situation
we have today.
Norman Wilson
Toronto ON
Hello all!
Since by the jury of 2010 we now know that Novell, not SCO, owns the UNIX
copyright, is the Caldera ancient UNIX 4-clause BSD-license still valid?
Thanks in advance, God bless!
- Stefan.
I was doing a trawl of related Unix source trees, and found that some early
C code from around 2nd Edition Unix is still in OpenSolaris today:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/if.c
Choose: Compare this file to OpenSolaris_b135/cmd/fmli/sys/test.c
and then click on the Side Scroll or the Printable button.
There's about 15 lines of code in common between the 2 files.
Cheers,
Warren
> I was doing a trawl of related Unix source trees, and found that some early
> C code from around 2nd Edition Unix is still in OpenSolaris today:
If it ain't broke, don't fix it?
:-)
Does anyone have installation instructions (with binary distribution) or
a ready-to-use image for an historical 4.4BSD (encumbered or -Lite plus
needed parts or -Lite2) with gxemul, tme, or other emulator?
Or any login shell available?
(For my tests, I want to use the real thing instead of a *BSD from the
time of the 4.4BSD-lite merge.)
Thanks
I ran across this web site, which conveniently hosts man pages for a number
of bell labs operating systems. Does anyone have the man pages for 9th or
10th edition that you could please share?
That's problematic. Neither the limited-release V8 tape,
the even-more-limited V9 (I'm not sure there even was a
single such release, maybe we just sent out a few snapshots),
nor the never-really-sent-to-anyone 10th Edition system
has ever, so far as I know, escaped its original restrictive
licensing. That includes the manual pages as well as the
software proper.
10/e is even tricker, because it was published as a book;
the ordinary book copyright on the contents may apply.
And since all that stuff is 20 years or more, and several
corporate reorgs/splits/buyouts, in the past, it may be
very hard to find anyone who will agree that the stuff is
no longer of any commercial value (the software all long
since outdated, the printed book long out of print).
Warren and Dennis and I talked about this many years ago.
As I recall, we concluded that if we could get at least
one of AT&T, Lucent, or the then-believed-owner of the
UNIX commercial intellectual property to say it was OK,
the others would likely go along; Warren had at the time
a good contact with the latter entity; but said entity
was still settling down after a buyout, so it seemed
wisest to wait a few months before pushing for anything
more.
Alas, said entity was Caldera, which had just bought up
The Santa Cruz Operation. Before a few months had passed,
they had rebranded themselves as The SCO Group and shifted
their primary business from technology development to
pursuing untenable legal claims.
I've no idea where one would start these days even to
find the Gordian knot, let alone to cut it.
Norman Wilson
Toronto ON
(who wrote some of them there manual pages, and
some of the software they describe too, all a long
time ago in a hill atop a swamp far far away)
Email secured by Check Point
I ran across this web site, which conveniently hosts man pages for a number
of bell labs operating systems. Does anyone have the man pages for 9th or
10th edition that you could please share?
http://man.cat-v.org/
I gather system calls can return EINTR only when they are "slow". True?
What makes a system call "slow"? Is it the ability to block for a while?
But I wouldn't think dup(2) would block, for example.
(I -=Love=- *ix!)
Hi All.
This is interesting. It shows that (apparently) early on, assembler was
viewed as the primary programming language.
It also shows the consequences a small, apparently local decision can have:
here we are 40+ years later and GCC on Windows is still preprending
underscores to function names!
In 15 minutes I helped the guy at work solve a problem he'd been working
on for two days!
Thanks everyone,
Arnold
> From: Brantley Coile <brantley(a)coraid.com>
> To: Dave Horsfall <dave(a)horsfall.org>
> Date: Mon, 20 Feb 2012 18:34:26 -0600
> Cc: The Eunuchs Hysterical Society <tuhs(a)tuhs.org>
> Subject: Re: [TUHS] why the leading under score added to function names?
>
> correct. we could link to assembler code with _entry points and not
i> worry about symbol collisions in the rest of the code.
>
> iPhone email
>
> On Feb 20, 2012, at 6:23 PM, "Dave Horsfall" <dave(a)horsfall.org> wrote:
>
> > On Mon, 20 Feb 2012, arnold(a)skeeve.com wrote:
> >
> > [...]
> >
> >> I'm pretty sure this dates back to PDP-11 days. I'm wondering "why?".
> >> Why did the C compiler prepend an underscore to function names?
> >
> > Sure was the PDP-11 :-) I vaguely recall that it was to make sure that
> > user functions did not conflict with predefined assembler functions, as
> > that would be a pain to diagnose (much like having swap overlap root).
> >
> > -- Dave
Hi All.
Recently at work I helped someone figure out that when working with ld,
the name of a function "foo" gets turned into "_foo" by the compiler.
(It took this old-timer 15 minutes to solve a problem he had been working
on for two days!)
I'm pretty sure this dates back to PDP-11 days. I'm wondering "why?".
Why did the C compiler prepend an underscore to function names?
Thanks,
Arnold
All, I've just received from Poul-Henning Kamp a document entitled
"UNIX Program Description", dated January 1976 and written by the
UNIX Support Group. It contains detailed descriptions of the functions
inside a Unix kernel. Given the date and the USG origin, I'm guessing
that the system described is PWB/1.0. Can anybody confirm this at all?
The URL is http://minnie.tuhs.org/Archive/PDP-11/Distributions/usdl/unix_program_descr…
but I'll move it if it turns out not to be about PWB.
I love how new documents and artifacts keep appearing! Thanks phk.
Cheers,
Warren
If I recall well the /sbin directory first appeared in HP/UX,
and the name stood for 'Static binaries'. Its reason for existence
was that with the introduction of shared libraries the file with
the C-library had become a single point of failure. Therefore this
sbin was introduced to hold Statically linked executables for the
most important commands needed to fix a broken system (sh, ls, mv,
cp, find, tar, fsck etcetera). With this directory earlier than
/bin in his PATH the administrator could at least restore a working
libc.so file. And, while we are at it, the name 'executable' was
not commonly used: they were called 'binaries' (except in IBM
mainframe terminology were they were called 'load modules').
Only much later the habit of /sbin = System binaries emerged.
An important reason to split /bin vs. /usr/bin and /lib vs. /usr/lib
etc. was that the root file system had to be kept small. The fsck
program, while at work, builds tables. If possible, they stay in
memory, but if memory runs out fsck writes them to disk. However,
you don't want them to be written to an untrusted/unchecked file
system, and certainly not to the file system currently under repair.
Since the root file system has to be checked before the others, it
had to be small enough so ensure that fsck could run memory-based
only. Therefore: the /bin, /lib and other root-fs based directories
held the minimal stuff needed for booting and for repairs/restores,
while all the rest had to go into the "overflow" directories /usr/bin,
/usr/lib etc (and, obviously, /usr was a separately mounted partition).
Remember: those were the days that every reboot included a full
fsck on all your partitions.
--
Hendrik-Jan Thomassen <hjt(a)ATComputing.nl>
AT Computing
6546 BE Nijmegen NL Fax +31 24 352 72 92
info(a)atcomputing.nl www.atcomputing.nl
'If you think education is expensive, then try ignorance.'
"Jose R. Valverde" <jrvalverde(a)cnb.csic.es> said:
> Beyond that, the original articles and comments complained also about
> directory naming (/bin /etc /lib) as "unintuitive". I fail to
> understand in
> what way is it easier for someone new to a computer to learn a "/bin
> /etc /var /lib" alien terminology and what it means, than to learn
> "System Config Libraries
> etc..." or "Windows Windows32 Windows64 Temp Users and Settings,
> etc..."
In SCO Xenix/UNIX, the home directory is usually mounted on /u.
I was amused the first time I saw it.
Lyndon Nerenberg:
A well designed system without library bloat can pump out some
pretty skinny static binaries.
=======
V6, for example. Or even V7 if carefully pruned.
Once upon a time, I made an RK05 disk (5MB) with a stripped-down
post-V7 for an 11/45. It had just enough programs to allow
basic file manipulation and text-processing.
We used this compact system to allow our secretaries (in a
small university department in the early 1980s) to continue
typing up papers and letters on the day the machine-room
air conditioning was being replaced. With the doors standing
open and a big fan, we were willing to leave the 11/45 running,
but not the VAX-11/780.
Due to contractor screwups (when the chilled water was turned
on, it rained up and down the hall--many poorly-soldered
joints in the copper pipes), we actually needed this for a
couple of days, so for safety I shut the system down every
evening, removed the RK05 cartridge, and took it downstairs
to the 11/34 that had a tape drive, where I booted RT11 and
took an image backup with ROLLOUT.
Norman Wilson
Toronto ON
> http://www.osnews.com/story/25556/Understanding_the_bin_sbin_usr_bin_usr_sb…
Cute, but most of the history is wrong.
The distinction between /bin and /usr/bin is true - / held the things
need to boot the system. Other things were on /usr.
The Berkeley guys did NOT invent shared libraries. Shared libraries as
we know them came originally from Sun, on SunOS 4.x for sure, possibly
on SunOS 3.x. (Larry?) Many commercial vendors adopted the design (Ultrix,
I think, and maybe others) and finally around 4.4 they found their way into
"pure" BSD.
/home and /opt came into the picture circa 1989 with SVR4 when Berkeley,
AT&T and Sun (and maybe a few others?) got together to standardize the
layout and make diskless booting possbile and reasonable with NFS sharing
of home directories. /sbin & /usr/sbin came into the picture at this
point also, to hold executables that until then had lived in /etc. The
idea was that /etc should only have per-machine configuration files.
The general point of the article and of some of the postings, that the
proliferation doesn't make a lot of sense today, is well taken. The
Bell Labs guys themselves recognized this when they did Plan 9.
The problem is even worse on 64 bit Linux systems, which can handle
two different architectures. /lib and /lib64 confuse a lot of the
older 'configure' programs.
Personally, I hate reading articles by "experts" where 85% of the facts
are wrong. I lived through all of it, and I know better... :-)
Arnold
I've received a link http://manpages.bsd.lv/history.html claiming to
be about man pages; in fact, it's a lot more than that, including the
prehistory of troff. Interesting stuff.
Greg
--
Sent from my desktop computer
Finger grog(a)FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
Hi. I announced this in comp.lang.awk in December and tried to BCC
the TUHS list but it didn't seem to happen. Here's the announcement
I posted.
Arnold
-----------------------------------------------
From: arnold(a)skeeve.com (Aharon Robbins)
Newsgroups: comp.lang.awk
Subject: AWKCC source now available
Date: Fri, 16 Dec 2011 12:27:39 +0000 (UTC)
Message-ID: <jcfdfr$qt9$1(a)dont-email.me>
[ BCC to TUHS list, Brian Kernighan & Chris Ramming ]
awk 'BEGIN { print "Sherman, set the wayback machine for 1988" }'
Hello All.
This note is to announce that through the valiant efforts of Brian Kernighan,
Alcatel-Lucent has been persuaded to make the source for awkcc available.
It can be found at:
https://open-innovation.alcatel-lucent.com/projects/awkcc
You have to register (no cost) before being able to download, but
it's easy. The license terms are at the site. It's a straightforward
"for personal use" kind of license.
For those who don't know, awkcc is an adaptation of Unix awk to translate
nawk programs into C. It was originally implemented by Chris Ramming (then
at Bell Labs, although no longer) circa 1988, and the source dist includes
some doc that Chris wrote.
Given how fast machines are these days, this program is mostly of
historical interest. But it's nice to have this bit of Unix / awk history
generally available. And, if you really need to turn an awk program into
C, this may provide a starting point.
Enjoy!
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381
Nof Ayalon Cell Phone: +972 50 729-7545
D.N. Shimshon 99785 ISRAEL
Hi All.
I announceced this some years ago but it's been renewed, so I'll announce
it again.
In 2004 sometime I downloaded all the comp.sources stuff I could from
uunet.uu.net, which was still making it available for anonymous ftp.
I've made a tarball of it available from http://www.skeeve.com/Usenet.tar.bz2
Warren, if you don't have this in the TUHS archives, maybe you could add it?
Thanks,
Arnold
Hi,
For those who want to refresh old memories.
Hans Bezemer has made big progress as far as performance of qemu is
concerned. His specific experience concerns Coherent, but other old
unixes could use it.
Details can be found in comp.os.coherent news group
http://groups.google.com/group/comp.os.coherent/topics
The older tuhs message can be mentioned :
http://minnie.tuhs.org/pipermail/tuhs/2008-July/001815.html
I have also noticed , that Coherent boots well and is very fast in
newest virtualbox 4.1.8, running in XP.
Dell Optiplex 755 was used with Core 2 Duo.
Details can be found in forums for "Other quests"
http://www.virtualbox.org
It suggests , that other old Unixes could benefit in new virtualbox.
Regards
Andrzej
A long time ago at the University that I graduated from. . .
Shell scripts had just added the ability to have functions in them, so I wrote a script to do some processing of files that I had, and then logged off to let it run in the background.
The shell script was named 'A'.
In the script was a function, named 'A'
When the script ran, instead of calling 'A' the function, it called 'A' the script, and you can see where this goes from here.
2 days later I received an email from the admin (thankfully a friend) who enclosed the 'ps -axl' output from the machine. It showed thousands of copies of my script running and a load that indicated that the machine was useless for almost everything.
With the admonishment: "Don't ever do this again."
I haven't.
David
David Barto
barto(a)kdbarto.org
barto(a)ucsd.edu
On Mon, Dec 26, 2011 at 8:15 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
> On Tue, 27 Dec 2011, Warren Toomey wrote:
>> Yes, a good reminder on the power that programming brings us. A question
>> though: what command would "bring the system down"?
>
> It's right here: "Programmers were free to poke around to see and directly
> manipulate what was in the computer's memory."
http://minnie.tuhs.org/pipermail/unix-jun72/2008-May/000250.html
> -- Dave
--
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
Hi,
I wonder if someone has an early version of top lying around? I'd
like to try getting it to work on my ZEUS clone. I'd start with
1.0 from 1984 if possible ;)
Regards, Oliver
Hi,
I'm trying to re-create the source files for the Z8000 UNIX I have
on my Z8000 system (it is a S8000+ZEUS clone).
Easy programs like sync.c where easy. But when argc/argv is involved,
I'm not able to generate 1:1 matching binary code.
I'm working on /etc/unlink for now.
I tried the following C file:
char whatstr[] = "@[$]unlink.c 2.1 07/23/82 21:19:30 - 87wega3.2";
main(argc, argv)
int argc;
char **argv;
{
if(argc!=2) {
write(2, "Usage: /etc/unlink name\n", 24);
exit(1);
}
unlink(argv[1]);
exit(0);
}
The original ASM code for the beginning of main() until the argc
check is:
0042 abf3 dec r15,#4
0044 5df60000 ldl %0000(r15),rr6
0048 0b070002 cp r7,#%0002
The ASM code my C file generates is:
0042 abf3 dec r15,#4
0044 1df6 ldl @r15,rr6
0046 0b070002 cp r7,#%0002
keep in mine, that r15 is considered as the "stack pointer".
I wonder how to get the ldl from the original binary.
I also tried to declare argv with "char *argv[]" which
resulted in the same code. Forcing the compiler to store
argv into a register by using the "register" keyword results
in completly different code:
(sp = stack pointer = r15)
#17 adb unlink
ADB: P8000 1.6
? 0x0042/i
%0042: dec sp,#6
?
%0044: ld %0004(sp),r14
?
%0048: ld %0002(sp),r7
?
%004c: ld r14,r6
?
%004e: cp r7,#%0002
? $q
#18
Maybe the C compiler used to compile /etc/unlink differs from
the C compiler shipped with the system (maybe an older version)
but I don't want this to be true for now ;)
Anyone with deeper ASM and C knowledge than me sees what could
be done here?
Before someone asks - yes I'm sure the source file was in C
and not ASM based on the whatstr. Symboltable of the original
/etc/unlink is empty as well (striped binary).
Regards, Oliver
Sven Mascheck:
With "original implementation (post 7th ed", I meant the undistributed
BellLabs-internal further development of 7th, the first system ever
to implement #!, leading to 8th ed, etc. (4BSD just incorporated this).
Not System V or other relatives, though.
=======
Can you cite a reference?
I'm quite familiar with what went on inside the system that was
later called 8th Edition, having been on the inside at Bell Labs
starting in mid-1984. But that was after the original research
group's general move to VAXes--they had no PDP-11s left by then,
except a few LSI-11s running special-purpose systems rather than
UNIX. In fact the VAX kernel they had adopted, I think sometime
earlier that year, was derived from that of 4.1 BSD. (It diverged
quite a bit from that start later, for which I am appreciably
to blame, but that has nothing to do with #!).
So if #! was implemented in an earlier kernel I don't know just
what was done. I'd assumed it was no different; if I'm
mistaken I'd love to see just how it really was.
Alas, the person I know was on the spot and was likely to
remember just what happened in what order can no longer answer
questions ...
Norman Wilson
Toronto ON
Sven Mascheck:
Well the original implementation (post 7th ed and 4.0/4.1 BSD)
didn't allow arguments at all ;-)
======
I believe you're mistaken. All the implementations I've
ever used allowed a single argument in the #! line,
and inserted the name of the script between that (if
present) and the arguments given to exec.
e.g. if ./lipsum began with
#!/usr/bin/awk -f
awk would be invoked with `/usr/bin/awk -f ./lipsum ...'.
Without allowing one argument for -f or the like,
#! wouldn't have been useful for much but the shell.
Norman Wilson
Toronto ON
Hi all, in the past few days I've been getting some
interesting e-mails from a new TUHS member,
Jonathan Gevaryahu. He has been searching for some
lost software, and his story of how he found it
is a good reminder to check through all the zeroes
and ones on the digital media at hand. With his
permission, I reproduce the e-mails below.
Cheers,
Warren
Hi, I'm Jonathan Gevaryahu, one of the developers of MESS but also a
speech synthesis history buff. I've been trying to find a copy of the
old unix 'speak' command source code and rule tables that M. D. Mcilroy
wrote back in 1974ish, but the TUHS archives only have the man pages
for it, and not the actual program or its tables.
As for the "why?" of this, its an important piece of history, and the
phoneme set used on the Federal Screw Works "VOTRAX" Model VS-4 unit
which was used with 'speak' at Bell Labs is compatible with the later
Votrax Model VS-6 unit at CHM, and also with the Votrax "SC-01" chip
used in some arcade/video games, several computer peripherals, and on
the "Type 'N' Talk" and "Personal Speech System" products. So actually
running the old code and having it speak should be quite doable, if we
can recover enough of it to be useful.
[ Jonathan assumed that the 'speak' source code had been lost. ]
I even asked Doug McIlroy about it a few years ago and he didn't have
a copy, and I had assumed it was just plain lost... Until today.
I was poking around in random TUHS files (after reading about
the v1 unix restoration project) and noticed that the size of
recovered files from the ritchie v6 tapes in the .tar.gz files
is actually significantly smaller than the tapes themselves. I
assumed there had to be some other data there, possibly corrupt or
fragmentary, and got down to peeking at the file contents themselves.
There were some mentions of speak.m and .c and .v, but finally, in
http://minnie.tuhs.org/Archive/PDP-11/Distributions/research/Dennis_v6/v6do…
I found the remains of the speak program. See
http://pastebin.com/FdvRYM2T for what I've managed to recover so far
(actually since i pasted that I recovered a good deal more of it, but
a lot is out of order and bits are missing) The file is fragmentary as
far as I can see, and is only speak.c (the .m file containing the rules
I haven't found yet, but since Doug has a scanned copy of the paper
describing speak on his website, hopefully I can just regenerate the
rule tables if needed), but it is there! Hopefully speak.m or .v are
still waiting to be found on that or one of the other tape images.
Also there are other things on that tape like the chess program, and
tic tac toe, which may not exist elsewhere. (Though, for these two I
honestly haven't checked)
Also, in the last 5 minutes I found a chunk of what I'm pretty sure is
either speak.m or speak.v, so there's more than just the .c file there.
Further progress attached of recovering speak from deleted disk pack
sectors: I have all of speak.c in order except for one 512-byte sector,
which was overwritten at some point, in the phoneme table. (This has to
be the least "damaging" sector of the entire program. lucky!) I also
have a good chunk (maybe 50-60%) of what may be a mix of speak.m and
speak.v, both out of order. I did not yet find
a copy of 'speakm', the rule displayer program for speak.m/.v. There is
a program, located after speak.c on the disk image, which looks like it
would convert numbers and months to their full speakable names.
In addition, either slightly more or slightly less of the files may be intact
on the
http://minnie.tuhs.org/Archive/PDP-11/Distributions/research/Ken_Wellsch_v6…
image, which appears to be originally an exact dd-copy of the dennis_v6
disk packs.
Ok, here's the 'repaired' speak.c file, with the missing entries of the
table filled in (this was IMMENSELY helped by the fact that speak.o, the
compiled object file, was also on the disk pack and appears to be fully
intact including the table; the ruleset files are fragmentary so far.)
All, here's a special Christmas present, especially for those who
helped out with the restoration of the 1st Ed Unix system, see
http://code.google.com/p/unix-jun72/
To do the restoration we needed a copy of the 1st Ed Unix kernel
source code, and Al Kossow had found these two documents and
scanned them in:
http://minnie.tuhs.org/Archive/PDP-11/Distributions/research/Dennis_v1/Kern…http://minnie.tuhs.org/Archive/PDP-11/Distributions/research/Dennis_v1/Prel…
At the time nobody could work out who had studied the kernel source code,
why they had done it etc. Nor could we work out who Ted Bashkow was and
why he was involved.
After my IEEE Spectrum article I was contacted by Jim DeFelice to say
thanks for the article. I recognised him as one of the people named in
the above documents, and asked him about the kernel study. He has contacted
some of the people involved and sent me the e-mail below, which gives
a full description of the work!
Before I get to it, just an aside. According to Berkley Tague,
Ted Bashkow "was a visiting Professor for the summer some time around
1970 or 1971 and worked with me and others in research on various
topics. I don't believe he contributed much to UNIX at that time, but
was an early user of the early systems."
Cheers,
Warren
[ Jim's story]
Here is as coherent a story as I can piece together Let me know if you
have any more questions.
Jim.
The documents that describe the UNIX system as it was implemented on
the PDP-11/20
circa 1971 originated as a consequence of a project undertaken within
the comptrollers
department of the AT&T General Departments. The project was titled the
Investment and Cost Information System (ICIS). It was a major new
accounting system intended to track
detailed cost information for the operating telephone companies of the
Bell System.
ICIS was a major IBM mainframe based system which was being developed
in COBOL.
I transferred from Bell Labs in late 1970 to join Chuck Everhart who
preceded me from the Labs. In 1971 we were joined by Ron Silacci, Cathy
Judge, and later (early '72?) Jerry Conser all from Bell Labs. We
formed the core of what would become
a much larger Development staff by 1973.
In preparation for a major development effort, we wanted to develop a
system to maintain the spate of expected ICIS specification and design
documents including graphics such as flowcharts. We decided on the
PDP-11/20 with a Tecktronix T4002 graphics terminal as the hardware
platform for the development of our document maintenance system.
For obscure reasons, in order to purchase the PDP-11/20, the ICIS team
needed to get approval from the Bell Labs computer aquisition review
department headed
by Berkley Tague. Berk made the approval for the purchase contingent
us agreeing to use UNIX as the operating system.First hearing of this
"UNIX" verbally, my mind was filled with scenes from the Arabian
Nights. "Eunuchs" seemed a strange name for an operating system.
At the time, the only instances of UNIX were to be found in the hands
of the developers (Ken Thompson & Co.) at Murray Hill, NJ. We
naturally asked for all the documentation. We were told there was
none. What we got was a source listing of the PDP-11 assembly
language UNIX Kernel. It was virtually without any commentary or
external description. In order to proceed we undertook to reverse
engineer the listing in order to understand how to
modify UNIX to support the T4002. To that end, in late 1971, we set up
shop at a Labs facility in Piscataway, NJ. The team got occasional
hints and pointers from the UNIX developers at Murray Hill, but they
tended to be focussed on their own work (the C programmimg language,
troff, etc.). Initial progress was slow, but as the overall design
structure emerged and the team became fluent with PDP assembly
language and the coding style of the UNIX developers things moved
along. Early work was
done with paper and pencil resulting in the document named by you as
"Kernel Subroutine
Description...". Once we took delivery of our PDP-11/20, we were able
to make
use of the UNIX tools "ed" and "roff" to create a more easily edited
digital document
"Preliminary UNIX Implementation Document"
The detailed timing of all this is uncertain. The hand work was done
from late 1971 through
March 1972 resulting in the Kernel Subroutine documentation. Chuck
Everhart left AT&T
in late 1971 and I became the group supervisor. A draft of the machine
based Preliminary
Implementation document was completed by June 1972 per the date on my
cover letter for its first distribution. By June 1972 there was
evidently a lot of interest in UNIX inside Bell Labs. The computer
commitee was pushing UNIX for all PDP based projects inside Bell Labs.
The ICIS owned PDP-11/20 was probably received after March 1972. The
hand written cover letter to Ted Bashkow is dated 4/3/72. Once we had
use of the PDP-11 we would have entered our work directly. The
modifications for the T4002 are not dated in
your PDF version and do not appear in the original printout that I
still have. I don't know why the date on all the printed pages is
3/17/72. Also, missing in the PDF version of the Preliminary
Implementation document that is in the paper version is a subroutine
cross reference listing that lists which subroutines are called by
which.
Regarding the authorship of the documents. Looking at the handwriting
it seems
at least four people contributed to the Kernel Subroutine document.
Myself and Ron
have actually reviewed the document and can claim authorship to
specific sections. By sections:
J. DeFelice
H0_01, H0_02, H0_03,H0_04,H0_05, H2-11_sysexec call chain,
H2.4,H2_1.7,H2-8,
H2-9 H4-3, H5-1, H5-2, H5-3, H5-4, H5-7,
H7-1, H7-2, H7-4, H7-5,H7-6, H8-01.2, H8-02, H8-03, H8-05, H8-06,
H8-07,
H8-08, h8-09-00, h5-6
Ron Silacci
sysclose, syscreate, sysent, sysexit, sysfork, sysmdate, sysgetty,
sysmdir,
error, badsys, sysopen, sysret, sysrele, sysstty, syswait, read, write,
ani,
sysstat, sysgetuid, sysintr, syslink, sysseek, syssetuid, sysstat,
sysstime,
systime, sysquit, sysunlink, wdir, fclose, isdir, isown, maknod, mkdir,
getf,
seektell, sysbreak, syschdir, syschmod, syschown, clear, idle, putlu,
swap,
tswap, unpack, rswap, wswap, clock, isintr, retisp, sleepo, setisp,
tty0,
wakall, ttyi, wakeup, itrunc, imap, dskr, cpass, readi, canon, cesc,
ctty,
ttych, getspl, iclose, iopen, sysmount, sysumount, bread, bwrite,
dioreg, drum, preread, rtap, tape, tstdeve, trapt, rw1, intract, otty.
Unknown 1 (all caps)
H4_00, H4_01, H4_02, H4_2.1, H6_2.2, H6_3.0, H6_6, H7_0.0.4, H7_3.0,
H7_3.2
H7_3.3, H9_00.1, H9_01, H9_02, H9_03
Unknown 2
H0_06, H0_07, H2_0.2, H2_3,H2_4, H3_2, H3_4, H5_2.0, H5_2.1,H6_0.9,
H6_1.0,
H6_1, H6_2.0, H6_2.2, H6_3, H6_4, H8_09, H8_11
The two unknowns would be Jerry Conser and Cathy Judge. I have not
been able to track
them down.
The comments in the listing were made by the people who authored the
corresponding man pages. We would comment the listing and as
understanding dawned write up the man page. I had a major hand in
Section F but can't claim sole responsibility.
The people listed in the recipients list in Ted Bashkow's cover letter
are the members of the computer aquisition department. According to
Joe Maranzano:
"Ted Bashkow was a professor from Columbia who was on a 6-month
sabbatical in Berkley Tague's department.
The other names on the memo are:
Dan Clayton
David Copp
Gwen Hansen
Jossie Hintz
Ruth Klein
Jim Ludwig
Georgette Petit
Joe Ritacco
Berk Tague
Dan Vogel
Linda Wright
This was the composition of the Department in 1972 and most of us were
working on Computer Acquisition Reviews for
the Computer Centers. The Unix Support Group was formed in 1973."
By the time the Tecktronix application was developed, the ICIS
development project was ramping up. The developers were using punch
cards for their Cobol programs. It occurred to me that we could
utilize our UNIX system to eliminate punch cards which were difficult
to manage and instead enter and edit the Cobol code using "ed". My
management (rotated in from Bell Operating Companies) was not keen on
diverting resources towards
more tool building but I had enough autonomy to push through the
ordering of a PDP-11/45 and a DEC developed Bisync communications
interface card. This configuration allowed the UNIX system to emulate
an IBM card reader/printer.
The PDP11/45 had memory protection, which made committing all the
source code for a major project to UNIX thinkable. I did all the
development work on a bisync driver myself while my group attacked the
main IBM development. The resulting system worked well and over the
course of a few months all the die hard card rearder afficianados had
converted to the new system. This despite the occasional file system
crash. At the time you could go in and edit i-nodes by hand to recover
lost files and directories. So with frequent tape backups for insurance
we never lost more that a few hours worth of work.
The Bell Labs UNIX support department (formed in 1973) eventually took
over the maintenance of the system and dubbed it the Programmers Work
Bench. Other types of workbench were to follow. I lost track of
developments in the UNIX world till I transferred back to Bell Labs in
1982. By then the UNIX support organization was an entire
Laboratory. The hardware platform was the DEC VAX system, UNIX was
rewritten in C, and Berkely UNIX was a major competitor to the AT&T
version. I still have the design and code for the Bisync driver if you
are interested.
Arnold Skeeve:
Have you asked Doug McIlroy?
=======
Actually I did, last night, on Warren's behalf.
I had meant to drop Doug a note anyway to apologize
for not letting him know I was in his general neighborhood
last week.
Here's Doug's reply:
Pipes were first documented
in v3, Feb 1973. At that time my original clumsy shell
syntax, cmd>cmd>[file] was still in use. Within a few
months, Ken invented today's pipe symbol as something
more presentable at a talk he'd been invited to give
in England--an Infosys "State of the Art" conference
if I remember correctly (not the same Infosys as the
current Indian giant).
I also remember the very blackboard in the garret
lab where I sketched my syntax and Ken exclaimed,
"I'll do it". That was late in the day and I'm
quite sure it was dark outside. Unlike Ken, I
was not in the habit of staying in the lab into
the evening. That makes me think that pipe day
was not too far off the solstice.
It would be nice to believe that pipes preciptated
the third edition, but in fact the first four editions
came out almost like clockwork at 8-month intervals,
so any correlation with pipes is highly speculative.
======
Norman Wilson
Toronto ON
(actually Ramsey NJ at the moment, a good bit north of Murray Hill)
All, would anybody have an e-mail address for Dick Haight? I am still
trying to narrow done the date when pipes were added to Unix, so far
between June 72 and January 73. I have this quote from Dick:
"I happened to have been visiting the research crew the
day they implemented pipes. It was clear to everyone
practically minutes after the system came up with pipes
working that it was a wonderful thing. Nobody would ever go
back and give that up if they could help it."
so he might be able to provide a smaller date range than what I have
at present.
Cheers,
Warren
Dave Horsfall scripsit:
> Great atricle :-)
Great ventricle, too.
--
But you, Wormtongue, you have done what you could for your true master. Some
reward you have earned at least. Yet Saruman is apt to overlook his bargains.
I should advise you to go quickly and remind him, lest he forget your faithful
service. --Gandalf John Cowan <cowan(a)ccil.org>
All, not terribly Unix specific, but here's a good
read for those who have suffered at the hands of
field circus engineers :)
http://nemesis.lonestar.org/stories/stages.html
Have a good Xmas everyone.
Warren
Also, is there a place where I can download archives of Usenet groups
in a plain text format? I think I've got v6.bugs and v7.bugs and some
of comp.sources.unix. I just came across net.unix on Google Groups,
but I'd rather not have to wget all that HTML!
Thanks,
Warren
All,
My IEEE Spectrum article finally got published and you can read it
on-line here: http://spectrum.ieee.org/computing/software/the-strange-birth-and-long-life…
I've had a few e-mails about it. This one has a few more snippets about
early Unix history (from Rey Bonachea):
It was with great pleasure and a bit of nostalgia that I read your IEEE
article below. Thank you very much for writing it. One aspect that did
not get mention, and that perhaps you may or may not be aware of, was
the pseudo real time applications of Unix.
In 1972 I joined Bell Labs in Holmdel NJ working on a project by the name
of Switching Control Center System. At the beginning I was just a brand
new member of the technical staff working on circuit design for
interfaces to the PDP11/20. This project was meant to centralize the data
streams from the maintenance channel of switching machine. Then, in a
multi-user environment , would analyze the incoming data streams and raise
alarms as appropriate. It also provided a whole suite of analysis tools to
allow switch maintenance personnel to trouble shoot the electronic
switches.
Because the switches could not buffer messages or be slowed by flow
control, the Unix system had to catch messages in real time and put it
away on disk for later analysis. Due to the near real time requirements, a
number of features were added to Unix such as semaphores. The Unix based
Switching Control Center System (SCCS) software was trialed in New
Brunswick NJ in 1973 and later that year was released as the first
commercial application of the Unix OS.
I learned to program on that PDP 11/20 computer running Unix and
eventually wrote many applications for the SCCS, initially in assembly
language and then in C as we were also the first project to use C
commercially.
Cheers,
Warren
Hi,
In memoriam, I read The Development of the C Language:
http://cm.bell-labs.com/who/dmr/chist.html
It talks a bit about how B was originally implemented somewhat like
ETH Pascal (p-code). Are there any B interpreters or programs in the
archive?
Thank you,
A. P. Garcia
Yep, dungeon runs great on RT-11 ... I've docuemnted the experence here...
http://virtuallyfun.superglobalmegacorp.com/?p=169
Building the fortran compiler was... an adventure onto its own, but luckily
I found some documentation @ bitsavers, and could ask on the PDP11 lists for
help... I'm amazed it compiled and runs! ..
Oh and TripOS is the BCPL based OS that ran on all kinds of machines, it was
very portable, the best known port would be AmigaDOS for the Commodore
Amiga. I wonder if it was licensing fees and BCPL/TripOS being based in the
UK what seperated them from C/Unix... I guess we'd be living in the B++, B#
and ObjectiveB world if it wasn't for DMR's wonderful world of C .. :)
-----Original Message-----
From: Gregg Levine [mailto:gregg.drwho8@gmail.com]
Sent: Saturday, October 15, 2011 12:37 AM
To: tuhs(a)minnie.tuhs.org
Cc: Jason Stevens
Subject: Re: [TUHS] b remnants?
On Sat, Oct 15, 2011 at 12:20 AM, Jason Stevens
<jsteve(a)superglobalmegacorp.com> wrote:
> Wasn't the other 'advantage' of threaded/pcode that it'd be smaller than a
> native executable?
>
> I know it's out of left field, but building Dungeon on RT-11, you have to
> use the treaded compiler, and I assume it was a space thing.. Just as on
> MS-DOS (Yeah I know...) a save for fitting stuff in 64kb for the later
> compilers was to compile to p-code..
>
> Wikipedia gives p-code for Pascal a timeframe of the 'early 70's and
> attribes the whole interpeted code as O-Code for BCPL ....
>
> I wonder if anyone ever did save any TripOS tapes for the PDP-11.....
>
> -----Original Message-----
> From: A. P. Garcia [mailto:a.phillip.garcia@gmail.com]
> Sent: Friday, October 14, 2011 11:58 PM
> To: tuhs(a)minnie.tuhs.org
> Subject: Re: [TUHS] b remnants?
>
>
> On Fri, Oct 14, 2011 at 9:52 AM, A. P. Garcia
> <a.phillip.garcia(a)gmail.com> wrote:
>>
>> In memoriam, I read The Development of the C Language:
>> http://cm.bell-labs.com/who/dmr/chist.html
>>
>> It talks a bit about how B was originally implemented somewhat like
>> ETH Pascal (p-code). Are there any B interpreters or programs in the
>> archive?
>
> What intrigued me about this is that it's such an early example of an
> abstract machine running as an interpreter. BCPL, roughly
> contemporaneous, used ocode as an intermediate language, but it seems
> this was intended to be further translated into assembly. While it's
> possible to interpret ocode, in practice it seems this was rare, if it
> was done at all. Almost everything I've read about abstract/vitual
> machines traces its roots back to the following source:
>
> James R. Bell. 1973. Threaded code. Commun. ACM 16, 6 (June 1973),
> 370-372. DOI=10.1145/362248.362270
> http://doi.acm.org/10.1145/362248.362270
>
> Here's where dmr mentions implementing B using this technique:
>
> The B compiler on the PDP-7 did not generate machine instructions, but
> instead `threaded code' [Bell 72], an interpretive scheme in which the
> compiler's output consists of a sequence of addresses of code
> fragments that perform the elementary operations. The operations
> typically-in particular for B-act on a simple stack machine.
>
> Note he says it was published in 1972, when it actually appeared in
> print in 1973 (same page numbers). Two paragraphs later he writes:
>
> By 1970, the Unix project had shown enough promise that we were able
> to acquire the new DEC PDP-11. The processor was among the first of
> its line delivered by DEC, and three months passed before its disk
> arrived. Making B programs run on it using the threaded technique
> required only writing the code fragments for the operators, and a
> simple assembler which I coded in B; ; soon, dc became the first
> interesting program to be tested, before any operating system, on our
> PDP-11. Almost as rapidly, still waiting for the disk, Thompson
> recoded the Unix kernel and some basic commands in PDP-11 assembly
> language. Of the 24K bytes of memory on the machine, the earliest
> PDP-11 Unix system used 12K bytes for the operating system, a tiny
> space for user programs, and the remainder as a RAM disk. This version
> was only for testing, not for real work; the machine marked time by
> enumerating closed knight's tours on chess boards of various sizes.
> Once its disk appeared, we quickly migrated to it after
> transliterating assembly-language commands to the PDP-11 dialect, and
> porting those already in B.
>
> The abstract machine is also mentioned in Thompson's "Users' Reference
> to B", dated January 7, 1972. If the 1970 date is correct, they were
> using this technique some three years before most of the computing
> world knew about it!?
Hello!
This discussion is beginning to strike a heck of a lot of chords.
Jason what is this TripOS you are describing here about? And did you
actually get Dungeon to work?
-----
Gregg C Levine gregg.drwho8(a)gmail.com
"This signature fought the Time Wars, time and again."
Wasn't the other 'advantage' of threaded/pcode that it'd be smaller than a
native executable?
I know it's out of left field, but building Dungeon on RT-11, you have to
use the treaded compiler, and I assume it was a space thing.. Just as on
MS-DOS (Yeah I know...) a save for fitting stuff in 64kb for the later
compilers was to compile to p-code..
Wikipedia gives p-code for Pascal a timeframe of the 'early 70's and
attribes the whole interpeted code as O-Code for BCPL ....
I wonder if anyone ever did save any TripOS tapes for the PDP-11.....
-----Original Message-----
From: A. P. Garcia [mailto:a.phillip.garcia@gmail.com]
Sent: Friday, October 14, 2011 11:58 PM
To: tuhs(a)minnie.tuhs.org
Subject: Re: [TUHS] b remnants?
On Fri, Oct 14, 2011 at 9:52 AM, A. P. Garcia
<a.phillip.garcia(a)gmail.com> wrote:
>
> In memoriam, I read The Development of the C Language:
> http://cm.bell-labs.com/who/dmr/chist.html
>
> It talks a bit about how B was originally implemented somewhat like
> ETH Pascal (p-code). Are there any B interpreters or programs in the
> archive?
What intrigued me about this is that it's such an early example of an
abstract machine running as an interpreter. BCPL, roughly
contemporaneous, used ocode as an intermediate language, but it seems
this was intended to be further translated into assembly. While it's
possible to interpret ocode, in practice it seems this was rare, if it
was done at all. Almost everything I've read about abstract/vitual
machines traces its roots back to the following source:
James R. Bell. 1973. Threaded code. Commun. ACM 16, 6 (June 1973),
370-372. DOI=10.1145/362248.362270
http://doi.acm.org/10.1145/362248.362270
Here's where dmr mentions implementing B using this technique:
The B compiler on the PDP-7 did not generate machine instructions, but
instead `threaded code' [Bell 72], an interpretive scheme in which the
compiler's output consists of a sequence of addresses of code
fragments that perform the elementary operations. The operations
typically-in particular for B-act on a simple stack machine.
Note he says it was published in 1972, when it actually appeared in
print in 1973 (same page numbers). Two paragraphs later he writes:
By 1970, the Unix project had shown enough promise that we were able
to acquire the new DEC PDP-11. The processor was among the first of
its line delivered by DEC, and three months passed before its disk
arrived. Making B programs run on it using the threaded technique
required only writing the code fragments for the operators, and a
simple assembler which I coded in B; ; soon, dc became the first
interesting program to be tested, before any operating system, on our
PDP-11. Almost as rapidly, still waiting for the disk, Thompson
recoded the Unix kernel and some basic commands in PDP-11 assembly
language. Of the 24K bytes of memory on the machine, the earliest
PDP-11 Unix system used 12K bytes for the operating system, a tiny
space for user programs, and the remainder as a RAM disk. This version
was only for testing, not for real work; the machine marked time by
enumerating closed knight's tours on chess boards of various sizes.
Once its disk appeared, we quickly migrated to it after
transliterating assembly-language commands to the PDP-11 dialect, and
porting those already in B.
The abstract machine is also mentioned in Thompson's "Users' Reference
to B", dated January 7, 1972. If the 1970 date is correct, they were
using this technique some three years before most of the computing
world knew about it!?
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
I didn't see it as immeditaly obvious on slackware 1.0 ... or SLS .. it very
well may have been some addon or something somehwere....
If anyone knew it's filename that'd go a long long way! :)
-----Original Message-----
From: Derrik Walker [mailto:lorddoomicus@mac.com]
Sent: Friday, October 14, 2011 12:36 PM
To: Gregg Levine
Cc: tuhs(a)minnie.tuhs.org
Subject: Re: [TUHS] b remnants?
On Oct 14, 2011, at 11:53 AM, Gregg Levine <gregg.drwho8(a)gmail.com> wrote:
> On Fri, Oct 14, 2011 at 11:34 AM, Derrik Walker <lorddoomicus(a)mac.com>
wrote:
> > Many, many eons ago, in the early '90's, there was an implementation of
B
> > for Linux ( I believe it was written in C, ironically enough ). I think
it
> > was part of a bigger collection of "ancient" software for Linux that use
to
> > be around in the early Slackware days.
> >
> > Alas, I have searched for it in the recent past, as I was thinking about
> > porting it to OS X for kicks, but it seems to have vanished.
> >
> > Having an B, implemented in a modern language for a modern OS would be
cool.
> >
>
>
> Hello!
> How early a time period for the Slackware Linux group? (Which is what
> I run.) There's a repository of older distributions on the Ibib site,
> and a more comprehensive one situated on a mirror in the UK.
It would have been around '92 or '93, back when Slackware really only
provided a very basic boot system, gcc, some fancy scripts, and a crap load
of tarballs to compile everything. I'm not even sure it was part of the
Slackware collection, it might have been something someone added to the
server - I didn't build that computer.
It was an experimental system at CSU, where I was going to school at the
time - and the first actually Linux computer I ever had an account on. One
of the older professors had a bunch of B code he got from someplace and put
the compiler on there to see if he could get it to build. I remember he
also put f2c on there too as he had a tape full of Fortran code he wanted to
compile.
But, for all I know, he may have written the B compiler himself, but I seem
to remember him telling me about this collection of ancient software for
Linux that someone else had written, and he had gotten it up and running on
the experimental Linux system. Just not sure how faulty my memory is. I
just remember looking at B, and asking why he just doesn't covert it to C?
Funny thing was, some of the younger professors were complaining saying the
preferred their "REAL UNIX".
Unfortunately, he as long since retired. And that Computer was retired when
they moved the main Student system from HPUX to Redhat in the late '90's.
- Derrik
Just for the record.
The correct way to mirror a site with links corrected is
wget -c -m -k -np -e robots=off URL
Seems most people have problem remembering this incantation.
--
EMBnet/CNB
Scientific Computing Service
Solving all your computer needs for Scientific
Research.
http://bioportal.cnb.csic.eshttp://www.es.embnet.org
We could set up a web site
inmemoriamdmr.org
maybe initially as a wiki and ask people to add their contribution
and then maybe we could try to collect there his works or add a blog with
articles about him that could be commented...
Just an idea, I am in the middle of a Congress, seated in the front
row and trying to listen to speakers through my consternation, and can do
very little now.
j
--
EMBnet/CNB
Scientific Computing Service
Solving all your computer needs for Scientific
Research.
http://bioportal.cnb.csic.eshttp://www.es.embnet.org
Truly a great loss.
I just saw this (I have traveling to some international meetings).
I wonder if we could come up with a way to pay hommage to him
all together to acknowledge his legacy.
Don't know what could be best, but I am sure there are people
here who knew him and through their consternation can give us an idea
of what would be the best way to publicly honor him.
Can we all get together to do something jointly for him? I
guess a global collaborative initiative would be most in his spirit
and philosophy of life.
Dunno, maybe create web site to celebrate him. Where everybody
can leave a testimony of how his work has affected our lives.
j
--
EMBnet/CNB
Scientific Computing Service
Solving all your computer needs for Scientific
Research.
http://bioportal.cnb.csic.eshttp://www.es.embnet.org
True. I had to mirror via ftp as the robots.txt stopped the http mirroring. It should be possible to fix the mirror in the tarball. I'll see what I can do.
Thanks, Warren
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Hans Ottevanger <hansot(a)gmail.com> wrote:
On Thu, Oct 13, 2011 at 6:57 AM, Warren Toomey <wkt(a)tuhs.org> wrote: > All, I've taken a mirror of http://cm.bell-labs.com/cm/cs/who/dmr/ > and placed it at http://minnie.tuhs.org/dmr/ > > Feel free to mirror from minnie, in case the Labs' server gets overloaded. > It's 112 Megs. > Warren, Thanks for this excellent action, but your links are still absolute, i.e. point to the original content on the Bell Labs website. If that content disappears for whatever reason you will have a lot of links to convert. Kind regards, Hans Ottevanger
On Wed, Oct 12, 2011 at 10:02:08PM -0700, Lyndon Nerenberg wrote:
> >Feel free to mirror from minnie, in case the Labs' server gets overloaded.
> >It's 112 Megs.
>
> A tarball, perhaps?
Of course. ftp://minnie.tuhs.org/misc/dmr_cm.bell-labs_mirror.tar.gz 90M
Cheers,
Warren
For those of you who haven't heard yet, dmr died on Sunday. Rob Pike
announced it at
https://plus.google.com/101960720994009339267/posts/ENuEDDYfvKP
I don't know what to say. A *real* giant is dead. And almost the
saddest thing is that nobody has paid any attention.
Greg
--
Sent from my desktop computer
Finger grog(a)FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
https://plus.google.com/101960720994009339267/posts/ENuEDDYfvKP?hl=en
I just heard that, after a long illness, Dennis Ritchie (dmr)
died at home this weekend. I have no more information. I trust
there are people here who will appreciate the reach of his
contributions and mourn his passing appropriately. He was a quiet
and mostly private man, but he was also my friend, colleague,
and collaborator, and the world has lost a truly great mind.
- Pob Pike
With great thanks and appreciation to him,
Warren
That is kind of what I'd imagine... In 1983 I thought 160kb was infinate
storage.. lol
> -----Original Message-----
> From: Lyndon Nerenberg (VE6BBM/VE7TFX) [SMTP:lyndon@orthanc.ca]
> Sent: Friday, September 09, 2011 6:23 PM
> To: jsteve(a)superglobalmegacorp.com; dave(a)horsfall.org; tuhs(a)tuhs.org
> Subject: Re: [TUHS] UNIX V 6.9999999 ?
>
> > It is insteresting reading about people haveing
> > 600MB of storage back in 1981
>
> You mean both of them?
Ah that makes sense, I could totally see that happening.. Esp with the cost
of hardware back then! It is insteresting reading about people haveing
600MB of storage back in 1981.. I can only imagine how much it'd have cost!
Thanks again!
Jason
-----Original Message-----
From: Dave Horsfall [mailto:dave@horsfall.org]
Sent: Wednesday, September 07, 2011 11:36 PM
To: The Eunuchs Hysterical Society
Subject: Re: [TUHS] UNIX V 6.9999999 ?
On Wed, 7 Sep 2011, Jason Stevens wrote:
> What is UNIX V 6.9999999?? I suspect it's v6 with a bunch of patches,
> but not quite v7? I've seen from some Russian stuff that they prefered
> v6 on pdp-11's as it "ran faster" than v7 and needed far less ram/disk
> space... I know it's 30 years too late to ask them what it is but I
> figure someone may have actually ran/used 6.9999999...
Back in the V6 days, I was known as Mr Unix 6-and-a-half, because I'd
spliced all sorts of V7 features into V6 - notably XON/XOFF, and there was
no way that V7 would run on the 11/40,
I rewrote the Calcommp and Versatec plotter drivers to use the block
interface, and they went like a bat out of hell.
Sigh... We had fun in those days.
-- Dave
_______________________________________________
TUHS mailing list
TUHS(a)minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
> > Interesting. I've taken a look at the sources from the CD set and
> found that the text there (in /usr/src/sys/sys/machdep.c) is the same
> > as above. Looking further, the entire directory has the same files in
> > 4.0 and 4.1, with the same modification dates. So it looks as the 4.0
> > sources accidentally got replaced by the 4.1 sources.
>
Hmmm, no, I don't have anything useful to add.
I suspect you could check the modification dates on the files, and the file
SCCS IDs, against the source-code revision logs to figure this out for sure.
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
keith(a)bostic.com
While cruising olduse.net I came across this puzzling entry in net.general
Department of Computer Engineering and Science
Case Western Reserve University
Cleveland, Ohio
We would like to announce our connection to Usenet. We are a
private university located in Cleveland, vacation spot of the midwest.
The department's primary facilities consist of:
VAX 11/780: hardware: RM05's, TU77, DZ-11, DH-11 (able), 2.5 Mbytes.
software: 4.1 BSD
PDP 11/45: hardware: RM02, DS330 (RP04), RK05, RX02, RS04(solid
state)
cache45 (able), DH-11
software: UNIX V 6.9999999
What is UNIX V 6.9999999?? I suspect it's v6 with a bunch of patches, but
not quite v7? I've seen from some Russian stuff that they prefered v6 on
pdp-11's as it "ran faster" than v7 and needed far less ram/disk space... I
know it's 30 years too late to ask them what it is but I figure someone may
have actually ran/used 6.9999999...
Thanks
Jason Stevens
All, IEEE Spectrum have asked me to write a paper on Unix to celebrate the
40th anniversary of the release of 1st Edition in November 1971. I'm after
ideas & suggestions!
I think my general thrust is that Unix is an elegant design, and the
design elements are still relevant today. The implementation is mostly
irrelevant (consider how much the code has changed from assembly -> C,
from the simple data structures in V7 through to current BSD), but the
original API is classic. Note that about 28 of the 1st Ed syscalls are
retained in current BSDs and Linux, and with the same syscall numbers.
I'm having some trouble thinking of the right way to explain what is
an elegant design at the OS/syscall level, so any inspirations/ideas
would be most welcome. I might highlight a couple of syscall groups:
open/close/read/write, and fork/exec/exit/wait.
If you have any references/URLs you think I should look at, please
pass them on to me.
I'm also trying to chase down some quotes; my memory seems to be failing me
but I'm sure I've seen these somewhere:
- in a paper, I think by Thompson & Ritchie, where they assert that the
kernel should provide no more than the most minimal services to the
userland programs. I thought this was the CACM paper, but I can't spot
this bit. Maybe it's in Thompson's preface to the Lions Commentary,
of which my copy is elsewere at present.
- I'm sure I remember someome (Kernighan?) say that Ritchie encouraged
them to espouse the use of processes as context switching was cheap,
but later measurements showed that in fact it wasn't that cheap in
the early versions of Unix.
Anyway, if you can think of good ideas/references about the elegance of
Unix, especially from the design perspective, I would much appreciate them.
Cheers,
Warren
Hi all,
As part of my IEEE Spectrum article on 40 years since 1st Edition
Unix, I've been asked for some suitable imagery/photos. Has anybody brought
1st Edition up on a real PDP-11/20, and if so, could they take some photos
of the system?
I think they would even be happy with photos of PDP-11s running V6 or V7.
Anything that you can supply would be great - there is not a lot of
photos from the early days of Unix.
Thanks in advance,
Warren
I was looking at Tom Yam's 4.0 BSD 'starunix' restoration project, and I had
a question about the version number that is reported vs the dates... I'm
using wikipedia as a source (I know I know..)
Anyways Tom's 4.0 boots up like this:
: hp(0,0)vmunix
87844+15464+130300 start 0x530
VM/UNIX (Berkeley Version 4.1) 11/10/80
But the wiki page lists 4.1 being from June of 1981, and 4.0 being from
November of 1980.. Did 4.0 BSD ship reporting itself as 4.1? I guess there
is the possibility that the kernel may include patches to bring it up to
4.1?
Does anyone have tape dumps of 4.0 & 4.1 ...?
I did find some iso image that has various levels of BSD but they are not in
tape dumps but rather extracted to the filesystem.. the 4.0 & 4.1 from there
seem identical Or at a minimum they use the same kernel that reports itself
as 4.1 ...
Anyways I'm just wondering....
Jason Stevens
Also from that cd image there was enough of 4.1c to make a working system by
untarring it from within 4.2 BSD ...
VAX780 simulator V3.8-1
Listening on port 23 (socket 156)
loading ra(0,0)boot
Boot
: ra(0,0)vmunix
215688+63964+69764 start 0xf98
4.1c BSD UNIX #2: Tue Aug 28 09:39:12 PDT 1984
real mem = 8384512
avail mem = 7036928
using 148 buffers containing 838656 bytes of memory
mcr0 at tr1
mcr1 at tr2
uba0 at tr3
hk0 at uba0 csr 177440 vec 210, ipl 15
rk0 at hk0 slave 0
rk1 at hk0 slave 1
uda0 at uba0 csr 172150 vec 774, ipl 15
ra0 at uda0 slave 0
ra1 at uda0 slave 1
zs0 at uba0 csr 172520 vec 224, ipl 15
ts0 at zs0 slave 0
dz0 at uba0 csr 160100 vec 300, ipl 15
mba0 at tr8
root on ra0
WARNING: should run interleaved swap with >= 2Mb
Automatic reboot in progress...
Tue Aug 28 09:54:53 PDT 1984
/dev/rra0a: 836 files, 6010 used, 1419 free (35 frags, 173 blocks)
/dev/rra0h: 6598 files, 41780 used, 320080 free (160 frags, 79980 blocks)
Tue Aug 28 09:54:58 PDT 1984
local daemons: telnetd ftpd tftpd syslog sendmail.
preserving editor files
clearing /tmp
standard daemons: update cron accounting berknet mail printer.
starting network: rshd rexecd rlogind rwhod routed.
Tue Aug 28 09:55:00 PDT 1984
ucbmonet login: root
Last login: Tue Aug 28 09:44:44 on tty00
4.1c BSD UNIX #2: Tue Aug 28 09:39:12 PDT 1984
Master source now lives here; freeze your 4.1c stuff now.
monet#
For those who are curious....
http://vpsland.superglobalmegacorp.com/install/simh/4.1c%20BSD.7z
When I boot V7 in SIMH (pdp11), I get a root shell and a root filesystem,
but... I see that /usr/bin is on root's default PATH, but I have no
/usr/bin directory. Is there some way I could get a /usr/bin with
additional executables, to get the full flavor of V7?
By way of introduction, I first started with *ix on an AT&T 3Bmumble, and
started really getting into it with SunOS 4.1.1. I've recently become
interested in trying a large number of different *ix's - I guess it was the
ease with which VirtualBox allowed many of those, and then seeing Nordier's
V7 port to x86 got me curious about trying some really old versions - he
mentioned that there was a pdp11 emulator available...
> Date: Wed, 3 Aug 2011 20:35:15 -0700
> From: Larry McVoy <lm(a)bitmover.com>
> To: Dan Stromberg <drsalists(a)gmail.com>
> Cc: tuhs(a)minnie.tuhs.org
> Subject: Re: [TUHS] /usr/bin on V7?
>
>> By way of introduction, I first started with *ix on an AT&T 3Bmumble, and
>> started really getting into it with SunOS 4.1.1.
>
> SunOS 4.1.1, ah, sweet memories. I and a bunch of my friends worked on
> that one. Guy Harris, even though he had left for Auspex, would come back
> to building 5 at Sun around 5:30, bang on the door, John Pope or I or one
> of the other kernel guys who worked into the night, would let him in and
> give him a place to work, and for the next few hours you'd hear "Jesus,
> they still haven't fixed this?" and some fix would get pushed in.
>
> That was how much we loved SunOS. Solaris? Not so much. We put in tons
> of effort to make SunOS good and it was a very pleasant version of Unix.
:-)
if you haven't yet, check out tme sometime:
http://people.csail.mit.edu/fredette/tme/
On Wed, Aug 3, 2011 at 8:24 PM, Michael Davidson <m_d(a)pacbell.net> wrote:
> You probably don't have /usr/bin because you haven't mounted /usr yet.
>
That's a good hypothesis, especially given the info I presented, but I do
have -some- things under /usr, and if I manually rerun sh -x /etc/rc in
multiuser, I get an error about /usr already being mounted.
> On V7 as best I can remember. /usr was always a mounted filesystem.
>
> So, somewhere in your V7 image there should be a disk image for /usr that
> can be hooked up to an appropriate device under SIMH and then mounted.
> Actually, it might already be there if your disk image is the entire device
> and not just the root filesystem - if you can figure out what your root
> device is then I would expect /usr to be on the same major device number but
> with aminor device # of 2 (root being 0 and swap being 1).
>
I'm thinking /usr is /dev/rp3, because my /etc/rc looks like:
# cat /etc/rc
PATH=/bin:/usr/bin
echo "Restricted rights: Use, duplication, or disclosure
is subject to restrictions stated in your contract with
Western Electric Company, Inc." >/dev/console
rm /etc/mtab
cat /dev/null >/etc/utmp
/etc/mount /dev/rp3 /usr
rm -f /usr/spool/lpd/lock
: /etc/accton /usr/adm/acct
rm -f /usr/tmp/*
rm -f /tmp/*
/etc/update
date >/dev/console
/etc/cron
> Actually if you just take the system multi-user it might even do it for
> you.
This does seem to at least try to mount /usr for me - hitting ctrl-d at the
initial singleuser #, that is.
Interestingly though, it seems that the number of directories in /usr is the
same on first boot into single user, as after /etc/rc has run as part of
entering multiuser, so perhaps my root filesystem has things in /usr that
would normally be obscured by a /usr mount. Also, /etc/mtab seems untouched
(in fact, it's nonexistent) after entering multiuser, and the output of
/etc/mount continues to be nothing.
touch /t does create a file named t in the root directory, so it's not
something about the root filesystem being readonly.
I'm puzzled. And yet, I'm enjoying it. :)
Any suggestions?
> --- On *Wed, 8/3/11, Dan Stromberg <drsalists(a)gmail.com>* wrote:
>
>
> From: Dan Stromberg <drsalists(a)gmail.com>
> Subject: [TUHS] /usr/bin on V7?
> To: tuhs(a)minnie.tuhs.org
> Date: Wednesday, August 3, 2011, 7:53 PM
>
>
>
> When I boot V7 in SIMH (pdp11), I get a root shell and a root filesystem,
> but... I see that /usr/bin is on root's default PATH, but I have no
> /usr/bin directory. Is there some way I could get a /usr/bin with
> additional executables, to get the full flavor of V7?
>
> By way of introduction, I first started with *ix on an AT&T 3Bmumble, and
> started really getting into it with SunOS 4.1.1. I've recently become
> interested in trying a large number of different *ix's - I guess it was the
> ease with which VirtualBox allowed many of those, and then seeing Nordier's
> V7 port to x86 got me curious about trying some really old versions - he
> mentioned that there was a pdp11 emulator available...
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> TUHS mailing list
> TUHS(a)minnie.tuhs.org <http://mc/compose?to=TUHS@minnie.tuhs.org>
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
What type of licensing agreements (maybe informal) were used for the
early INGRES tape distributions? I am trying to see if they were an
example for BSD or how compared with early BSD.
The BSD-style licenses were not introduced until 1987 and later
(starting in but not completed in 4.3BSD-Tahoe). But various earlier BSD
(distribution) components did have open source licenses long before that
-- such as Eric Allman's trek (circa 1977) in 1BSD and MIT's X
components (1985) shipped with 4.3BSD.
The COPYRIGHT for INGRES 6.3/-1 (February 1, 1981) source shipped with
2.79BSD (Febuary 1981) indicated it was not open source: "... may not be
reproduced or disclosed without the prior written permission of the
owner."
My BSD history book in progress has at least 15+ pages of examples and
commentary and interview quotes about the history of proprietary and
open source licensing in early BSDs. I also plan to research the
history of licensing for W and early X.
Hi Warren.
Here's your answer. :-)
Arnold
> Date: Thu, 28 Jul 2011 12:39:24 -0400 (EDT)
> From: Brian Kernighan <bwk(a)CS.Princeton.EDU>
> To: Aharon Robbins <arnold(a)skeeve.com>
> Subject: Re: can you help warren w/this?
>
> well, he only has one child; that i know for sure. can't vouch for
> the quote, however; i have not heard it before.
>
> On Thu, 28 Jul 2011, Aharon Robbins wrote:
>
> > Hi. Warren runs The Unix Historical Society and is working on a paper.
> > Can you help him with this?
> >
> > Thanks,
> >
> > Arnold
> >
> >> Date: Thu, 28 Jul 2011 21:31:09 +1000
> >> From: Warren Toomey <wkt(a)tuhs.org>
> >> To: tuhs(a)tuhs.org
> >> Subject: [TUHS] ken: # of children?
> >>
> >> All, apologies for these seemingly random questions. How many children does
> >> Ken Thompson have? I want to use the phrase that Unix was "Ken's other child",
> >> but it would be inaccurate if he had several real children.
> >>
> >> Thanks,
> >> Warren
> >> _______________________________________________
> >> TUHS mailing list
> >> TUHS(a)minnie.tuhs.org
> >> https://minnie.tuhs.org/mailman/listinfo/tuhs
All, apologies for these seemingly random questions. How many children does
Ken Thompson have? I want to use the phrase that Unix was "Ken's other child",
but it would be inaccurate if he had several real children.
Thanks,
Warren
All, thanks for the help with that image of Ken and Dennis at the 11/20
console. Now I'm after a reference/citation to a great quote attributed to
Henry Spencer:
Those who don't understand Unix are condemned to reinvent it, poorly.
Any ideas if/when Henry said this and where: date, first time it appeared
in print etc.
While we are at it, are there any other good Unix quotes that spring to mind?
Thanks,
Warren
I went to Dennis' home page this morning to find something, and it seems
to be gone. The URL I'm using is http://cm.bell-labs.com/cm/cs/who/dmr/
Does anybody know if it's moved or, if not, who to contact to fix it?
I'm actually after the hi-res version of the photo with dmr and ken
at the PDP-11/20 console. I think I have a copy cached away. If not, does
anybody else have a copy?
Cheers,
Warren
Warren:
I went to Dennis' home page this morning to find something, and it seems
to be gone. The URL I'm using is http://cm.bell-labs.com/cm/cs/who/dmr/
=======
Looks like there has been substantial reorganization of
the company's web pages, doubtless to reflect reorganization
of the company itself.
I dug around to see where personal web pages seem to be now,
and tried some obvious guesses, and still couldn't find Dennis's
stuff.
I've sent a query to someone on the inside; I'll report back
if I find the answer.
It might be worth trying the Wayback Machine in the mean time.
Norman Wilson
Toronto ON
> On Wed, 2011-07-27 at 08:53 +1000, Warren Toomey wrote:
> > I'm actually after the hi-res version of the photo with dmr and ken
> > at the PDP-11/20 console.
On Wed, Jul 27, 2011 at 01:07:29AM +0200, Hellwig Geisse wrote:
> I don't know if this is the resolution you are looking for:
> http://www.psych.usyd.edu.au/pdp-11/Images/ken-den.jpeg
No, there's a huge one around, something like 4000x3000 pixels.
Also, Dennis is the bearded one standing, and Ken is the beardless one
sitting, to answer Jason's question.
Cheers,
Warren
Hi,
I'm currently reading J. Lion's commentary of Unix Code Level Six. It
is the most useful commentary to operating system kernel I have ever
read.
It would be really useful to also have the source code of SVR4 kernel
for Intel x86. Does anyone have that?
> To call this joint is complete nonsense. Sun was in a cash bind, AT&T
> wanted to make SVR4 the main Unix platform and SunOS was winning. The
> story I heard, not widely known, is that AT&T bought a big pile of Sun
> stock at 35% over market - in return for which Sun had to dump their BSD
> based SunOS and go to SVR4.
>
> Biggest mistake Sun ever made in my opinion.
"Sun has helped spark a major controversy within the UNIX community
that may have split it into different directions.
The controversy began to heat up in October 1987, when AT&T announced
that it would license Sun's SPARC architecture as the basis for AT&T
computer systems. Furthermore, said AT&T, it was going to collaborate
with Sun to develop a UNIX "standard" that would eliminate
deficiencies in the operating system--such as lack of features for
commercial applications--and be compatible at the binary level across
the entire SPARC architecture.
Not surprisingly, other companies in the UNIX Community smelled
incipient monopolistic practices that would give AT&T and Sun an
unqualified advantage in the UNIX market. These moves would
effectively make the Sun/AT&T-developed System V and SPARC proprietary
standards controlled by the two companies. This perception was
bolstered in January 1988, when AT&T announced that it had agreed to
purchase 20 percent of Sun by buying shares, in amounts and at times
determined by Sun, at 25 percent above current market value."
[Sunburst: The Ascent of Sun Microsystems, p. 112-113]
> Contrary to a lot of the distant opinions here,
> SVr4 was actually a joint project between USL
> (the AT&T commercial-UNIX organization) and Sun.
> The intent was to bring together the two different
> commercial-UNIX cults (what Stu Feldman once referred
> to as Sunni and Shiite UNIX).
>
> I was at Bell Labs while this was going on, but
> well off to the side of the effort, in a research
> group where we tended (foolishly) to look down
> our noses a bit at the whole thing. I do know that
> there were a lot of ruffled feathers within USL
> about the allegedly overbearing Sun guys, and it
> wouldn't surprise me a bit to hear that there
> were similar feelings going the other way. On
> the other hand there were some pretty smart
> people involved at a technical level on all
> sides.
>
> Certainly it wasn't a one-way street, with BSD-isms
> being injected into a USG system or vice versa.
>
> Norman Wilson
> Toronto ON
Thanks, Norman. This clarify a lot my confusion about SysV.
I'm reading the J. Lions Commentary to V6 UNIX, the ancestor of all
UNIXes, including SysV (if I understood correctly). The last Research
Unix release was Tenth Edition Unix. Is the source code of
releases 8, 9 and 10 available? Are there other commentaries of ancient
Research Unixes, like Lions book?
Thanks,
--Michele
P.S. to Cyrille: Again, my apologies for the confusion. I realized my
mistake just after I sent the mail. I'm really sorry!
Mahlzeit,
some years after losing my MO drive and unable to access my
PUPS copy I would like to redownload it before it perhaps
vanishes. I have forgotten my access data. I believe it was
with rsync. And with all the borken links on the website and
the time going by I am not sure what the current status is.
Is Warren still here? His last posting was from April last year.
Mahlzeit,
Matthias
--
kitty mea felis duodeviginti annos nata requiescat in pace.
laeta gaudiumque meum erat. desiderio eius angor.
Contrary to a lot of the distant opinions here,
SVr4 was actually a joint project between USL
(the AT&T commercial-UNIX organization) and Sun.
The intent was to bring together the two different
commercial-UNIX cults (what Stu Feldman once referred
to as Sunni and Shiite UNIX).
I was at Bell Labs while this was going on, but
well off to the side of the effort, in a research
group where we tended (foolishly) to look down
our noses a bit at the whole thing. I do know that
there were a lot of ruffled feathers within USL
about the allegedly overbearing Sun guys, and it
wouldn't surprise me a bit to hear that there
were similar feelings going the other way. On
the other hand there were some pretty smart
people involved at a technical level on all
sides.
Certainly it wasn't a one-way street, with BSD-isms
being injected into a USG system or vice versa.
Norman Wilson
Toronto ON
On Mon, 2011-07-11 at 23:25 +0200, Cyrille Lefevre wrote:
> Le 11/07/2011 12:29, Michele Ghisolfo a écrit :
> > Hi,
> >
> > I'm currently reading J. Lion's commentary of Unix Code Level Six. It
> > is the most useful commentary to operating system kernel I have ever
> > read.
> >
> > It would be really useful to also have the source code of SVR4 kernel
> > for Intel x86. Does anyone have that?
>
> Hi,
>
> Try this :
>
> ed2k://|file|usl-4x-source.emulecollection|84|A15FBAA27D00C2C4147EA58EAB629B1C|h=VHD37XHFUXWKQJMQUWGNXZHD6NCQONEQ|/
>
> Regards,
>
> Cyrille Lefevre
I downloaded it and I only got a 4k file named
"usl-4x-source.emulecollection". Doesn't seem a tar. I'm using aMule
client and I put the address on the "ed2k Link" field.
What I am doing wrong?
There is a somewhat modern port of V6 to the 286, which is in the archive (http://minnie.tuhs.org/Archive/Other/V6on286/) There is also a modern x86 port of V7 available at http://www.nordier.com/v7x86/ This one is more interesting as it aims to run in modern machines and includes a bootable CD image.
Best regards,
Sergio Aguayo
----- Mensaje original -----
De: "Michele Ghisolfo" <ghisolfo.m(a)gmail.com>
Para: "Sergio Aguayo" <sergioag(a)qmailhosting.net>
Enviados: Lunes, 11 de Julio 2011 7:02:37
Asunto: Re: [TUHS] SVR4 x86 -- Sources
On Mon, 2011-07-11 at 08:50 -0400, Sergio Aguayo wrote:
> If you're reading the Lion's book, better get Unix V6 from the archive. SVR4 is quite different in many aspects.
>
> Best regards,
>
> Sergio Aguayo
I got them, but they work on PDP-11. I'd like to see an version of Unix
working on Intel x86. As far as I know, SVR4 was the first Unix working
on this architecture.
If I recall correctly Unix V6 was only ported on Interdata 7/32
computers. I'd like to get the sources of a small Unix kernel working
on x86.
Has anyone ported Unix V6 on x86?
Thanks for your replies,
-- Michele
All, several years back Mike Mahoney interviewed several of the original
Unix players for a Unix oral history. The transcripts are at:
http://www.princeton.edu/~hos/mike/transcripts/
At the time AT&T were going to release these in audio format, but it seems
to have fizzled out. Does anybody know if the audio interviews ever got out?
The transcripts are fine, but in places they show "(unclear)" when a word
or name is used, and of course it's exactly that name you want to find out.
Many thanks for any leads.
Warren
> All, IEEE Spectrum have asked me to write a paper on Unix to celebrate the
> 40th anniversary of the release of 1st Edition in November 1971. I'm after
> ideas & suggestions!
of course this quote is always good for a chuckle:
Ken Thompson was once asked what he would do differently if he were
redesigning the UNIX system. His reply: "I'd spell creat with an e."
[http://en.wikiquote.org/wiki/Kenneth_Thompson]
and I always liked this quote from Linus Torvalds:
On Tue, 22 Jun 1999, Rik van Riel wrote:
> The real issue here is paradigms. The classical "everything's
> a file" broke down with the advent of networking, sockets and
> non-blocking reads. At the moment the file paradigm is so much
> out of touch with computational reality that web servers need
> to fork for each client and people are crying out for asynchronous
> sendfile and other weird interfaces.
Sure. But I think it's still a valid paradigm to consider "everything is a
stream of bytes". And that's _really_ what the UNIX paradigm has been from
the first: the whole notion of pipes etc is not all that different from
networking.
[http://groups.google.com/group/fa.linux.kernel/msg/7bcbbfeaea2b93c9?hl=en&d…]
> I'm also trying to chase down some quotes; my memory seems to be failing me
> but I'm sure I've seen these somewhere:
ugh..my memory is failing too at the moment. I'm sure I once read a
nice rant of sorts about how Unix has proven to be of sound design
that has adapted well to changes in the computing landscape...
Anyone remember picasso, a vector graphics GUI app
that generated pic(1) source?
I know nothing of it, anyone got a screenshot even?
is the source available?
was its frontend X11 or blit terminal?
Was it related to the blit cip and xcip tools
or are they a different genus?
Thanks for any info.
-Steve
I figured you guys may get a kick out of this...
You can download a 'ready to run' version here:
http://code.google.com/p/vak-opensource/downloads/detail?name=dvk-demos.zip…
Included is a modified version of SIMH's PDP-11 emulator with a new
disk controller. Binaries are included for both Linux & Win32.
Source to his additions are here:
http://vak-opensource.googlecode.com/svn/trunk/bk/simh-dvk/
And the source to version 2.2 of Demos has been provided here:
ftp://ftp.besm6.org/pub/archives/d22.tar.gz
Oh control+n lets you input in russian, and control+o lets you input in english.
>From what I understand DEMOS is derived from 2.9 BSD..
I don't speak Russian and what I end up doing is cutting & pasting
into google translate... For some really bizarre translations.
Demos is Copyright 1991 by Research Institute "Scientific Centre", lab 462/2.
I thought you guys may enjoy this...
http://aiju.de/code/pdp11/
It's a PDP-11 with a teletype console, and a RK05 with Unix v6.
Because browsers are weird, here is some of the keycommands...
DEL is the interrupt key (^C on modern *nix), Pause the quit key (^\
or ^L) and PrtScr is EOF (^D).
Jason
Now that Novell has definitively been found by the courts to own the
Unix copyrights AND decided not to sell them in their latest batch of
financial flailing about, I'm wondering what they're going to do about
the Ancient Unix license. While they've promised not to sue anybody
about Unix, I'm wondering if they'll ever officially endorse the
Ancient Unix 4-clause license or perhaps even switch it to something a
little less awkward like a 3-clause BSD clone or the MIT license.
Also, I wonder if perhaps they might be convinced to expand the
license to cover things like System III or maybe even some early
versions of System V. How might one go about making these inquiries?
Hi.
> > Hi. Does anyone remember for sure if "new" awk shipped with System V
> > Release 3.1 or 3.2? I know it wasn't 3.0.
>
> Hi,
>
> http://www.levenez.com/lang/ says 1978 for oawk and 1985 for nawk.
New awk existed inside the Research group for some time before it
filtered out through System V. It was even available separately,
directly from them, to educational institutions. Circa 1986 I got
a copy that way when I worked at the Emory University computing center.
> regarding http://www.levenez.com/unix/, 1978 is between v6 and v7,
> and 1985 is between SVr2 and SVr3.0.
True but not relevant; new awk was released with System V at either
3.1 or 3.2; I'm leaning towards 3.1 since that is what I wrote way back
when in the gawk manual when I knew for sure. :-)
Unless anyone can check the actual sources, I think we should declare
this closed... Thanks to everyone for the feedback.
Arnold
Jaap Akkerhuis wrote:
> Officially it was written by Aho Weinberger Kernighan but
> I suspect Brian did most of the actual coding.
quote of Aho from an interview ---
"We [Aho and Kernighan] had created a grammatical specification for AWK but
hadn't yet created the full run-time environment. Weinberger came along
and said 'hey, this looks like a language I could use myself', and within
a week he created a working run time for AWK."
see http://www.computerworld.com.au/article/216844/a-z_programming_languages_aw…
I know for sure that in 1988's svr3.2 the "awk" command was the 1988 version
and the "oawk" command was the version from 1979.
In svr3.0 the "awk" command was the old and we'd get the new one
from Holmdel's unix tools distribution group (called USTOP) and
install it as "nawk"
I think you could get the new one in stock svr3.1 but cannot
remember it it was provide as "awk" or "nawk."
> Hi. Does anyone remember for sure if "new" awk shipped with System V
> Release 3.1 or 3.2? I know it wasn't 3.0.
>
> Thanks!
>
> Arnold Robbins
Regardless of its technical merits (and I suspect that the implementation may have been pretty bad) RFS was doomed by AT&T's licensing policies and general ineptitude at marketing UNIX. Similarly the widespread adoption of NFS was driven by the fact that Sun made it a de facto standard.
On Thu Mar 31st, 2011 7:51 PM PDT Nick Downing wrote:
>I also looked up EDOTDOT and found reference to RFS but not much info about
>it. Why was it not used? Not reliable enough? I have often thought that
>the stateless, idempotent NFS protocol leaves a lot to be desired due to its
>inability to implement unix semantics (as discussed in the wikipedia stub
>article on RFS), has this been improved with NFS4? Should RFS be revived
>and used? Some of its features sounded quite attractive (location
>transparency, etc). It does appear to have the ability to execute a program
>remotely?? What happens with regard to PIDs, home directory etc in this
>case? Does anyone know?
>cheers, Nick
>
>On Fri, Apr 1, 2011 at 1:23 PM, Michael Davidson <
>michael_davidson(a)pacbell.net> wrote:
>
>> --- On *Thu, 3/31/11, Random832 <random832(a)fastmail.us>* wrote:
>>
>>
>> EDOTDOT caught my eye for some reason - maybe because it's the only one
>> you attributed to linux in a long list of SVr1 ones... what were 72
>> through 76 in SVR1?
>>
>>
>> As the comment indicates, EDOTDOT came from "RFS" - the almost never used
>> "remote file system" that was (optionally, I think) part of System V Release
>> 3.
>>
>> As best I can recall, that is also where several of the other error numbers
>> in the 72 - 79 range probably came from.
>>
>> Michael Davidson
>>
>> _______________________________________________
>> TUHS mailing list
>> TUHS(a)minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>>
Hi all,
PJ from groklaw.net has asked me to trace the origin of
the errno names and values in recent versions of Linux. Attached
is where I am up to. The columns are:
- errno name
- errno value in Linux, and its original value if different
- system which originally defined it
- release date of that system
There are a few errno names which I don't think I have the
correct original system:
EDOTDOT, ENOMEDIUM, EMEDIUMTYPE, ECANCELED,
ENOKEY, EKEYEXPIRED, EKEYREVOKED, EKEYREJECTED,
EOWNERDEAD, ENOTRECOVERABLE, ERFKILL
Can anybody shed some light on these ones, that would be
great, especially if they come from SysV or Unixware.
Also, if you can spot any other mistakes, let me know!
Many thanks in advance,
Warren
Hi all, best wishes for 2011. I had an e-mail from Sven Mascheck asking about
the history of #! interpretation in System V. I couldn't find any #!
code in the kernels before SysVR4. However, I thought I'd pass the
query onto the TUHS list, in case others can shed some light on the question.
Did SysV systems before r4 do #! interpretation, and if so where was it done:
kernel, library, shell? Any code references, e.g. function names etc.?
Many thanks,
Warren
My interest is tweeked, do you still have the source
for the paper on your editor and perhaps the plan9 source?
I never moved across to acme, I am still a sam addict, but
I am always interested in new ideas.
The Only editors I ever used on Edition-VII where vi and le,
and le I only brushed up against.
-Steve
Warren Toomey said:
> I first encountered Unix in 1982 at a summer school held by the University
> of Wollongong in Australia. They had an modeless text editor installed,
> and I have never been able to determine if this was a homegrown editor, or
> an editor which was more widely distributed.
The editor was homegrown in Wollongong in 1981, as a late addition to the
Interdata Unix port. I wrote it in response to an elegant and concise
formal mathematical specification of a "display-oriented text editor"
written by Bernard Sufrin of Oxford University's Programming Research
Group. Bernard's specification was essentially an abstract model of an
existing minimalist (and modeless) screen editor 'ded' developed by his
colleague Richard Bornat at Queen Mary College in London. I've never seen
'ded' itself, but I expect that if you tried both editors you would see a
close family resemblance.
The Wollongong editor was not widely disseminated. I don't think it got
into any official Unix distribution except perhaps for Edition VII - its
austere minimalism could not compete with the dazzling complexity of emacs
or vi. I did license it to Interdata (later aka Perkin-Elmer) for use on
their own OS/32 operating system, where it was called MEDIT. I carried on
for many years using it myself and porting it to various flavours of Unix,
Minix, even MS/DOS, and most recently Plan 9. It was only after giving up
Unix for Plan 9 that I finally switched to using Rob Pike's 'acme', which
is, in its way, even more elegantly minimal.
-- Richard Miller
I thought I'd pop in another question here, given the good response we had
with #!
I first encountered Unix in 1982 at a summer school held by the University
of Wollongong in Australia. They had an modeless text editor installed,
and I have never been able to determine if this was a homegrown editor, or
an editor which was more widely distributed.
I've attached the first 2 pages of the editor's tutorial; the rest are
temporarily at http://minnie.tuhs.org/Z2/WollongongEdit/
Does anybody recognise this at all?
Many thanks in advance,
Warren
Hello,
Looking for an old version of SQR (Oracle's reporting program) -
3.0.13/.0.15 for >= SunOs5, a.k.a Solaris (>=2.x).
We've got SQR 3.0.13 for SunOS 4, but of course it is not compatible
with our Solaris Oracle client (which isn't sunos4, but sunos 5.8).
According to some records and posts online, there is an 3.0.13 for
Solaris :) just need to find a copy
We've already posted a request in SQRUG (SQR User Group) mailing list
and of course contacted our local Oracle provider (who gave us the
SunOS4 version).
Needles to say, we're in contract with Oracle, once we get a correct
version of the program and according to a successful P.O.C, fully
payed licenses will be purchased.
Check with your ex MITI/Sqribe, Oracle contacts.
Cash prize - $1,000 to finder.
Thanks a lot,
A', D' and friends at the DGUX Project
I asked a while back if anyone had any NetBSD 0.8 or 0.9 archives.. I
thought I'd let the list know that I did manage to find NetBSD 0.9, and
using VMWare I've managed to revive it into something that Qemu can run.
If anyone has VMWare and wants to stroll down memory lane, I've uploaded the
install diskettes here:
http://sourceforge.net/projects/bsd42/files/Install%20tapes/NetBSD/0.9/NetB…
And I've setup an archive with Qemu & NetBSD all ready to go here:
http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
If anyone wants to use their own qemu for their own platform, I've had to
modify the hw/pc.c and remove the NE2000 definition of 0x300,9 as irq 9 is
in use somewhere else in the emulator and it won't allow any sharing on
Irq9.. (Wasn't IRQ 9 shared anyways with the cascade controller???)
At any rate, I built irc, lynx & bzip2 on there, and they seem to function
just fine.
Again if anyone has any lead on NetBSD 0.8 that'd be great, I'd like to save
these from the digitial dumpster....
For anyone that is even remotely interested, I found a way to 'cheat'
the install process, and I've gotten 386 BSD 0.0 to install under
bochs. Qemu is convinced it can't read the disk for a kernel....
But it does work, well as well as 386BSD 0.0 can work.
http://vpsland.superglobalmegacorp.com/install/386BSD/386bsd-0.0/bochs/
I'll try to clean up what I can later.......
well I think I've flogged this dead horse enough... :)
Basically I've mashed in as much as I could figure out, and got the
majority of a make install (build world?) on this thing to work.. I
still don't know where /usr/bin/install comes from as I couldn't
readily identify the source in NetBSD 0.9 or any of the 386 BSD's...
I'm probably looking in the wrong place or maybe it's just from Net/2?
I didn't spend too long trying to work out stuff like that.
If anyone wants, it's in a Qemu runnable image here:
http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
It is just under 50MB, which I guess isn't bad since it's source and binaries..
I've manually copied over a few things from etc, and it seems that
NetBSD 0.8 still identifies itself as 386BSD.. did anyone run 0.8 and
remember? The CVS history on /etc/motd seems to have the 0.8 still
reporting as 386BSD which didn't change until 0.9 ...
I had to use a good chunk of 386 BSD pl 23 to fill in the missing
parts from the CVS archive of the kernel, but I got it to build!
>From the NetBSD 0.8 release/announcement it doe say:
The source for NetBSD is derived from 386BSD 0.1, patched
with the 0.2.2 patch kit. In addition, many programs in
UCB's second BSD Networking Software Release which were
missing from 386BSD have been integrated into NetBSD, some
of the changes from the upcoming 0.2.3 patch kit have been
included, and many local additions and bug fixes have
been performed.
So I'm assuming this wouldn't be too far off then.
So for the curious, here is a dmesg:
386BSD 0.1 (GENERICISA) #2: Sun Dec 5 13:30:14 PST 2010
root@branch.oldbsd.org:/usr/src/sys.386bsd/arch/compile/J
real mem = 67104768
avail mem = 64663552
pc0 at 0x60-0x6f irq 1 on isa
pc0: color
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: <QEMU HARDDISK>
wd0 at wdc0 slave 0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
ne0 at 0x320 irq 10 on isa
ethernet address 52:54:00:12:34:56
npx0 at 0xf0 irq 13 on isa
wdc0: extra interrupt
wdc0: extra interrupt
ISA strayintr 4004ff
ISA strayintr 4004ff
ISA strayintr 4004ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
ISA strayintr 2ff
Too many ISA strayintr not logging any more
I'm not sure if the 386BSD name is hanging around because of all the
386 BSD files I included of if it wasn't renamed in NetBSD 0.8 ... I
can give anyone the list of files, steps etc, or it may be easier to
just download the merged & built sources here:
http://vpsland.superglobalmegacorp.com/install/NetBSD/NetBSD-0.8/Resurrecti…
Thanks to everyone for providing the CVS and a few hints on what was
going on with it..!
I hate to post this publicly, but Natalia's email address that I have
is also on the domain... Anyways it's expired, you may want to renew
clanuia.com.
I'm sorry for posting this publicly, wasting peoples time bandwidth etc etc.....
Jason
On 12/03/10 03:00, "Jeremy C. Reed"<reed(a)reedmedia.net> wrote:
>> > Maybe I'm totally dense, or something...?
>> >
>> > cvs -P :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -R netbsd-0-8 src
>
> cvs -d :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -r netbsd-0-9 \
> src/sys/kern/kern_exit.c
>
> (note I changed -P and -R to -d and -r respectively)
Wow. Did I really write that? :-)
Thanks for the correction. I have no excuse.
> cat src/sys/kern/kern_exit.c
Anything in particular we should look for?
Johnny
On 11/17/10 03:00, Jason Stevens<neozeed(a)gmail.com> wrote:
> I don't suppose anyone has this kicking around, or any pre-release vax
> images of netbsd?
>
> I did manage to get 1.2 installed on SIMH for what it's worth....
Btw, fwiw, I'm pretty sure VAX only started working with NetBSD 0.9, and
the first machine supported was the VAX-11/750.
Johnny
On 12/02/10 03:00, Jason Stevens<neozeed(a)gmail.com> wrote:
> I asked a while back if anyone had any NetBSD 0.8 or 0.9 archives.. I
> thought I'd let the list know that I did manage to find NetBSD 0.9, and
> using VMWare I've managed to revive it into something that Qemu can run.
>
> If anyone has VMWare and wants to stroll down memory lane, I've uploaded the
> install diskettes here:
> http://sourceforge.net/projects/bsd42/files/Install%20tapes/NetBSD/0.9/NetB…
>
> And I've setup an archive with Qemu& NetBSD all ready to go here:
> http://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Net…
>
> If anyone wants to use their own qemu for their own platform, I've had to
> modify the hw/pc.c and remove the NE2000 definition of 0x300,9 as irq 9 is
> in use somewhere else in the emulator and it won't allow any sharing on
> Irq9.. (Wasn't IRQ 9 shared anyways with the cascade controller???)
>
> At any rate, I built irc, lynx& bzip2 on there, and they seem to function
> just fine.
>
> Again if anyone has any lead on NetBSD 0.8 that'd be great, I'd like to save
> these from the digitial dumpster....
Maybe I'm totally dense, or something...?
cvs -P :pserver:anoncvs@anoncvs.netbsd.org:/cvsroot co -R netbsd-0-8 src
or substitute the tag netbsd-0-9 or netbsd-0-9-base if you need those
revisions. Nothing is going to disappear into a digital dumpster when
you have revision control systems...
(There are bunch of more tags related to NetBSD 0.9 as well, if you want
to know, and you can get at any other version you want as well, just as
easily.)
If you want binaries and not just sources, then it might be a bit more
tricky. But since you can build the system from the sources, I can't see
that this should be a big hurdle.
Johnny
Just to loop things around a bit:
Some of the larger VAXes used small PDP-11s (and their
bastard offspring) as console processors.
This started with the very first VAX, the 11/780, which
used an 11/23 as a console. The console ran a stripped-down
system, possibly based on RT-11 or RSX-11, I forget (and
am typing this on a train in the Outer Mongolia part of
Texas where it's hard to look up references).
I don't know the whole list of what was used as a console
for different VAXes, but I do remember that the Nautilus
series (8500-8550-8700-8800) used either a Pro/350 or a
Pro/380, running P/OS, which was slightly more satisfactory
than the rude English non-computer expansion of PoS might
imply, but only slightly. Especially for those of us who
wrote code to fit into UNIX on the VAX and talk to the
console processor.
I also vaguely remember that although Digital were
reluctant (at least early on) to make an RT-11 that would
run on the Pro-series systems, someone made a UNIX for
those systems.
I never knew a lot about this stuff and have forgotten much
of what I did know, but perhaps my words will trigger others'
memories.
Norman Wilson
Toronto ON
I don't suppose anyone has this kicking around, or any pre-release vax
images of netbsd?
I did manage to get 1.2 installed on SIMH for what it's worth....
Jason
How much does an old pdp-11 type system cost these
days (ie. a pdp-11/40 with disks and terminal capable
of running something like 1st, 6th or 7th ed)?
How much power do they take up to power on?
Whats maintenance like on those things?
I've always been curious.
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
I was wondering if anyone has ever been able to build and use BSD 1 on
Research Unix v7 (pdp-11)?
I've installed the Keith Bostic tape, and I've been fighting the floating
point and some other weird stuff....
I've configured my PDP-11 like this:
set cpu 11/70
set cpu 2M
set cpu idle
set rp0 rp06
att rp0 rp06-0.disk
att tm0 xx.tap
boot tm0
but I'm lost on the install guide, as it mentions for floating point...
Floating Point
UNIX only supports (and really expects to have) the
FP11-B/C floating point unit. For machines without this
hardware, there is a user subroutine available that will
catch illegal instruction traps and interpret floating point
operations. (See fptrap(3).) To install this subroutine in
the library, change to /usr/src/libfpsim and execute the
shell files
compall
mklib
The system as delivered does not have this code included in
any command, although the operating system adapts automati-
cally to the presence or absence of the FP11.
Next, a floating-point version of the C compiler in
/usr/src/cmd/c should be compiled using the commands:
cd /usr/src/cmd/c
make fc1
mv fc1 /lib/fc1
This allows programs with floating point constants to be
compiled. To compile floating point programs use the `-f'
flag to cc(1). This flag ensures that the floating point
interpreter is loaded with the program and that the floating
point version of `cc' is used.
The library doesn't actually build a libfpsim.a but rather it hooks into
libc? And the fc1 command won't build as there is no libfpsim....
Maybe I'm doing something obviously wrong?
Any hint would be appreciated.
Jason
Anyone have a scanned (or text) copy of the 4.3BSD License Agreement
from 1986 they can send me?
Much of the code shipped in 4.3BSD says ``The Berkeley software License
Agreement specifies the terms and conditions for redistribution.'' As
far as I can see, it is not included in the source, nor in the Univ. of
Wisconsin fork, and not in Tahoe release.
I do have the agreement between UC and AT&T and copies of some of their
letters during that period clarifying the licensing.
The Net1 release included the license agreement in the source files. But
does anyone have a separate license agreement for Net1 too? (The README
seems to imply there was a separate license agreement too.)
I am also looking for addendum for Tahoe and the addendum for Reno. And
was there any agreement to sign for those who chose to pay for statement
that Net2 was freely redistributal (I guess that wouldn't make sense)?
Warren:
I thought the BSTJ went into 1984, as I have some references to 1984 issues,
e,g, The Evolution of UNIX System Performance. Bell System Technical Journal,
63(8):1791b1814, October 1984.
=======
The journal's name changed at the end of 1983, from Bell System Technical
Journal to AT&T Bell Laboratories Technical Journal, to reflect
divestiture.
There was indeed a late-1984 all-UNIX-papers issue of the BLTJ, but
technically (and journally) it was the BLTJ then, not the BSTJ.
I don't know whether there are issues of copyright-ownership or
the like over the post-divestiture journal (does it belong to
Bell Labs, now owned by Alcatel, or to AT&T, now owned by
Southern Bell?) that interfere with releasing the latter-day
journal.
Norman Wilson
Toronto ON
(actually passing through Davis CA on a train, but
who cares?)
A friend sent this to me. Both of these mailing lists are likely
to find this of interest. I have a paper copy of the 1978 BSTJ,
either the '82 or '83 issues, whichever one was devoted to Unix. :-)
Arnold
> Date: Mon, 8 Nov 2010 17:42:14 -0700 (MST)
> From: "Nelson H. F. Beebe" <beebe(a)math.utah.edu>
> To: fslc(a)fslc.usu.edu
> Cc: beebe(a)math.utah.edu
> Subject: [fslc] historical papers on Unix now online
>
> The Bell System Technical Journal from 1922 to 1983 is now online at
>
> http://bstj.bell-labs.com/
>
> with free downloadable PDFs of all articles.
>
> I've downloaded all of the HTML files, and found that just three of
> them contain mention of Unix:
>
> BSTJ.1978.5706-2.html
> BSTJ.1982.6109.html
> BSTJ.1983.6206.html
>
> Some of those important early articles that document the development
> of Unix have also been reprinted in these books:
>
> @String{pub-PH = "Pren{\-}tice-Hall"}
> @String{pub-PH:adr = "Upper Saddle River, NJ 07458, USA"}
>
> @Book{ATT:AUS86-1,
> author = "AT{\&T}",
> key = "ATT",
> title = "{AT}{\&T UNIX} System Readings and Applications",
> volume = "I",
> publisher = pub-PH,
> address = pub-PH:adr,
> pages = "xiv + 397",
> year = "1986",
> ISBN = "0-13-938532-0",
> ISBN-13 = "978-0-13-938532-2",
> LCCN = "QA76.76.O63 U553 1986",
> bibdate = "Sat Oct 28 08:25:56 2000",
> }
>
> @Book{ATT:AUS86-2,
> author = "AT{\&T}",
> key = "ATT",
> title = "{AT}{\&T UNIX} System Readings and Applications",
> volume = "II",
> publisher = pub-PH,
> address = pub-PH:adr,
> pages = "xii + 324",
> year = "1986",
> ISBN = "0-13-939845-7",
> ISBN-13 = "978-0-13-939845-2",
> LCCN = "QA76.76.O63 U553 1986",
> bibdate = "Sat Oct 28 08:25:58 2000",
> }
>
> -------------------------------------------------------------------------------
> - Nelson H. F. Beebe Tel: +1 801 581 5254 -
> - University of Utah FAX: +1 801 581 4148 -
> - Department of Mathematics, 110 LCB Internet e-mail: beebe(a)math.utah.edu -
> - 155 S 1400 E RM 233 beebe(a)acm.org beebe(a)computer.org -
> - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ -
> -------------------------------------------------------------------------------
>
I will be giving a lecture at NYCBSDCon on November 13 about my research
covering the history of Berkeley Unix and will highlight some of the
important events and key participants in BSD history.
http://www.nycbsdcon.org/2010/
I have done over 50 interviews with early participants, including during
the first Berkeley UNIX Software Tape, the Second Berkeley Software
Distribution, and vmunix period. (I still have many to do.)
On 10/20/10 04:00, Tim Newsham<newsham(a)lava.net> wrote:
> I'm playing with unix v6 right now. I don't see the "man"
> binary anywhere.. anyone know why?
>
> I have v6 installed from tape. The tape has images for three
> disks apparently, root, source and docs. The docs image has
> a man directory with the man pages in them. I don't see a
> man binary anywhere though, and I don't see the sources to
> man in the sources directory either.
>
> I checked the disk images available on the simh "kits" page.
> It has man pages in /mnt/man but no sources or binary.
> (by the way, this image is missing /usr/sys for some reason,
> which is why I am running an installation from tape).
>
> I also checked the
> PDP-11/Trees/V6 directory on TUHS and similarly dont see
> sources or binaries for man (though the man pages are present
> in /usr/man).
>
> There's even a /usr/man/man1/man.1, formatted online here:
> http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/I/man.html
>
> anyone know why the source and binary are missing from the
> distributions?
What "man" binary? You use cat... You have the man-pages, you have a
program (or several) to type files... Why would you need yet another
program to type files?
Johnny
I'm playing with unix v6 right now. I don't see the "man"
binary anywhere.. anyone know why?
I have v6 installed from tape. The tape has images for three
disks apparently, root, source and docs. The docs image has
a man directory with the man pages in them. I don't see a
man binary anywhere though, and I don't see the sources to
man in the sources directory either.
I checked the disk images available on the simh "kits" page.
It has man pages in /mnt/man but no sources or binary.
(by the way, this image is missing /usr/sys for some reason,
which is why I am running an installation from tape).
I also checked the
PDP-11/Trees/V6 directory on TUHS and similarly dont see
sources or binaries for man (though the man pages are present
in /usr/man).
There's even a /usr/man/man1/man.1, formatted online here:
http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/I/man.html
anyone know why the source and binary are missing from the
distributions?
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
hi everyone,
Just to let you all know that a few years ago I adapted the 2.11BSD
source so that it could be built on a modern system and transferred
across to the PDP-11. The changes are:
1. The PDP-11 assembler was written in assembler so made a
line-by-line translation into C code.
2. The C compiler required access to PDP-11 math e.g. for constant
folding, so I inserted some code from Bob Supnik's emulator in those
places.
3. Basically everything that runs from a makefile (e.g. "sh", "make",
"yacc", etc) has been upgraded to a more modern coding style with non
portable code fixed up, independence on type sizes, prototypes added,
etc, and the build system now generates two versions where
appropriate, one for running locally (compiled with gcc or whatever
your local compiler is) and one for inclusion in the distribution
(compiled with the PDP-11 cross toolchain).
4. I also fixed a number of "just plain bugs" that obviously had
remained undiscovered under PDP-11 conditions.
I used conditional compilation and macros where appropriate so as not
to break the PDP-11's ability to run the toolchain locally. I used a
binary comparison between the locally compiled build and the cross
compiled build to weed out bugs, and it did seem to be pretty robust
as I left it. The only reason I didn't make this work available
generally (apart from laziness), was that there's quite a few
experimental changes in addition to points 1-4, for example:
5. A reworking of the (existing) system that extracts strings and puts
them in the code segment (necessary to get the PDP-11 to run large
executables such as nethack). I can't really remember why I did this,
probably just to clean things up, but I don't think it's all that
essential so perhaps could be removed for the sake of minimal change.
6. Some changes to how "make" works, and to the Makefiles, intended to
clean things up, which in retrospect weren't essential and should be
removed (except for those changes necessary for point 3 above, need to
untangle it somehow). I didn't get around to converting all Makefiles
so there's probably a bit of inconsistency there. I might have broken
some things like "make tags" and "make depend", not sure.
7. Fortran stuff had to be disabled as the Fortran compiler is written
in assembly language (IIRC) and would probably be difficult to convert
into C (but I don't think this is a big deal).
If anybody volunteers to sift through the changes and sort out the
good from the dross then I will happily send the whole thing.
cheers, Nick
You've bested me there -- by a little. I only had the Sixth Edition on an 11/45. Now I could probably emulate that system on this iPhone, and it would run faster than the actual hardware.
Oh well, time to stop wallowing in nostalgia. ;-)
Sent from my iPhone
On Sep 28, 2010, at 9:42 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
> And besides, I've used V5 on a /40 :-)
>
> -- Dave, turning 58 next month
I do indeed.
At 10:02 AM 9/29/2010 -0400, Bill Pechter wrote:
>Anyone else here remember fansi-console's ansi emulator.
>
>Works great instead of ansi.sys and is a pretty good screen driver for dos.
>
>On Wed, Sep 29, 2010 at 5:24 AM, Johnny Billquist
><<mailto:bqt@softjar.se>bqt(a)softjar.se> wrote:
>Mark Tuson wrote:
>Hi everyone, this is my first message, after being on the mailing list for
>the best part of three years :)
>
>Though I might consider 2.11BSD, if that'll work on a machine with 24M of
>core, and if the escapes will display properly, because
>[24;1H[?1h=[;H[2J
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~[H
>
>is a little bit difficult to work with when I'm wanting to edit source code.
>
>
>2.11BSD won't make a difference. You'll see the same result. This is a
>problem because you are running under DOS. It is the DOS screen handler
>that needs to understand whatever codes are output by the programs running
>inside simh. In this case, the program inside simh thinks it is connected
>to a VT100 (or xterm, or something similar), and sends escape codes based
>on that. I don't know why it thinks so, but I suspect you told the system
>by setting the TERM variable. Please set it to something that matches
>reality, or else fix reality. :-)
>
> Johnny
>
>
>
>Anyone else here remember fansi-console's ansi emulator.
>
>Works great instead of ansi.sys and is a pretty good screen driver for dos.
>
><http://www.highbeam.com/doc/1G1-11953307.html>http://www.highbeam.com/doc/1G1-11953307.html
>
>Bill
>
>--
> d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
> <http://pechter-at-gmail.com>pechter-at-gmail.com
>_______________________________________________
>PUPS mailing list
>PUPS(a)minnie.tuhs.org
>https://minnie.tuhs.org/mailman/listinfo/pups
---
Jay R. Jaeger The Computer Collection
cube1(a)charter.net
> > There is close zero chance I'll ever use this stuff,
> > unless I retire
> > to teaching in which case I'll make people write
> > PDP-11 assembler.
>
> That seems a tad archaic. MIPS might be a better
> choice; it's 32-bit
> with 32 registers, and there are excellent simulators for
> it.
At my university there's a grad class that's ostensibly on reverse
engineering,but you can't really disassemble anything if you don't
learn assembler, so you learn it. The downside, I guess, is that
I've read a decent amount of x86 assembler, but written very little.
I don't think it's a bad way to learn, but of course, Larry was
talking about teaching a nice instruction set, and you
kind of lose that. But you get Windows DLL function calling
back as a booby prize.
John Finigan
Hi everyone, this is my first message, after being on the mailing list
for the best part of three years :)
I've a couple of [hopefully] simple questions about running Seventh
Edition UNIX on SIMH.
The first question is: how can I get the C compiler to work properly?
When I've tried to compile programs, I get 'cannot create temp' - here's
a full list of what's on the screen:
@boot
New Boot, known devices are hp ht rk rl rp tm vt
: rl(0,0)rl2unix
mem = 177856
# Thu Sep 22 07:50:47 EDT 1988
login: mark
$ ed
a
main() {
printf(" Hello.\n");
return; }
.
w a.c
46
q
$ cc a.c
cc: cannot create temp
$
Also, how can I get the backspace key to erase? I've done /stty erase
'^H'/ but I have to actually type <CTRL>+H to erase.
The other thing I want to ask about is: can I compile SIMH on DOS, so it
doesn't display any messages except those of the simulated software, and
so it ignores ^E?
I'm asking because I want v7 on an ancient laptop I've got lying around
- a 486 with 24M of core. v7x86 won't work on it, and I don't really
fancy putting Slack 3 back on it - if I'm going to go outdated, I might
as well go the whole hog and go /really/ outdated.
Though I might consider 2.11BSD, if that'll work on a machine with 24M
of core, and if the escapes will display properly, because
[24;1H[?1h=[;H[2J
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~[H
is a little bit difficult to work with when I'm wanting to edit source code.
Thanks very much. Mark Tuson.
I see The Unix Tree has browsable "4.1c BSD". Where can I download this
(so I don't have to browse)?
Also where can I find downloads for 4.1BSD and 4.1aBSD and 4.1cBSD and
anything after 2BSD but before 2.79BSD?
Thanks
Jeremy C. Reed
Hello.
I have a working Data General Aviion AV5500.
I'm searching for DG/UX tape images, documents and software for it,
specially
development kits for C.
Anybody has a machine like this or some data?
Thanks
Andrea
I managed to get 2.11 installed on SIMH, and hacked the de driver to work
(pretty much the same thing I did for 4.2 BSD on the 11/780) and now I've
gotten it networking.
I'll admit I'm not all that swift on the pdp-11, but I get the impression
that the maximum exe size is 128kb with 64kb of instructions, and 64kb of
data? Isn't there something that can be done with overlays or some other
linker thing to act like an 8086/80286 with the large memory model (ie
multiple segments...?)
I've been trying to build ircII-4.4 and I can't figure out how to link
something that big... I've tried the -Z and -O flags to ld to no avail.
Clearly I'm doing either something wrong, or impossible or stupid.
FWIW, here is the size of the same program on the VAX
myname# ls -l irc-4.4
-rwxr-xr-x 1 root 413696 Jun 8 08:46 irc-4.4*
myname# size irc-4.4
text data bss dec hex
293888 67584 20784 382256 5d530
I have a feeling that 300kb of text, along with 67kb of data is just too
much...?
Any pointers would be appreciated!
Jason
Sorry to bother you all with my questions over this ancient machine
and my failing trials with it..
Trying to get a DGUX system (Intel based) to work, as is, on a 'regular' x86 PC.
Just a couple of things :
1. I did find out that that DG machine is looking for an Adaptec PCI
SCSI Controller, and so I got an AHA-2940UW PCI card, installed it in
an old PC, got a matching 9GB HDD and booted it up from my image I've
'DD'ed from the original DG machine.
Boot prompt came up and said it's trying to load
sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3
it didn't, no error msg, just gave me back a "Boot command:" prompt.
Bootpath of the original machine is sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3.
The disk drive parameters are correct, according to the docs, its -
dev(ctrl(pci[pci_num]),slot[,func_num[,ctrl_id]])[,dev_id[,LUN]]).
I've checked the PCI slot in which I installed the card, it's 3, and
so I've tried '3' instead of 'd' in the command above, just got the
boot prompt back again.
Also tried - sd(apsc(pci(),3),0)root:/dgux -3 which should also work
according to the docs (all other params are default).
Tried to play with it and tried tons of combinations, just for the
heck of it, still nothing. If I do type in some nonsense it does give
me an error msg : "Error: No device specifications found in the boot
command. Invalid boot command line".
According to the docs, once I get the correct syntax, the system should load up.
Anyone got any advice about that?
2. Anyone here a/was a DG/UX user/admin? you guys are very hard to find :)
Thanks,
D'
---------- Forwarded message ----------
From: Bruce Jones <probes(a)communication.ucsd.edu>
Date: Mon, Aug 23, 2010 at 2:41 PM
Subject: [Sysadmin-L] Historical materials
To: sysadmin-L(a)ucsd.edu
Anyone want the complete set for BSD/386 v 1.0?
Includes manual, CDR, and 3.3" diskettes.
Just the thing to add to your library of obsolete but historically
significant software.
Bruce Jones
Department of Communication
(858) 534-0417/4410 FAX (858) 534-7315
-=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=-
--
carl lowenstein marine physical lab u.c. san diego
clowenstein(a)ucsd.edu
The 'problem' is with the de driver...Basically SIMH flags something wrong
with all incoming packets, and the driver thinks they are all corrupt...
in the procedure derecv
if ((rp->r_flags &
(RFLG_ERRS|RFLG_FRAM|RFLG_OFLO|RFLG_CRC))||
(rp->r_flags&(RFLG_STP|RFLG_ENP)) !=
(RFLG_STP|RFLG_ENP) ||
(rp->r_lenerr & (RERR_BUFL|RERR_UBTO|RERR_NCHN)) ||
len < ETHERMIN || len > ETHERMTU) {
something here is being passed wrong.. I've just changed the statement to
if(1==2) to keep the logic flow...
Anyways the same issue cropped up with 4.2 BSD & the VAX 11/780
On my pdp-11 the ini I'm using is:
set cpu 11/94 4M
set cpu cis
set cpu idle
set xu ena
att xu slirp
;attach tm0 211bsd.tap
attach tm0 ircii-4.4.source.tap
set rp0 rp06
attach rp0 auto.dsk
set rq dis
set rk dis
set rl dis
set hk dis
set rx dis
set tq dis
set dz lines=8
att dz 1000
boot rp0
I'm also using a version of SIMH that I've replaced the libpcap with SLiRP
from Qemu.. It's basically a user mode ip stack to do NAT. The advantage is
that they always have the same ip address, and it doesn't
require escalated privileges to run.
On Wed, Aug 11, 2010 at 5:45 AM, Johnny Billquist <bqt(a)softjar.se> wrote:
> Jason Stevens <neozeed(a)gmail.com> wrote:
>
> I managed to get 2.11 installed on SIMH, and hacked the de driver to work
>> (pretty much the same thing I did for 4.2 BSD on the 11/780) and now I've
>> gotten it networking.
>>
>
> Huh? What did you hack with the qe driver? Was that in 2.11BSD? I didn't
> know there was any problems with it in the first place.
>
> Or is there some problem in simh that you fixed?
>
> I'll admit I'm not all that swift on the pdp-11, but I get the impression
>>
>> that the maximum exe size is 128kb with 64kb of instructions, and 64kb of
>> data? Isn't there something that can be done with overlays or some other
>> linker thing to act like an 8086/80286 with the large memory model (ie
>> multiple segments...?)
>>
>
> Yes and no. In principle, the maximum size of a program is 64K instruction
> and 64K data. That's as much as is directly addressable. With overloays you
> can extend that somewhat, but there are limitations and restrictions.
>
>
> I've been trying to build ircII-4.4 and I can't figure out how to link
>> something that big... I've tried the -Z and -O flags to ld to no avail.
>>
>> Clearly I'm doing either something wrong, or impossible or stupid.
>>
>> FWIW, here is the size of the same program on the VAX
>>
>> myname# ls -l irc-4.4
>> -rwxr-xr-x 1 root 413696 Jun 8 08:46 irc-4.4*
>> myname# size irc-4.4
>> text data bss dec hex
>> 293888 67584 20784 382256 5d530
>>
>> I have a feeling that 300kb of text, along with 67kb of data is just too
>> much...?
>>
>> Any pointers would be appreciated!
>>
>
> You'll need to trim some fat off.
>
> Points to remember:
> 64K data is the max. There is no way to use overlays to get more data
> space. Overlays can only extend the instruction space.
> Overlays and the main program share the same address space. That is, the
> size of the main code and the largest overlay segment together must not
> exceed 64K. So, overlays is just a way to move parts of the program in and
> out of your basic 64K address space.
> When you link a program, you'll be able to see the sizes of all segments as
> well as the main program.
>
> As an example, this is how tcsh looks like:
>
> Test:/# size /bin/tcsh
>
> text data bss dec hex
> 48960 14844 11986 75790 1280e total text: 140864
> overlays: 15424,16000,14144,14016,16256,16064
>
> Notice how text+max(sizeof overlays) is less than 64K.
>
> All that said, you can easily find IRC clients who are much smaller than
> that... :-)
>
> Johnny
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt(a)softjar.se || Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol
>
Hi,friend
I find a good website which is www.dybers2.com It sells electronic
products. All of them are brand new and original and they all have
cheap price and high quality.The company also deal with the tariff for
us. One of my friends orders an Apple laptop. It only takes a week to
get it.
Let us enjoy the happiness of shopping. %--u
As you might remember from a previous post, I am trying to virtualize
/ emulate an old Data General UNIX system to a VM env'.
This is my progress so far (after a lot of reading, searching and
understanding who is who and what does it all mean) :
1. I've DD'ed an exact copy of the raw system disk as an image on my Linux box.
2. Loaded it up with most virtualization products out there - VMware,
VirtualBox, Xen/KVM/Qemu, Bochs and such.
They all work, ie, bootloader works and getting a DG/UX menu to
choose my proper kernel/system disk.
3. This is where they fail, as they cannot find the system's original
Adaptec PCI SCSI Controller (which is an AIC-7880 chip).
Most VM products only support LSI/BusLogic SCSI, and IDE of course.
As I see it, I have a few things I can do to make it work:
1. write an Adaptec driver for a VM product.
2. write an LSI/BusLogic driver for DG/UX or implement virtio drivers into it.
3. get IDE support working.
1st 2 options, as I understand from software eng' and other
professionals, are very difficult.
The 3rd option is interesting :
On one hand, I have an config file with all of DG/UX's supported
hardware, IDE is simply not there (would love for someone else to have
a look if possible. Just say so and I'll send you the file).
_and_ docs say "Data General has not tested or qualified the use of
IDE devices in AViiON AV 2100 systems".
_BUT_, on the other hand, BIOS seems to have plenty of IDE config
options and also docs say:
"IDE Interface - Disabled/Auto" , "OnBoard IDE Controller - enabled".
" The AV 2100 board set consists of a system board with six PCI
expansion slots, three ISA expansion slots, and several embedded
controller devices (PCI video, SCSI, Network, and IDE).
and "..A SCSI-III AIC-7880 controller for connecting up to seven 8-bit
narrow SCSI devices. You can also connect a mixture of fifteen 8-bit
narrow and 16-bit wide SCSI devices to the controller—maximum of seven
8-bit narrow SCSI devices. PCI-enhanced Integrated Drive Electronics
(IDE) hard disk interface that supports two hard disk drives"
Also " Since the lower bay contains a SCSI CD-ROM drive, only one
other SCSI device can be installed. You can install an IDE device in
the remaining bay. "
And much more. The question is, if I have an exact image of the
primary disk and I did try to load it via an IDE drive (in Qemu/
VirtualBox etc), didn't work out. Like last time, bootloader booted up
and then hang after trying to load the kernel.
Is there something I can try and do as a different config in my image file?
Anything else you can think of?
Please let me know if you need any file sent over.
Any help would be greatly appreciated.
Thanks,
Adam
Speaking of DG/UX, anybody know where to find this article?
M. H. Kelley. A look at the DG/UX file system.
Technical Report 3, Data General Corporation, 1990
I have a feeling DG was very early with journaling / crash resistant
filesystem tech but I've seen almost no detailed info, just a couple of
lines in a brochure.
John Finigan
asbesto(a)freaknet.org:
p.s. a copy of the operating system or a dump of the DISK/OS
will be appreciated, is very important to save this kind of
software, very hard to found today.
[...]
[ *I DELETE* EMAIL > 100K, ATTACHMENTS, HTML, M$-WORD DOC and SPAM ]
=======
I guess if I had a copy it would be unwise to e-mail it to you.
(I dislike using e-mail as a large-file-transfer service myself,
but I communicate with enough non-geeks that I consider the
battle lost.)
Norman Wilson
Toronto ON
Hi,
A big thanks to all who replied to my request for takers for the old
PDP-11 systems I have. I'm afraid I haven't been able to respond to
everyone yet as there's been a lot going on but I appreciate the
enlightenment on some of the aspects of the machines.
To be honest I really know very little about the PDP-11 and I had
hoped to learn more though these, so my MicroVAX II was a best guess
based on trying to match the hardware up to images on the web.
I will try and get back to all who expressed an interest with more
detailed information on the configuration and better pictures.
> Of course a PDP-11 is not a MicroVAX, and vice versa.
>
> Looking at the pictures, the only thing really worth saving would be
> the chassis shown with a keyboard next to it. One can see a floppy
> disk drive, and a hole where a hard disk drive probably was once. If
> there is a nameplate on the front, it is not readable in the picture.
> A picture of the rear panel would help in further identification, as
> well as a reading of any nameplate data on the rear panel.
--
Regards,
Kevin Phair
Hey all,
Got an old PentiumPro AViiON DG/UX machine.
I was just wodering if anyone happens to have an old, unused machine like
that.
If so, please reply with details, as well as geographic location.
All shipping costs will be payed by me.
A cash reward is offered, if you are interested.
Thanks,
A'
Hi,
A number of years ago I diverted a couple of PDP-11 systems which were
on their way to a skip. I believe they were in working condition and I
had always intended to clean them up and get them set up and running
again to see what it was all about. This never happened and I no
longer have the space to store them. As a result I'm offering them to
anyone who's willing to pay the shipping. They are located in Dublin,
Ireland.
There is some mild corrosion on some of the metal chassis and the
paint on the VDU casings is peeling off in place but overall I think
they will clean up well.
I think they are the MicroVAX II model and the consist of the PDP-11
chassis unit with a Ramstar T-1500 VDU and keyboard. Each one also has
a power distrubution box and they are configured for 120VAC operation.
There are also power cables (amongst others). I don't know what boards
are installed in them, but they did originally have tape drives
connected and were used to drive an inkjet printing system, so I
expect there is at least a tape controller and serial/parallel
interface in each of them.
Photos of everything are up on
http://sites.google.com/site/kevinphair/old-electronic-equipment/PDP-11
but unfortunately the cabinet units are no longer available.
If anyone is interested in these please get in touch soon as I won't
be able to keep them for much longer. If there's no interest in the
complete units, I'd also be happy to consider donating parts from them
to help with restorations or upgrade projects. I'm also open to
putting them in storage if someone wants to arrange collection at a
later date and is willing to split the storage costs.
--
Regards,
Kevin Phair
If you used BSD before 1982, please let me know. Off-list is fine. I
have a few questions to ask to help provide examples in a history book I
am writing. Thanks.
I'm sorry if this has been done before, but I could find no indication
this was the case in the unix archive itself or in any of the months I
checked in the mailing list.
I have figured out what the first 50176 bytes of s1-bits are.
It is an "INIT Tape" as described in Dennis_v1 Boot Procedures(VII) and
Dennis_v3 bproc.8. It is apparently contemporary with s2 [all of the
files on it /etc/getty /bin/ls and so on match up exactly with their
counterparts on s2], and this would seem to make s2 the "/bin-/etc-/lib
tape" described in bproc.8.
Also - is there any other known copy of the "bos" bootloader? I'm
partway through hand-disassembling the one on the tape.
Anyone know how to get SIMH to send ^J for return?
Anyway - with the KE-11A enabled you need to use "d system sr" to set
the switch register [which must be set to 1 to cold boot, 73700 to come
up in single user mode, and any random value other than the special ones
0 57500 10 20 40 1 2 to come up normally]
The RF disk is not even large enough to contain the whole s2 tape, and
while even v1 supported mountable filesystems, there is no mkfs or mount
on the tapes.
I was looking at several NetBSD manual pages and saw that some HISTORY
sections had wrong .Bx or BSD reference like:
HISTORY
The xstr command appeared in 3.0BSD.
I looked at a few and saw this was in 4.4BSD manual pages. By the way,
when were these history sections added? (They aren't in 4.2BSD manual
pages. I should look at 4.3 before asking ...)
I didn't see any that refered to original Berkeley UNIX Software Tape
nor 2BSD.
But from looking at the 1BSD and 2BSD, I see:
apropos was in 2bsd
colcrt was in 1bsd but not in 2bsd
even though 2BSD iul, soelim, and ssp manuals referenced it
(why missing from 2BSD?)
colrm was in 1bsd but not in 2bsd
csh was in 2bsd (even 1bsd referenced the upcoming "csh")
ctags was in 2bsd, but as a shell script using ed
expand was in 1bsd and 2bsd
finger was in 2bsd
fmt was in 2bsd
from was in 2bsd
head was in 1bsd and 2bsd
lock was in 2bsd
last was in 1bsd and 2bsd
mkstr was in 1bsd and 2bsd
msgs was in 2bsd
printenv was in 2bsd
soelim was in first BSD and 2BSD
tset was in 1bsd and 2bsd
w was in 2bsd as finger -sf
whatis was in 2bsd
whereis was in 2bsd
xstr was in 2bsd
lastlog file format was in 1bsd and 2bsd (?? maybe different format??)
Any comments on the above?
Or is this simply because "2BSD" is not a operating system release per
se, so "3.0BSD" is correct?
But this makes me wonder if my 2BSD versions are newer than first
2BSD, so really 3BSD is correct for some of this.
I was going to ask a NetBSD list about this to fix these histories, but
decided to consult TUHS instead. Okay to change history to fix history?
:)