From owner-freebsd-alpha Thu Nov 16 11:36:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A57B37B479 for ; Thu, 16 Nov 2000 11:36:44 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA11123; Thu, 16 Nov 2000 11:36:44 -0800 Date: Thu, 16 Nov 2000 11:36:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Polstra Cc: alpha@freebsd.org Subject: Re: 4.2-RC1 failure on 164LX In-Reply-To: <200011161935.eAGJZVL49143@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 16 Nov 2000, John Polstra wrote: > 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. Hmm. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message