From: dfevans@bbcr.uwaterloo.ca (David Evans)
Subject: [pups] 2.11BSD device config trouble
Date: Wed, 30 Apr 2003 12:59:36 -0400 [thread overview]
Message-ID: <20030430125936.A7938@bcr10.uwaterloo.ca> (raw)
In-Reply-To: <20030430182349.N196974@MissSophie.unixag-kl.fh-kl.de>; from jkunz@unixag-kl.fh-kl.de on Wed, Apr 30, 2003 at 06:23:49PM +0200
On Wed, Apr 30, 2003 at 06:23:49PM +0200, Jochen Kunz wrote:
> On 2003.04.30 15:40 David Evans wrote:
>
> > I didn't see my other post go through;
> I got it only via private mail.
>
Ahh, OK--misfire on my part.
> > have you tried adding some comments
> > to the end of this line? Perhaps the autoconfig parser becomes
> > confused if there aren't any.
> Hmm.
> [...]
> I added comments at the end of the lines and now it works:
>
> April 30 17:29:29 init: configure system
>
> dhv ? csr 160440 vector 310 didn't interrupt.
OK--that at least fixed the "three handlers" (or whatever) error message.
I haven't looked in detail at the parsing code for autoconfig so I don't
know why this is happening. I may poke at it tonight if I have the energy,
though of course Steve has the knowledge to do it more easily. :-)
> But still trouble with the dhv. Maybe wrong interrupt vector too?
It's possible that your DHV board is simply strapped for something other
than 310.
> Normaly I use the console for booting only and then I telnet to the
> machine.
Likewise.
> But I wane connect some terminals to the PDP-11 at the VCFe, so
> the visitors can log in play around.
>
Not a bad plan.
> [fsck trouble]
> > Is the disk write-inhibited?
> No. It seams that I made the mistake to reboot using reboot(8) insted of
> power cycling the machine when fsck modified the file system. Didn't
> notice that / was mounted r/w.
I typically use "reboot -n" in such circumstances.
--
David Evans (NeXTMail/MIME OK) dfevans at bbcr.uwaterloo.ca
Ph.D. Candidate, Computer/Synth Junkie http://bbcr.uwaterloo.ca/~dfevans/
University of Waterloo "Default is the value selected by the composer
Ontario, Canada overridden by your command." - Roland TR-707 Manual
next prev parent reply other threads:[~2003-04-30 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 22:48 Steven M. Schultz
2003-04-30 8:24 ` Jochen Kunz
2003-04-30 13:40 ` David Evans
2003-04-30 16:23 ` Jochen Kunz
2003-04-30 16:59 ` David Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 19:14 Michael Sokolov
2003-05-01 13:49 Norman Wilson
2003-05-01 4:04 Steven M. Schultz
2003-05-01 3:30 Carl Lowenstein
2003-05-01 3:48 ` Gregg C Levine
2003-04-30 18:43 Steven M. Schultz
2003-05-01 9:24 ` Jochen Kunz
2003-04-30 16:03 Steven M. Schultz
2003-04-30 15:56 Steven M. Schultz
2003-04-30 16:58 ` Jochen Kunz
2003-04-29 21:54 Jochen Kunz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030430125936.A7938@bcr10.uwaterloo.ca \
--to=dfevans@bbcr.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).