From owner-freebsd-questions Thu Apr 6 17: 4:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.commlitho.com (medusa.commlitho.com [207.254.73.4]) by hub.freebsd.org (Postfix) with SMTP id 1438037C321 for ; Thu, 6 Apr 2000 17:04:40 -0700 (PDT) (envelope-from patb@commlitho.com) Received: from pc11.commlitho.com [207.254.73.2] by mail.commlitho.com with ESMTP (SMTPD32-4.07) id A606BF0258; Thu, 06 Apr 2000 17:04:22 MST Message-Id: <4.3.1.2.20000406165729.00ae02a0@commlitho.com> X-Sender: patb@commlitho.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 06 Apr 2000 17:04:22 -0700 To: questions@FreeBSD.org From: Patrick Burm Subject: boot loader suddenly appears Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had searched the archives until I had to finally give up. I installed 4.0 fresh using the entire disk but not using the "dangerously dedicated" option. I now wish I had. For some reason, today, after making some changes to rc.conf, powering down and moving the server, it decides to give me that boot manager that looks like this: >> FreeBSD/i386 BOOT Default: 0:da(0,a)/boot/loader boot: And then just sits there. I can hit enter and get it to boot, but it concerns me that a power outage (longer than my UPS can handle) will make the thing sit there waiting for someone to push enter. I have tried fdisk /mbr from a dos disk, I have tried using the fdisk from /stand/sysinstall and marking the partition active and telling it a standard MBR and writing. Nothing will make it go away. Any ideas. Or at least can I give that boot manager a directive to just boot automatically somehow? Help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message