7 Jun
2000
7 Jun
'00
3:56 a.m.
On 6 Jun, Michael Sokolov wrote:
A litle
note like:
Look at http://minnie.cs.adfa.edu.au/Quasijarus/compress.html to see how
to decompress the files.
in the FORMAT file can save much time if you are a Quasijarus beginner.
Or a Link "HOWTO install Quasijarus" with a note about the compress
issue, creating tapes, ... on the Quasijarus main page will do the job
also.
Pointers would go on the web pages (that's easy). Real files in the Archive :-)
As part of the division of things into system/platform-specific and
Unix-generic areas, I'm updating the Unix Heritage Society web pages.
A preview is at http://minnie.cs.adfa.edu.au/tuhs/
We need more affiliated groups! Bob, you want to lead an IBM group?
David, how about an encumbered BSD group? Minnie will provide web space,
archive area, mail list as required.
The web page above is the place to put pointers to hardware information
and other useful stuff, unless that has already been done by an affiliated
group. So start sending me URLs :-)
The existing pups@minnie mail list will become the tuhs@minnie list. A
new pups@minnie list will be created for PDP-11 specific stuff. Next week
sometime.
In a month say, I'll reorganise the structure of the PUPS Archive, and
rename it as the Unix Archive. If you have mirrors, don't worry I'll
e-mail out a shell script with lots of mkdir and mv commands in it :-)
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id IAA17685
for pups-liszt; Wed, 7 Jun 2000 08:51:22 +1000 (EST)
(envelope-from owner-pups(a)minnie.cs.adfa.edu.au)
Ahhh! Why is
there no note in the distribution directory?
OK, I'll add one. Hmm, I thought this was enough info for folks to
figure out that
components/compress.tar is the right tarball...
Again. "Look at
Distributions/4bsd/components/compress.tar" can save
time...
It's in the components directory, as opposed to
the tape distribution directory
for any particular release, because it's a grabbed-out BSD component that can
be used with any release. The tape distribution directories have exactly what
goes on the tape in the format it goes there, nothing more, nothing less.
Ahh. I
did not know this.
ARGL! Now my TK50 died! Sh..., fu..., [other censored stuff]
What have we learned now? Kids, do not dismount the optical positioner
at the back of a TK50 drive for cleaning! GRMBL.
OK. Tomorrow is a new day, new luck. I will mount the TK50Z in the MVII
and I will give Quasijarus a try. If Quasijarus also fails, the BA23 box
will stay inactive until I get a working, 2.11BSD capable PDP11 CPU.
--
a guts Nächtle,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id HAA17429
for pups-liszt; Wed, 7 Jun 2000 07:59:15 +1000 (EST)
(envelope-from owner-pups(a)minnie.cs.adfa.edu.au)
From Warren Toomey <wkt(a)cs.adfa.edu.au> Wed Jun
7 07:57:16 2000
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au
[131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id HAA17425
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 7 Jun 2000 07:59:13 +1000 (EST)
(envelope-from wkt(a)henry.cs.adfa.edu.au)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id HAA32202;
Wed, 7 Jun 2000 07:57:16 +1000 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <200006062157.HAA32202(a)henry.cs.adfa.edu.au>
Subject: Re: Hardware info in Unix Archive
In-Reply-To: <200006062030.QAA05591(a)uni00du.unity.ncsu.edu> from
"rdkeys(a)unity.ncsu.edu" at "Jun 6, 2000 4:30:26 pm"
To: rdkeys(a)unity.ncsu.edu
Date: Wed, 7 Jun 2000 07:57:16 +1000 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society)
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by rdkeys(a)unity.ncsu.edu:
> Terry Kennedy's THIRD-PARTY-DISKS.TXT,
available via anonymous FTP
> from
>
> ftp://ftp.spc.edu/third-party-disks.txt
>
> Since this subject comes up several times a year, would it be possible
> to link to the above document from somewhere in the PUPS archive, Warren?
I'd prefer to not put things into the archive unless they were Unix-related.
Notwithstanding that comment, if there's enough disk space, why not.
However, it would have to be in an area which was marked as generic information.
Ciao,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id IAA17544
for pups-liszt; Wed, 7 Jun 2000 08:25:16 +1000 (EST)
(envelope-from owner-pups(a)minnie.cs.adfa.edu.au)
From Warren Toomey <wkt(a)cs.adfa.edu.au> Wed Jun
7 08:23:20 2000
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au
[131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id IAA17540
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 7 Jun 2000 08:25:14 +1000 (EST)
(envelope-from wkt(a)henry.cs.adfa.edu.au)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id IAA32518;
Wed, 7 Jun 2000 08:23:20 +1000 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <200006062223.IAA32518(a)henry.cs.adfa.edu.au>
Subject: Re: Hardware info in Unix Archive
In-Reply-To: <020401bfd004$d7ee0490$5d01a8c0@p2350> from emanuel stiebler at
"Jun 6, 2000 4:16:14 pm"
To: emu(a)ecubics.com (emanuel stiebler)
Date: Wed, 7 Jun 2000 08:23:20 +1000 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society)
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by emanuel stiebler:
I'd
prefer to not put things into the archive unless they were
Unix-related.
Why not an pointer to the ftp archive ?
If something changes there, we're updated. So we have to keep track of the
changes :-( From Warren Toomey <wkt(a)cs.adfa.edu.au> Wed Jun
7 08:49:14 2000
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au
[131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id IAA17681
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 7 Jun 2000 08:51:20 +1000 (EST)
(envelope-from wkt(a)henry.cs.adfa.edu.au)
Received: (from wkt@localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id IAA32738;
Wed, 7 Jun 2000 08:49:14 +1000 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt(a)cs.adfa.edu.au>
Message-Id: <200006062249.IAA32738(a)henry.cs.adfa.edu.au>
Subject: Re: VAX group in TUHS?
In-Reply-To: <393D9CE9.533EFA0E(a)openecs.org> from chris at "Jun 7, 2000
2:52:57 am"
To: chris(a)openecs.org (chris)
Date: Wed, 7 Jun 2000 08:49:14 +1000 (EST)
Cc: pups(a)minnie.cs.adfa.edu.au (Unix Heritage Society),
msokolov(a)ivan.Harhan.ORG
Reply-To: wkt(a)cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
In article by chris:
I really like to help starting a VAX Unix archive. My
VAX11/750 is bored by
NetBSD and want's to try out some other "real" UNIX.
So this might be a great chance.
Regards - Chris
At present, Michael Sokolov looks after the 4BSD VAX section of the
archive under the aegis of the Quasijarus project. Michael, do you want
to continue to do this? Or should we separate the historical 4BSDs for
someone to curate while you manage the ongoing Quasijarus work?
Cheers,
Warren
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id IAA17708
for pups-liszt; Wed, 7 Jun 2000 08:59:36 +1000 (EST)
(envelope-from owner-pups(a)minnie.cs.adfa.edu.au)
From "Steven M. Schultz"
<sms(a)moe.2bsd.com> Wed Jun 7 08:45:02 2000
Received: from moe.2bsd.com
(0(a)MOE.2BSD.COM [206.139.202.200])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id IAA17704
for <pups(a)minnie.cs.adfa.edu.au>; Wed, 7 Jun 2000 08:59:30 +1000 (EST)
(envelope-from sms(a)moe.2bsd.com)
Received: (from sms@localhost)
by moe.2bsd.com (8.9.3/8.9.3) id PAA01871;
Tue, 6 Jun 2000 15:45:02 -0700 (PDT)
Date: Tue, 6 Jun 2000 15:45:02 -0700 (PDT)
From: "Steven M. Schultz" <sms(a)moe.2bsd.com>
Message-Id: <200006062245.PAA01871(a)moe.2bsd.com>
To: jasomill(a)shaffstall.com, pups(a)minnie.cs.adfa.edu.au
Subject: Re: RX50 on RQDX3 on 2.11BSD
Sender: owner-pups(a)minnie.cs.adfa.edu.au
Precedence: bulk
Hi --
Wow, quite a bit of interest in 2.11 these days - I suppose I should
get back into it (too many other projects, etc and so little time ;))
From: "Jason T. Miller"
<jasomill(a)shaffstall.com>
Does anyone have experience using the RX50 floppy drive under 2.11BSD? I
patched my FreeBSD kernel to handle RX50-format (80 cyl / 1 hd / 10 sec)
Not for eons - the RX50 I had was so flakey (well, actually it finally
got to the point it was declared broke) it was replaced with a 1.2mb
5.25" Teac "PC" drive).
$ dd if=testrx50.img of=/dev/ra12a
800+0 records in
800+0 records out
$ dd if=/dev/ra12a of=test
800+0 records in
800+0 records out
$ diff testrx50.img test
Binary files testrx50.img and test differ
WHOA! This shouldn't happen, should it? In my late-night screwings-around,
No, in fact I'd have expected an error on the first 'dd'.
Using 'cmp -l' will show where the differences are. If they are only
in the first couple sectors but the rest compare ok then I think I
know what the problem might be.
I'd also, not that it would make any difference (I hope), use the
raw device for speed purposes (RX50 is slow enough as it is ;)):
dd if=testrx50.img of=/dev/rra12a
- The '11/2.11BSD never seem to write the first
two sectors, although
no error is returned to this effect; in fact, the data in sector three is
from offset 1024 in the input data (0x0003 in the above example). Is this
due to disk label support or something? The raw (character) device reports
itself as read-only, even for root.
Indeed it is related to disklabel support. In the face of a missing
or corrupt disklabel the kernel is supposed (and I think it is in this
case) synthesize a label that spans the entire disk with the 'a'
partition.
I do not know why the first two sectors are not being written if the
synthetic label is being used. It's probably a bug having to deal
with not setting the "enable write for label area" when the fake label
is being used. Sigh. I have a floppy drive on my 11/73 - I'll try
to find time and play around before going on vacation in a couple weeks.
The first sector should have been written (that's the boot block), the
label sector is the 2nd sector and that's 'write protected' unless
either an ioctl() is done or the 'disklabel' program is used to
un-writeprotect it.
Try doing a
disklabel -W /dev/rra12a
to enable writing the label sector. If that works then the problem
lies in not setting that bit when a corrupt/missing label is seen.
Normally this isn't necessary since filesystems are created on disks
and they're not treated as raw output bitcontainers. Floppies are
special in that 'raw' device usage is more common.
Finally, I noticed there is no floppy-specific code in
the MSCP driver, so
all the gory details of floppy control (along with the gory details of the
above) must be dealt with by the RQDX3. Anybody got documentation for this
Quite so. To the driver the RX50 is just another MSCP disk.
Oh, for debugging purposes you can enable more or all of the MSCP
messages with the 'sysctl' command:
sysctl -w machdep.mscp.printf=X
where X is a bitmask (at present only the first 4 bits are in
use). Setting X to 15 will enable every printf the driver
has.
* Bit 0 = print/log all non successful response packets
* Bit 1 = print/log datagram arrival
* Bit 2 = print status of all response packets _except_ for datagrams
* Bit 3 = enable debug/log statements not covered by one of the above
See the pdpuba/ra.c sources for more details, and what printf/log
statements are covered by which bit.
Steven Schultz
sms(a)moe.2bsd.com
Received: (from major@localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id JAA17936
for pups-liszt; Wed, 7 Jun 2000 09:41:44 +1000 (EST)
(envelope-from owner-pups(a)minnie.cs.adfa.edu.au)