From owner-freebsd-chat Sat Jul 17 17:38:16 1999 Delivered-To: freebsd-chat@freebsd.org Received: from 196-31-98-23.iafrica.com (196-31-98-23.iafrica.com [196.31.98.23]) by hub.freebsd.org (Postfix) with ESMTP id 7D4CC14F7F for ; Sat, 17 Jul 1999 17:37:58 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA13086; Sun, 18 Jul 1999 02:35:42 +0200 (SAST) From: Robert Nordier Message-Id: <199907180035.CAA13086@ceia.nordier.com> Subject: Re: Is possible that our bootblock ... In-Reply-To: <37910EDA.C168A103@giovannelli.it> from Gianmarco Giovannelli at "Jul 18, 1999 01:16:42 am" To: gmarco@giovannelli.it (Gianmarco Giovannelli) Date: Sun, 18 Jul 1999 02:35:39 +0200 (SAST) Cc: chat@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ... that is installed by boot0cfg is not able to boot Linux partition, > even if they are corrected identified ? At least RedHat has taken to installing Linux in extended DOS partitions by default. (I've no idea about other distributions.) Unless you're going to rely on LILO or some other non-standard boot manager, you don't want to do this for two reasons: o Linux has no business being in an extended DOS partition in the first place. o Only primary partitions are startable (bootable). However, you can override this and ensure that a primary partition is used. If that is done, boot0 boots RH 5.2 fine. > It works only with Linux partition installed by Debian (2.1)... All > the other (Redhat 5.2, 6.0 ; Suse 6.1, turbolinux, Mandrake, Slackware > etc etc ) fails to boot and appears the prompt F? ... everything else > (FreeBSD or windows) boot correctly... If you are getting a F? prompt, you're using BootEasy not boot0. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message