From: corey@hotrod.alph.att.com corey@hotrod.alph.att.com
Subject: Plan9 & OS/2 Boot Manager
Date: Wed, 6 Sep 1995 12:55:42 -0400 [thread overview]
Message-ID: <19950906165542.GtQOpk6s3h30EOLK3Uj0IXS5LIisA42FgzbUWw1IB9c@z> (raw)
In article <Pine.3.89.9509041742.A130-0100000@localhost>,
Michael C. Montero <9fans@cse.psu.edu> wrote:
>I am trying to setup Plan9 on my machine which has OS/2 Boot Manager. I
>currently have a DOS parition and a Linux partition. I followed the
>steps outlined in the documentation for setting up the PC distribution
>(20 megs) of Plan9. However, for some reason the Disk1 is setting itself
>up on the floppy instead of on the partition I left available for Plan9.
>I am NOT trying to make Plan9 part of OS/2 Boot Manager. According to
>the documentation, the DOS partition is supposed to be formatted and
>space is supposed to be left for Plan9. If anyone has any idea of what
>the problem may be or if anyone has gotten around this (in any way)
>please let me know! The only thing I would like is to maintain my DOS
>and Linux partitions and, if possible, not to have to delete my Linux
>partition. The DOS one has been mutilated already.
I ran into exactly the same problem last night. I would guess
that you are using the OS/2 Boot Manager stored in the MBR
and that LILO is installed in the Linux root partition.
In my case I had DOS and Linux loaded and was using LILO in
the MBR. Plan9 was doing the exact same thing you mentioned
and failed to write to my SCSI drive. To solve the problem
I removed LILO from the MBR with DOS fdisk /mbr and I also
removed my Linux partition as I had not allocated space for
Plan9 previously. This solved the problem and I now have Plan9
loaded.
You might be able to get away with just unloading the OS/2
Boot Manager instead of doing what I had to do. i.e deleting
my Caldera (Linux) partition) :-( :-(
One of the problems with Caldera Linux is that Lilo cannot
be installed in the root partition, if you have an all SCSI
system. Don't ask me why, I just read it in the documentation.
When I put Linux back on my machine I will use the loadlin
utilities to boot Linux.
--Corey
>
>Thanks for all your help!
>Mike
>
--
/* Corey Brown (WB0RXQ): 20m, 15m, 2m(146.82) 70cm(443.65) */
/* AT&T NSD | corey@hustler.att.com */
/* Alpharetta, Ga 30202 | attmail!wcbrown */
/* (404)750-8071 | New rays from an ancient sun (JS) */
next reply other threads:[~1995-09-06 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-06 16:55 corey [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-11 10:50 Johnson
1995-09-06 17:46 Will
1995-09-04 21:11 Michael
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=19950906165542.GtQOpk6s3h30EOLK3Uj0IXS5LIisA42FgzbUWw1IB9c@z \
--to=corey@hotrod.alph.att.com \
/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).