From owner-freebsd-bugs  Sun Jun 18 13:46:35 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA02834
          for bugs-outgoing; Sun, 18 Jun 1995 13:46:35 -0700
Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02828
          for <bugs@FreeBSD.org>; Sun, 18 Jun 1995 13:46:33 -0700
Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18724; Sun, 18 Jun 1995 13:46:27 -0700
Date: Sun, 18 Jun 1995 13:46:26 -0700 (PDT)
From: Howard Lew <hlew@genome.Stanford.EDU>
To: Bruce Evans <bde@zeta.org.au>
cc: bde@zeta.org.au, terry@cs.weber.edu, bugs@FreeBSD.org
Subject: Re: 2.05R panics on boot
In-Reply-To: <199506180538.PAA15480@godzilla.zeta.org.au>
Message-ID: <Pine.SUN.3.91.950618134309.18684D-100000@vegemite.Stanford.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

On Sun, 18 Jun 1995, Bruce Evans wrote:
> It's not clear to me whether this is an installation error.  Why is Ontrack
> managling disks that it isn't on?  Can the problem be fixed by installing
> Ontrack on all disks, or configuring it to only manage the disk(s) that it
> is installed on?

Actually Ontrack does not seem to do anything to disks that it is not on.  A 
pfdisk output (in my last message which should be floating by any second 
now) kind of shows that none of the geometries are changed on my 
non-Ontrack hard drive.