From owner-freebsd-current Mon Jan 18 21:56:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20381 for freebsd-current-outgoing; Mon, 18 Jan 1999 21:56:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles139.castles.com [208.214.165.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20376 for ; Mon, 18 Jan 1999 21:56:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA01750; Mon, 18 Jan 1999 21:52:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901190552.VAA01750@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 06:48:56 +0100." <19990119064856.A991@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 21:52:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi ! Bad news, make release still produces non bootable floppies. > I cvsupped yesterday evening at 8pm and did a make world and > make release .... > > Now I tried the boot.flp image from the ftp subdir in /R/.... > > First error message > No /boot/loader > Then the typical "boot banner" > 2nd error message > No /kernel > When typing ? > . .. kernel.gz > When typing kernel.gz to load this kernel > invalid format Of course, it's gzipped. > Well, there is _still_ something wron, believe me. The single-floppy install is broken. Use the two-floppy install as I've been encouraging people to do now since the 12th. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message