9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug fix to /sys/src/libdisk/disk.c and /386/bin/format
Date: Mon, 23 Oct 2000 10:48:43 -0700	[thread overview]
Message-ID: <200010231748.e9NHmhH53490@ducky.net> (raw)
In-Reply-To: <39F25303.9417B14F@null.net>

>Perhaps a working Plan 9 boot block (512 bytes) could be
>placed on the distribution updates page?  (One could floppy-
>boot the system then copy the new block into place.)

The problem with this idea is that getting the correct bits
in your Plan 9 boot block depends on the disk geometry as
well as the details of the 9fat partition.  So there is
no one-size-fits-all boot block.

But, perhaps the Bell Labs folks could provide a new
install/boot floppy image, with a bugfixed format binary?

In the meantime, here is a sleazy workaround you can do
with the current install/boot floppy that will have the
exact same effect: just prior to doing the "bootsetup"
command, start a new window, and in the new window type
this command:

	dd -if /dev/sd00/data -of /dev/sd00/9fat -count 1

(where sd00 is the disk you are installing Plan 9 on; for IDE
disks it will be something like sdC0, etc.)

Then, go back to the install command window, run "bootsetup",
and select the "plan9" boot method.  (It will ask if you want
to install a new master boot record; in my experience you
can usually decline and things will work fine--you especially
want to say "no" if you are running a multi-boot manager of
some kind.  I use the one that comes with FreeBSD.)



  reply	other threads:[~2000-10-23 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-21  8:08 Mike Haertel
2000-10-23  9:01 ` Douglas A. Gwyn
2000-10-23 17:48   ` Mike Haertel [this message]
2000-10-21 14:10 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=200010231748.e9NHmhH53490@ducky.net \
    --to=mike@ducky.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).