9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tomas <psycho@pobox.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] booting plan 9 from LILO (was matrox ...)
Date: Thu, 23 May 2002 20:36:46 +0200	[thread overview]
Message-ID: <Pine.GSO.4.44.0205151409480.9465-100000@peppar.cs.umu.se> (raw)
In-Reply-To: <5b0661baed9d9ed48792f5a5cce0d972@plan9.bell-labs.com>

On Sat, 4 May 2002 at 1:35pm, Russ Cox wrote:

> > 2.  I installed plan9 on the 2nd partition of my secondary
> > master (/dev/hdc2 on linux). I made an 'other' entry in
> > lilo.conf and run lilo. When I try to boot to plan9, I get an
> > error that the disk is not a bootable. So what could be going
> > wrong here?
>
> I suspect the problem is that Plan 9 doesn't know how to boot
> from anything but the primary master.  More precisely, I don't
> know how that would work and so I'm not surprised that it
> doesn't.
>
> It could be that we're not dealing with LILO properly at all,
> although I think some people have gotten it working.  I would
> try it myself on my laptop but I'm afraid to wipe my MBR, since
> I'm not 100% sure how to put the Windows 2000 one back.
>
> Anyone want to share LILO success stories?

Yes. I installed r3 a few weeks ago on my second primary
partition. Booting Plan 9 from lilo works without problems, with

other=/dev/hda2
        label=plan9
        table=/dev/hda

in /etc/lilo.conf

I did however run into troubles. Since it's a while ago, I can't
remember exactly how I did things, but I know I partitioned the
drive using Linux's cfdisk and marked the partition as being of
type Plan 9. Then I let the Plan 9 install procedure format the
partition, and all of a sudden there's something wrong with my
partitions. Linux's cfdisk now refuses to start up ("FATAL ERROR:
Bad primary partition 2: Partition ends after end-of-disk"), and
this is what Linux's fdisk tells me:

Disk /dev/hda: 255 heads, 63 sectors, 4111 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       255   2048256    b  Win95 FAT32
/dev/hda2           256       510   2048287+  39  Plan 9
/dev/hda3           511      4112  28931047    f  Win95 Ext'd (LBA)
/dev/hda5           511      4111  28925001    b  Win95 FAT32

I'm blaming Plan 9, since there was no problem with the
partitions before installing Plan 9. I haven't tried to do
anything about it yet, though, since I want to backup my system
before changing anything in the partition table.

I have since installed r4 on another machine, so I'll probably
just wipe the Plan 9 partition and use it for storing mp3s or
something.

/Tomas



  parent reply	other threads:[~2002-05-23 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 17:35 Russ Cox
2002-05-04 18:47 ` Sam
2002-05-04 19:29 ` Quinn Dunkan
2002-05-05  1:31 ` Michael H.Collins
2002-05-23 18:36 ` Tomas [this message]
2002-05-05  6:00 Russ Cox
2002-05-05 12:39 ` Michael H.Collins
2002-05-06  9:13 Fco.J.Ballesteros
2002-05-06 12:04 Jatin Nansi
2002-05-06 13:34 Russ Cox
2002-05-06 14:35 ` Jatin Nansi
2002-05-06 15:26 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=Pine.GSO.4.44.0205151409480.9465-100000@peppar.cs.umu.se \
    --to=psycho@pobox.com \
    --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).