From owner-freebsd-alpha Wed May 10 19:55:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.cdrom.com [204.216.28.153]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB937B7E4 for ; Wed, 10 May 2000 19:55:31 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA02328 for alpha@freebsd.org; Wed, 10 May 2000 19:39:49 -0700 (PDT) (envelope-from obrien) Date: Wed, 10 May 2000 19:39:49 -0700 From: "David O'Brien" To: alpha@freebsd.org Subject: need help finding when /boot/loader broke Message-ID: <20000510193949.A2311@dragon.nuxi.com> Reply-To: obrien@nuxi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have narrowed down when /boot/loader broke for me. On a current -CURRENT box: cd /sys/boot cvs up -D 5/1/2000 make obj ; make depend ; make all install produces a working loader. Using cvs up -D 5/2/2000 above does not. It would be quite helpful if people could check to see if that is when the loader broke for them. There are two different failures modes people are seeing, and I want to know if they both happen across this time period. P.S. DON'T FORGET to have a backup loader as /boot/loader.good *AND* to update your boot blocks (which allow you specify a different loader than the hardcoded "/boot/loader"). -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message