9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brian L.Stuart <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] installation procedure question
Date: Wed, 14 Feb 2007 10:41:40 -0600	[thread overview]
Message-ID: <20070214164140.ZKYZ17450.ibm65aec.bellsouth.net@mail.bellsouth.net> (raw)

> While searching for info on how to get this to work with the grub 
> bootloader, I found this on a forum:
>
> Cd anyone comment on this or, even better, suggest a way to avoid this 
> happening if true? I am thinking of installing onto a Dell PIII laptop 
> with 6 other OSs currently on it. I wanted to put Plan 9 on the final 
> primary partition on the drive and continue to use Grub as a bootloader.

I can't speak authoritatively, but I can relate how I installed
it on mine using grub.  The short answer is that I selected
the option that installs the boot loader in the partition's boot
block, rather than the disk's MBR.  Then I configured grub
to act much like you do for Windows.  The actual grub entry
I have looks like:

title=Plan9
  rootnoverify (hd0,1)
  chainloader +1

Now having said that, I must also say that I seem to always
end up doing something wrong along the way.  Almost every
time I do an install, I end up having to manually mess with
the DOS partition where the kernel and plan9.ini are kept.
But I've been able to successfully install it several times
without killing the other OSs on the machine.

One caveat:  It's been a while since I last did this, so my
memory of details may be a bit fuzzy.

BLS




             reply	other threads:[~2007-02-14 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 16:41 Brian L.Stuart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-14 16:28 Glenn Becker
2007-02-16 11:17 ` Alberto Cortés

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=20070214164140.ZKYZ17450.ibm65aec.bellsouth.net@mail.bellsouth.net \
    --to=blstuart@bellsouth.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).