From owner-freebsd-current Sun Oct 18 19:16:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03393 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:16:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03387 for ; Sun, 18 Oct 1998 19:16:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA02013; Sun, 18 Oct 1998 19:15:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: dan@math.berkeley.edu (Dan Strick) cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 17:46:54 PDT." <199810190046.RAA12702@math.berkeley.edu> Date: Sun, 18 Oct 1998 19:15:56 -0700 Message-ID: <2009.908763356@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. Well, it sounds like the new boot manager (which is not BOOTEASY, even though it looks a bit like it) is in fact broken somehow, even though it works on my test machines (damn!). Could you tell us a bit more about whether this was a dedicated/non-dedicated installation, whether there were other OSes on the disk, etc etc? I really would like to continue using the new boot0 since it's the first time we've had a boot manager for which the sources were compiliable and maintained under the FreeBSD tree, unlike BOOTEASY which was a DOS program getting ever more stale under our umbrella. - Jordan P.S. to Robert: I *told* you we should have made those prompts look more different; people are still confusing it with BOOTEASY! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message