From owner-freebsd-alpha Thu Nov 16 11:35:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2F10B37B479 for ; Thu, 16 Nov 2000 11:35:35 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA26452; Thu, 16 Nov 2000 11:35:32 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAGJZVL49143; Thu, 16 Nov 2000 11:35:31 -0800 (PST) (envelope-from jdp) Date: Thu, 16 Nov 2000 11:35:31 -0800 (PST) Message-Id: <200011161935.eAGJZVL49143@vashon.polstra.com> To: alpha@freebsd.org From: John Polstra Cc: mjacob@feral.com Subject: Re: 4.2-RC1 failure on 164LX In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , Matthew Jacob wrote: > > > > What I had been thinking of is taking boot.flp and copying all 3MB > > > to the head of a SCSI or IDE disk and booting that on your 164LX. > > > > Hrm, I'd love to help but I don't think I can take it quite that far. > > :-( > > Okay. Whatever you can do. We suck right now. I don't know whether this is useful info or not, but the -stable from Oct. 31 which is installed on my hard drive boots fine using -current's loader. "Huh?" OK, I have a dual boot setup with -current on da0a and -stable on da0f. So when I boot, -current's loader always gets control. Then I can make it boot -stable like this: unload set currdev=disk0f boot /kernel That works reliably. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message