Message-ID: <3A9185C1.E78A195C@uswest.net>
From: Debbie Padgett <puyallupwa@uswest.net>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.minix
Subject: Re: partition whoes post-minix install
References: <96k7ac$hj5$2@woodrow.ucdavis.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 54
Date: Mon, 19 Feb 2001 12:44:49 -0800
NNTP-Posting-Host: 63.228.103.158
X-Trace: news.uswest.net 982615127 63.228.103.158 (Mon, 19 Feb 2001 14:38:47 CST)
NNTP-Posting-Date: Mon, 19 Feb 2001 14:38:47 CST
Path: news.adfa.edu.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!news.mel.connect.com.au!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-out.uswest.net!news.uswest.net.POSTED!not-for-mail
Xref: news.adfa.edu.au comp.os.minix:36899

    First if you installed the linux boot loader (probably lilo) in the master boot
sector, you should be able to use it to call the minix boot loader.  If you are
using the lilo boot loader you can add the lines:

other=/dev/hdxx
    label=minix
    table=/dev/hdx

to the bottem of your /etc/lilo.conf file where is says hdxx put the letter linux
assigns the drive in the first x and the linux assigned partition number in the
second x.  Where it says /dev/hdx just put the drive letter in place of the x do
*not* put the partiton number after it.  And then run /sbin/lilo.  This will work
with Red Hat linux 6 and 7 for sure,  and probably any other distribution using
lilo.  If your not using lilo then your on your own here.  Try the man pages.

    To check what what drive minix is on or to see what linux calls in use your
fdisk utility.  Red hat has one called cfdisk.  It would work well for this.  Maby
you have maby not type cfdisk to find out.  P.S. Linux may call minux partitions
'old linux'.

    For the second part you must change the 'rootdev' and the 'ramimagedev'
variables to the minix name for the minux partition in the boot monitor.  To view
the settings type 'set', to change them type 'thevariablename = partitionname'  (ex.
rootdev = hd3a).  You can set rootdev=ram and minix will put part or all of the
rootdev on a ram drive but minix will not save any changes made to the root device
will you leave minix automaticaly.  You would have mount the root filesystem to some
point other than /,  a good place would be /mnt, and copy root to it (cp / /mnt) to
save changes.  To find what the partition's name is use 'part'.

Leon Sol Levy wrote:

> i was wondering how i could go about fixing this problem:
>
> i installed minix on a partition i made in the middle of my HD like so:
>
> [windoze][minix][fat32]
>
> and all was well.  i installed minix on hd2 and was able to get it going without
> any trouble.
>
> then i felt compelled to put linux on there, so i made some more slices and
> dices to my HD like this
>
> [windoze][minix][fat32][linux]
>
> and now i cant get minix to boot without a boot disk.  after i made the new
> partition (with FIPS), minix is now on hd3 for  some reason.  what can i tell
> the minix boot program to "boot" since minix=(=,MINIX) {boot} no longer works?
>
> thankS
>
> --
> -leon (in the dungeon of EUII @ UC Davis)

