From owner-freebsd-current Tue Oct 13 09:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09282 for freebsd-current-outgoing; Tue, 13 Oct 1998 09:03:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09277 for ; Tue, 13 Oct 1998 09:03:44 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id JAA20244; Tue, 13 Oct 1998 09:03:13 -0700 (PDT) (envelope-from dhw) Date: Tue, 13 Oct 1998 09:03:13 -0700 (PDT) From: David Wolfskill Message-Id: <199810131603.JAA20244@pau-amma.whistle.com> To: sthaug@nethelp.no, wollman@khavrinen.lcs.mit.edu Subject: Re: bitten 3 times already. Cc: current@FreeBSD.ORG In-Reply-To: <199810131520.LAA08350@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 13 Oct 1998 11:20:31 -0400 (EDT) >From: Garrett Wollman >> + The kernel crash dump is written using CHS addressing. Kernel crash >> + dumps should not be enabled for disks running in LBA mode. >Doesn't belong in a machine-independent manual page. OK.... That leaves a couple of options: * Don't provide such a (machine-dependent) warning, or * Provide one somewhere else. Now, it may well be that anyone running certain flavors of an OS should be expected to know the arcana of each instantiation of the hardware on which it happens to be implemented. If so, I'd appreciate a pointer to such information, since I'm finding PC hardware very strange and prone to peculiar forms of misbehavior. (My prior experience has been mostly with Sun boxen & IBM mainframes.) If not, it would seem that providing a place for warnings of a machine- dependent nature would be a Good Thing. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message