The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Subject: [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape....
Date: Thu, 20 Oct 05 16:57:53 GMT	[thread overview]
Message-ID: <0510201657.AA16789@ivan.Harhan.ORG> (raw)

Aharon Robbins <arnold at skeeve.com> wrote:

> Wasn't there an "installboot" program that told the bootblock where
> to find the /boot file?

The installboot program in the original 4.3BSD, whose function has been
incorporated into disklabel(8) in 4.3-Tahoe/Quasijarus, writes the boot
blocks to the disk, but it does not patch them with the location of
/boot, the bootblock code is smart enough to understand the filesystem.

As for Robert's problem, I don't know where he got screwed - but man,
use your head, what do you think your god-given brain is for?  You can
single-step through the code with the MicroVAX ROM monitor's N command,
you can put some printf's in the code to see where it dies, etc, the
possibilities are limitless.  Just debug it the same way you would debug
any other problem.  What do you think I do when I get a similar
mysterious snafu?  I debug it like a real programmer, don't go crying to
a mailing list.

MS



             reply	other threads:[~2005-10-20 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 16:57 Michael Sokolov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-21 12:31 Jose R Valverde
2005-10-20  7:36 Aharon Robbins
2005-10-20 15:04 ` robertdkeys
2005-10-21  7:52   ` Jochen Kunz
2005-10-19  3:52 Michael Sokolov
2005-10-19  4:25 ` Gregg Levine
2005-10-19 17:28 ` robertdkeys
2005-10-15 15:49 [TUHS] Ancient unixes Gregg C Levine
2005-10-19  3:00 ` [TUHS] Bringing up any 4.3BSD on a MicroVAX without tape robertdkeys

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=0510201657.AA16789@ivan.Harhan.ORG \
    --to=msokolov@ivan.harhan.org \
    /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).