From owner-freebsd-alpha Wed Oct 11 17:52:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AD92337B502 for ; Wed, 11 Oct 2000 17:52:30 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA03723; Wed, 11 Oct 2000 20:52:29 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9C0qT677201; Wed, 11 Oct 2000 20:52:29 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 11 Oct 2000 20:52:29 -0400 (EDT) To: Terry Lambert Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem with FreeBSD on AlphaStation 255/233 In-Reply-To: <200010120048.RAA10968@usr09.primenet.com> References: <14820.25415.513392.588558@grasshopper.cs.duke.edu> <200010120048.RAA10968@usr09.primenet.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14821.2733.354190.309985@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert writes: > How is this possible? Same question: is the install process broken, > in that it actually permits this to happen, ever? I think both have occured in the past. I know that at least the latter was possible when somebody booted from floppies & installed x86 bins from the cd. Basically, I never run the install tools on alpha & I don't keep up w/bugs in said tools. Its more likely the boot loader is broken. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message