Hello again from Gregg C Levine
Yes, Ian. That's exactly what I mean. Of course I was thinking of RL02
images, rather then a RK05 image. Which one did you choose? And can
you post something explaining the steps?
And your response was the simpler form, which is what I wanted.
David's comment was a bit obtuse, but I got it. By the way? Are you a
WB fan? As in Warner Bros. Animation. I'm partial to the wisdom of B.
Bunny.
-------------------
Gregg C Levine hansolofalcon(a)worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."Â Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
Sign on the side of a transport belonging to the Rebel Alliance,
"Force happens".
> -----Original Message-----
> From: Ian King [mailto:iking@killthewabbit.org]
> Sent: Thursday, May 01, 2003 1:34 AM
> To: Gregg C Levine
> Subject: Re: [pups] Restoring volumes
>
> That's where I got my RK05 image for UNIX v6, which I run on my
11/34. Is
> that what you're asking, or am I being simple? -- Ian
>
> ----- Original Message -----
> From: "Gregg C Levine" <hansolofalcon(a)worldnet.att.net>
> To: <pups(a)minnie.tuhs.org>
> Sent: Wednesday, April 30, 2003 8:35 PM
> Subject: [pups] Restoring volumes
>
>
> Hello again from Gregg C Levine
> Just for the sake of an argument, has anyone actually managed to
> restore a volume from the collection on the ftp server, back to an
> originally sized disk pack? Or for that matter restored a system so
> that it behaves as advertised under E-11?
>
> No, folks that machine I "have on order", has not arrived. Once
again
> I am searching for information for a future project. One that might
be
> happening sometime this week, or even later this month.
> -------------------
> Gregg C Levine hansolofalcon(a)worldnet.att.net
> ------------------------------------------------------------
> "The Force will be with you...Always." Obi-Wan Kenobi
> "Use the Force, Luke." Obi-Wan Kenobi
> (This company dedicates this E-Mail to General Obi-Wan Kenobi )
> (This company dedicates this E-Mail to Master Yoda )
Norman Wilson <norman(a)nose.cs.utoronto.ca> wrote:
> This convenience was abolished in either 4.2 or 4.3 (I am
> travelling right now and cannot check manuals and
> sources).
I don't remember the details in my head and I'm also typing this on the go, but
in 4.3BSD fsck does work on the block device and then you reboot with, well,
reboot, and it works.
MS
Carl Lowenstein:
Isn't this really true of Unix systems of any age, when doing fsck
on a mounted root file system?
Some middle-elderly BSD systems--4.1 and possibly 4.0--
managed the buffer pool in such a way that the super-block
of a mounted file system was kept in the original buffer,
with device and block number correctly stored in the struct
buf header. Hence if fsck wrote to the block device rather
than the raw one, the super-block came out right even when
checking a mounted file system; in particular there was no
need to reboot.
This convenience was abolished in either 4.2 or 4.3 (I am
travelling right now and cannot check manuals and
sources). I never quite understood why, though I never
looked at the source code in the later systems. The
scheme found in most current systems, in which the
root starts out read-only, is a better idea anyway.
Norman Wilson
Toronto ON (normally)
Hello again from Gregg C Levine
Just for the sake of an argument, has anyone actually managed to
restore a volume from the collection on the ftp server, back to an
originally sized disk pack? Or for that matter restored a system so
that it behaves as advertised under E-11?
No, folks that machine I "have on order", has not arrived. Once again
I am searching for information for a future project. One that might be
happening sometime this week, or even later this month.
-------------------
Gregg C Levine hansolofalcon(a)worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."Â Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
Sign on the side of a transport belonging to the Rebel Alliance,
"Force happens".
Hi -
> From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de>
> As already mentioned: If I add comments at the end of the lines it
> cn 1 176540 344 5 cnrint cnxint # kl/dl-11 (on mvx11-aa)
> cn 2 176550 354 5 cnrint cnxint # kl/dl-11 (on mvx11-aa)
> cn 3 176560 364 5 cnrint cnxint # kl/dl-11 (on mvx11-aa)
> cn 1 csr 176540 vector 344 attached
> cn 2 csr 176550 vector 354 attached
> cn 3 csr 176560 vector 364 attached
> Sounds like a funny bug?
Yes, it does. A bug in the parsing. Why it does not affect all
the lines is unknown. Perhaps some trailing whitespace caused the
parser to exhibit the bug.
> But if I try to use /dev/ttyl1 I get a message about a unknown interrupt
> and the output of /dev/ttyl1 hangs after the first character.
What is the exact message? I did a "strings /unix" and could not
not find a string that looked mentioned unknown or interrupt.
That would seem to indicate that the device is interrupting but not
at the expected vector.
It is possible to use 'adb' to look at the contents of the vectors.
adb -k /unix /dev/kmem
0344/o
will show the contents of the 0344 vector. The value there should
be equal to 'cnrint' (or cnxint - I forget which comes first).
> I have a M3106 DZQ11 that I can use instead.
Definitely worth trying.
> The DHV is a DEC M3104:
> dhv ? csr 160440 vector 310 didn't interrupt.
> The DL11 card is a clone made by Sigma.
Ah, ok. Thanks for the correction. I misread the initial mail item.
> > 'halt' button?
> [...]
> Noticed that already. I am really not used to Unix stuff of that age.
:)
I did the the same thing - wondered why I could never get a clean
file system. Then I realized what was going on.
Cheers,
Steven Schultz
Hi -
> From: Carl Lowenstein <cdl(a)mpl.ucsd.edu>
> > > > 'halt' button?
> > > [...]
> >
> > I did the the same thing - wondered why I could never get a clean
> > file system. Then I realized what was going on.
>
> Isn't this really true of Unix systems of any age, when doing fsck
> on a mounted root file system?
Not really. Newer systems mount the root filesystem read-only
while running fsck. After the filesystem is verified as clean
then it is upgraded to read-write.
Older systems such as 2BSD can't run with a read-only root
filesystem that I know of. At least not easily/happily. Might be
possible (the ability to upgrade a ro mount to rw is present) but
it's never been a priority to look into it ;)
Cheers,
Steven Schultz
> From: "Steven M. Schultz" <sms(a)2BSD.COM>
> To: pups(a)minnie.tuhs.org
> Subject: Re: [pups] 2.11BSD device config trouble
> Date: Wed, 30 Apr 2003 11:43:11 -0700 (PDT)
>
> Hi -
>
> > From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de>
>
> > > 'halt' button?
> > [...]
> > Noticed that already. I am really not used to Unix stuff of that age.
>
> :)
>
> I did the the same thing - wondered why I could never get a clean
> file system. Then I realized what was going on.
Isn't this really true of Unix systems of any age, when doing fsck
on a mounted root file system?
carl
Anyone thought of asking him if he could contribute his Concurrent Pascal and
Solo, etc, to PUPS?
Just a thought.
Welsey Parish
--
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."
Hi -
> From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de>
> I am preparing my PDP-11/73 for my exhibition at the VCFe. I want to get
> the DHV11 (M3104) and a four port DLV11J clone to work. At the moment I
> get upon boot:
>
> autoconfig: warning: more than three handlers for device cn on line 38.
That is not a normal message. I believe autoconfig is saying that
is something wrong with line 38 of /etc/dtab
> dhv ? csr 160440 vector 310 didn't interrupt.
> ra 0 csr 172150 vector 154 vectorset attached
> ra 1 csr 160334 vector 764 vectorset attached
> rx ? csr 177170 vector 264 skipped: No CSR.
> tms 0 csr 174500 vector 260 vectorset attached
> ts 0 csr 172520 vector 224 attached
> cn 1 csr 176540 vector 344 no address found for kl/dl-11
> What is wrong with the "cn" devices?
Is 'cn 1 ...' line 38 of the /etc/dtab file?
Did you compile a kernel with NKL set to 5 (1 for the console and
4 for the DLV11J)?
Cheers,
Steven Schultz
Hi -
> From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de>
> > > cn 1 csr 176540 vector 344 no address found for kl/dl-11
> > Is 'cn 1 ...' line 38 of the /etc/dtab file?
> Yes:
> cn 1 176540 344 5 cnrint cnxint
Interesting. I do not recall any particular problem getting
additional DL devices recognized (the 11/93 had 7 of them).
Seeing the 'no address found' error is *strange* though - that
would indicate that 'autoconfig' could not find 'cnrint' or 'cnxint'
in the /unix symbol table. Look at /sys/autoconfig and you can
see where that message is coming from.
If you do
nm /unix | egrep 'cnxint|cnrint'
what do you see?
> NKL 4 # KL11, DL11
> The card has four ports, one of them is the console. (The M8192 CPU card
> has no SLU / ROM / ...)
Ah, ok. My 11/73 has a SLU/ROM card and the console is on that. I
also have a DHV installed (alas, the system is powered down now
so I can not check for more information).
> But I would prefere to get the DHV11 working. It seams that this device
> is more suitable for multi user operation.
Yes, it's a little better. Not as nice as a DHQ-11 though (which can
run in DHU or DHV modes - with DHU mode having much better silo
handling).
I forget the exact error you were getting on the DHV but if it was
'no interrupt' then it might be that the DHV clone is not behaving
exactly like a DEC DHV
In /sys/autoconfig/dhvauto.c here is how the probing attempts to
force an interrupt:
dhvprobe(addr,vector)
struct dhvdevice *addr;
int vector;
{
if ( grab ( &(addr->dhvcsr) ) & DHV_CS_MCLR )
DELAY(35000L);
if ( grab ( &(addr->dhvcsr) ) & (DHV_CS_MCLR|DHV_CS_DFAIL) )
return ( 0 );
stuff ( DHV_CS_RI | DHV_CS_RIE, &(addr->dhvcsr) );
DELAY(3500L);
stuff ( 0, &(addr->dhvcsr) );
return(ACP_IFINTR);
}
Either 3500 microseconds (very approximately of course) is too short
of a wait _or_ the method of trying to generate an interrupt is
not correct. You can try changing 'ACP_IFINTR' to 'ACP_EXISTS'
which tells autoconf to not care if the device interrupted or not.
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Free List
> BLK(S) MISSING
> SALVAGE? y
>
> ** Phase 6 - Salvage Free List
> 1364 files, 11625 used, 2430 free
>
> ***** FILE SYSTEM WAS MODIFIED *****
>
> But on the next reboot I get the same when running fsck. Any hints?
How are you rebooting? With the "reboot" command or by using the
'halt' button? You do not want to use the 'reboot' command because
that does a "sync" which flushes the disc cache (and superblock) back
out to disc - that overwrites the work that 'fsck' did.
A few 'missing' blocks is not a serious problem though and can be
ignored.
Cheers,
Steven Schultz
