From owner-freebsd-alpha Thu Nov 16 16:54: 2 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 BC35F37B4C5 for ; Thu, 16 Nov 2000 16:53:59 -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 QAA12482; Thu, 16 Nov 2000 16:53:28 -0800 Date: Thu, 16 Nov 2000 16:53:26 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Paul Halliday Cc: alpha@FreeBSD.ORG Subject: Re: Alpha PC164, #two. In-Reply-To: <3A147B9B.C200E0C1@penix.org> 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 Got me on this one, other than somebody was using this beast for linux at one point. > Matthew Jacob wrote: > > > > Hmm. I'm a bit unclear on what you've done. Where's your root supposed to be? > > What did you add? > > [07:22pm]-root@dissent# cat fs.out > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0a 992239 42874 869986 5% / > /dev/da0e 299163 1 275229 0% /home > /dev/ad0e 1006351 512010 413833 55% /usr > /dev/ad1e 517631 168 476053 0% /var > procfs 8 8 0 100% /proc > > Did you notice all of the strange characters in the dmesg output? not to > mention tons of words mispelled. > It makes no sense. also, near the end of that output, (which was a > single `dmesg >dmesg.out`) there is some info on da0: > syncing disks... 3 2 > done > Uptime: 5m37s > (da0:ahc0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 > (da0:ahc0:0:0:0): Invalid command operation code > Unrecognized boot flag '0'. > > ...confused.... > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message