Probably this is documented somewhere, but I really need a pointer or a
brief tutorial on the major/minor device numbers for mknod() and the device
names for MSCP drives in 2.11bsd.
If I have a really simple PDP with an RQDXn and one RDxx disk, then the
device name is conventionally /dev/ra0x and the first partition, ra0a is
(5,0), the second, ra0b, is (5,1), etc. Pretty easy.
If I have two drives on my single RQDXn, then the second hard disk is
/dev/ra1 and ra1a is (5,8), ra1b is (5,9), etc. I guess the offset of 8
must be the maximum number of partitions on a drive - OK, I'm still with
you.
But what if I have a second MSCP controller? Assuming that I've built the
kernel to handle it and modified dtab to autoconfigure it, that is. What
are the usual names and mknod() numbers for the drives on the second
controller?
Worse, what if the MSCP controller isn't a RQDX but is a real UDA/QDA ?
Now the drives have their own MSCP unit numbers that can be anything from 0
to 250 - where does this figure in?
Same question for TMSCP - what if I have more than one tape controller?
This case is easier, though, since TMSCP controllers normally have only one
drive associated with them.
Thanks,
Bob Armstrong
> The bandwidth of a mouse and menus is not very high. The bandwidth of a
> keyboard is a lot higher.
I've long thought that what we needed was control panel which operated on
revision controlled flat files in /etc. So you could write scripts to
do the automated stuff but you could point and click to do the stuff that
you forgot how to do.
--
---
Larry McVoy lm at bitmover.comhttp://www.bitkeeper.com
whilst looking around the bitsavers.org pdf archive, I
found a document called
PreliminaryUnixImplementationDocument_Jun72.pdf.
Having had a quick scan through, it contains a source
code listing and some commentary (lions i hear you
say). The strange thing is that all of the source code
appears to be in assembler...
whats this about?
is it a comentary of PDP-7 unix?
regards
Martin
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
On 6/15/06, Greg 'groggy' Lehey <grog(a)lemis.com> wrote:
> On Wednesday, 14 June 2006 at 16:24:29 -0700, Martin Lovick wrote:
> > whilst looking around the bitsavers.org pdf archive, I found a
> > document called PreliminaryUnixImplementationDocument_Jun72.pdf.
>
> Can you give a full URL for this document? I've taken a brief look at
> the list in http://bitsavers.org/pdf/, but nothing jumped out at me.
< http://bitsavers.org/pdf/bellLabs/unix/PreliminaryUnixImplementationDocumen…
>
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
Martin Lovick remarked,
> whilst looking around the bitsavers.org pdf archive, I
> found a document called
> PreliminaryUnixImplementationDocument_Jun72.pdf.
> Having had a quick scan through, it contains a source
> code listing and some commentary (lions i hear you
> say). The strange thing is that all of the source code
> appears to be in assembler...
> whats this about?
> is it a comentary of PDP-7 unix?
It is a fairly early version, with commentary, of PDP-11 Unix (the kernel),
indeed still in assembler. It is an interesting find, probably
the earliest version yet unearthed. Kossow told me about
it when he did (or got) the scan of the document.
I can't remember receiving it at the time.
It is clearly different from what we in the research
group were running at the time--it has devices we didn't have,
and I think by then we were on the 11/45.
Dennis
This is a long New York Times article with a lot of detail.
They say there'll be at least one public open house before it's
demolished. I think you can now read a limited number of NY Times
articles without subscribing (they seem to count how many you read
-- maybe with a cookie). Here's the URL:
http://www.nytimes.com/2006/06/14/realestate/commercial/14bell.html
Jerry
--
Jerry Peek, jpeek(a)jpeek.com, http://www.jpeek.com/
Hi,
last week a work mate told us a tale about how Unix came to its
name. He believes that Unix is named after the term eunuch (a
homophone of (to?) unix in english language). One can see Unix as a
castrated successor of Multics. Hmmm, I am interested in Unix history
for several years now, but I haven't heard about that before. It is
really a tale I guess. Any clear words about this topic?
Michael
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Hi,
"Bill Cunningham" <billcu1(a)verizon.net> writes:
> ----- Original Message -----
> From: "Michael Welle" <m.welle(a)gmx.net>
> To: <tuhs(a)minnie.tuhs.org>
> Sent: Saturday, June 03, 2006 9:57 AM
> Subject: [TUHS] Unix, eunuchs?
>
>
>> Hi,
>>
>> last week a work mate told us a tale about how Unix came to its
>> name. He believes that Unix is named after the term eunuch (a
>> homophone of (to?) unix in english language). One can see Unix as a
>> castrated successor of Multics. Hmmm, I am interested in Unix history
>> for several years now, but I haven't heard about that before. It is
>> really a tale I guess. Any clear words about this topic?
>>
>> Michael
>>
>
> I know Dennis have said pretty clearly that Unix is a pun on Multics
> that the team really never got to start on because Bell changed there minds.
> Ken continued with Unix which must've been his idea. In assembly first then
> B. Dennis came up with C and its lasted down through the years.
that sounds familiar to me. The same story is told in 'A quarter
century of Unix' and other sources.
VG
hmw
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
> There's a reason Dennis Ritchie and Ken Thompson have been awarded
> the U.S. National Medal of Technology (1998) and are fellows of the
> Computer History Museum Online. Dave Cutler hasn't and isn't.
> "You are not expected to understand this."
And while I think this is a little unfair to Dave that's a great .sig
It goes well with the recent post about Unix vs NT that concluded about
NT "there is no there there". I live on both platforms and I couldn't
agree more.
Some day I'll post my view on this but here is the really short summary.
There are two classes of people: those who derive answers and those who
memorize them. As Mark Twain said, the latter group is much larger than
the former. My claim is that Unix appeals to the first group - you can
guess what it is going to do and you'll be right most of the time.
Windows appeals to the other group. They don't have the ability to derive
any answer and they are comfortable with a system that mostly works but
has "no there there". They can't tell the difference.
The sad part (and the good part!) is that all of us on this list are
in the former group which is smaller. I think we (well, many of us)
wish that more people thought like we do and figured stuff out for
themselves but the reality is that most people aren't inclined to do that.
So the good and bad part is that we're a small select group. Personally,
I've come to accept that and like it. I've gotten to the point where I
realize that people who can derive the answer are special, they are gift,
and I consider myself lucky when I run into a concentrated group of them.
Cough, cough, that would be you. :)
--
---
Larry McVoy lm at bitmover.comhttp://www.bitkeeper.com