From owner-freebsd-hackers Mon Jun 5 14:25:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA09412 for hackers-outgoing; Mon, 5 Jun 1995 14:25:23 -0700 Received: from emory.mathcs.emory.edu (emory.mathcs.emory.edu [128.140.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA09401 for ; Mon, 5 Jun 1995 14:25:16 -0700 Received: from bagend.UUCP by emory.mathcs.emory.edu (5.65/Emory_mathcs.4.0.14) via UUCP id AA07337 ; Mon, 5 Jun 95 17:25:11 -0400 Received: by bagend.atl.ga.us (Smail3.1.29.1 #1) id m0sIjQk-0006SmC; Mon, 5 Jun 95 17:11 EDT Message-Id: From: jan@bagend.atl.ga.us (Jan Isley) Subject: Re: latest install adventures To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Mon, 5 Jun 1995 17:11:26 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, jkh@freefall.cdrom.com In-Reply-To: <199506052016.NAA22855@ref.tfs.com> from "Poul-Henning Kamp" at Jun 5, 95 01:16:19 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2772 Sender: hackers-owner@freebsd.org Precedence: bulk Poul-Henning Kamp wrote: > > installing onto *wd1* from a dos partition on *wd0* ... some of > > my problems went away ... I can install after telling it not to > > diddle with the MBR, but it marks the BSD partition bootable and > > unsets the OS/2 BM unbootable... again, BSD is going onto wd1 and > > BM is on wd0 ... should install not do *anything* to wd0 ??? I > > don't care what it does to it's own slice but it should not assume > > anything else about any other slice *or* disk, yes? > So you DO have a FreeBSD slice on the wd0 ? Only if you consider the DOS partition to be a FreeBSD slice, but I do not allways tell sysinstall to mount it. I have the same problems if I do NOT indicated wd0 in fdisk. I do sometimes try to use the hda6 partition as a BSD slice... but not as /. Here is the output from linux fdisk -l: I am running linux to type this but I am *trying* to get converted to FreeBSD. :) Disk /dev/hda: 16 heads, 63 sectors, 2099 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Begin Start End Blocks Id System /dev/hda1 655 655 2099 728280 5 Extended Partition 1 has different physical/logical endings: phys=(1023, 15, 63) logical=(2098, 15, 63) /dev/hda2 4 4 654 328104 6 DOS 16-bit >=32M /dev/hda3 * 1 1 3 1480+ a OS/2 Boot Manager /dev/hda5 655 655 915 131512+ 7 OS/2 HPFS /dev/hda6 916 916 1625 357808+ 7 OS/2 HPFS /dev/hda7 1024 1626 1829 102784+ 83 Linux native /dev/hda8 1024 1830 2033 102784+ 83 Linux native /dev/hda9 1024 2034 2099 33232+ 82 Linux swap Disk /dev/hdb: 16 heads, 38 sectors, 684 cylinders Units = cylinders of 608 * 512 bytes Device Boot Begin Start End Blocks Id System /dev/hdb1 1 1 344 104557 83 Linux native /dev/hdb2 345 345 684 103360 a5 BSD/386 OS/2 Boot Manager has the DOS, OS/2, Linux (hdb1) and BSD (hdb2) partitions marked as bootable... and will boot any of them from the menu, regardless if DOS or Linux fdisk reports that they are active or not. I have Linux LILO installed in the hdb1 partition, not in the MBR. > Try to mark the OS/2 partition active on wd0. This is how I recover from adventures with sysinstall... I boot dos from a floppy and set the Boot Manager (hda3) active, then rebooting gives me the Boot Manager back. After running sysinstall, the BSD partition on hdb2 is marked active, and on hdb1, BM is not marked active ... but the extended partions, 5 through 9 *are* marked active. ??? !!! -- Jan Isley | If you couldn't find any weirdness, jan@bagend.atl.ga.us | maybe we'll just have to make some! - Hobbes