9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: venti+fossil problems on new install
Date: Fri, 22 Sep 2006 16:06:43 -0500	[thread overview]
Message-ID: <da866941428105e08d910e5b41b69ff3@quanstro.net> (raw)
In-Reply-To: <200609222150.ab09361@salmon.maths.tcd.ie>

On Fri Sep 22 15:51:32 CDT 2006, stalker@maths.tcd.ie wrote:
> I think the question of whether the mbr is plan9 or not is a bit of a red
> herring.  I have trouble even when booted from the cdrom.  The specific
> error message I get about not having an mbr comes from
> /sys/lib/dist/pc/inst/partdisk on the cdrom.  A quick look at the rc
> script shows that it should appear when /sys/lib/dist/pc/inst/hasmbr
> returns false.  That should happen when the magic number in the last
> two bytes of the mbr is wrong, i.e. not aa55.  The magic number is not
> wrong, however.  The only explanation I can come up with is that the
> read of /dev/sdC0/data is failing for some reason.

why don't you try this by hand?

i have one machine that can't be booted from the cdrom and access the hd.
what i have to do is boot from the floppy, start 9660srv to mount the cd
and continue.

- erik


  reply	other threads:[~2006-09-22 21:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  6:50 John Stalker
2006-09-21  8:13 ` erik quanstrom
2006-09-21 18:19 ` Lyndon Nerenberg
2006-09-21 18:25   ` erik quanstrom
2006-09-21 18:51     ` jmk
2006-09-21 20:27       ` C H Forsyth
2006-09-21 20:47     ` Charles Forsyth
2006-09-21 20:56       ` jmk
2006-09-21 21:08         ` Charles Forsyth
2006-09-21 21:50           ` erik quanstrom
2006-09-21 22:00             ` Charles Forsyth
2006-09-21 22:16               ` erik quanstrom
2006-09-21 22:31                 ` Charles Forsyth
2006-09-21 22:31                 ` jmk
2006-09-21 23:22                   ` erik quanstrom
2006-09-21 23:28                     ` geoff
2006-09-21 23:47                       ` geoff
2006-09-22  0:05                         ` erik quanstrom
2006-09-22  0:24                           ` Russ Cox
2006-09-22  0:50                             ` erik quanstrom
2006-09-22  1:25                               ` jmk
2006-09-22  7:23                             ` John Stalker
2006-09-22 11:23                               ` erik quanstrom
2006-09-22 17:30                                 ` John Stalker
2006-09-22 17:45                                   ` erik quanstrom
2006-09-22 19:48                                     ` John Stalker
2006-09-22 20:09                                       ` erik quanstrom
2006-09-22 20:50                                         ` John Stalker
2006-09-22 21:06                                           ` erik quanstrom [this message]
2006-09-22  0:29                           ` jmk
2006-09-21 23:52                       ` erik quanstrom
2006-09-21 23:59                       ` erik quanstrom
2006-09-22  0:50                         ` geoff
2006-09-22 16:39                           ` erik quanstrom
2006-09-23  5:24 Zoran Kolic
2006-09-23  6:51 ` John Stalker
2006-09-23 10:34   ` erik quanstrom
2006-09-23 15:04     ` Russ Cox

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=da866941428105e08d910e5b41b69ff3@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).