From owner-freebsd-questions Wed Mar 18 21:01:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14936 for freebsd-questions-outgoing; Wed, 18 Mar 1998 21:01:34 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14882 for ; Wed, 18 Mar 1998 21:01:21 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id VAA04537; Wed, 18 Mar 1998 21:01:17 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 18 Mar 1998 21:01:17 -0800 (PST) From: Doug White Reply-To: Doug White To: Mike Mann cc: freebsd-questions@FreeBSD.ORG Subject: Re: dual boot on wd0: fbsd(old)/fbsd(mew) In-Reply-To: <199803182121.VAA08029@avalon.netcom.net.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Mar 1998, Mike Mann wrote: > >Our boot blocks are pretty dumb; it searches for the first slice with the > >correct type and boots it. You won't be able to boot wd0s4 unless you > >disable wd0s2 first. > > Sorry if this is a silly question (I'm not entirely sure what 'type' > means in this context) but I'm wondering if this answer applies to my > configuration where I have both FreeBSD and Linux installed on my > second HD. > > FreeBSD sees the disc as: > > Name Ptype Desc Subtype > wd3s1 2 fat 6 <-DOS d: > wd3s2 3 freebsd 165 <-FreeBSD > wd3s3 4 extended 5 <-Linux > > and Linux sees wd3s3 as a succession of partitions named hdd5 to hdd9. > > FreeBSD boots and works perfectly but I've been unable to boot Linux > since installing it. The FreeBSD boot manager doesn't seem to be able > to see the Linux partition, OS-BS doesn't seem to be able to boot from > a second disc and the Linux LILO boot manager failed to install (don't > know why yet). What is the `freebsd boot manager'? booteasy? no clue about the rest. Most systems probably won't recognize a DOS extended partition as actually bootable though, it goes against the usual DOS universe. My suggestion would be to migrate it to a native Linux partition and try that. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message