From owner-freebsd-arch Sat Oct 26 2:46:50 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E72F37B401 for ; Sat, 26 Oct 2002 02:46:48 -0700 (PDT) Received: from thuvia.demon.co.uk (thuvia.demon.co.uk [193.237.34.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD0843E4A for ; Sat, 26 Oct 2002 02:46:47 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar.thuvia.org (dotar.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.12.3/8.12.3) with ESMTP id g9Q9jMcF053100; Sat, 26 Oct 2002 10:45:22 +0100 (BST) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar.thuvia.org (localhost [IPv6:::1]) by dotar.thuvia.org (8.12.6/8.12.6) with ESMTP id g9Q9jLH5099470; Sat, 26 Oct 2002 10:45:21 +0100 (BST) (envelope-from mark@dotar.thuvia.org) Received: (from mark@localhost) by dotar.thuvia.org (8.12.6/8.12.6/Submit) id g9Q9jL0o099469; Sat, 26 Oct 2002 10:45:21 +0100 (BST) Date: Sat, 26 Oct 2002 10:45:21 +0100 (BST) From: Mark Valentine Message-Id: <200210260945.g9Q9jL0o099469@dotar.thuvia.org> In-Reply-To: <20021026025654.GA23034@edgemaster.zombie.org> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Sean Kelly Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c write_pc98_disk.c Cc: Julian Elischer , Poul-Henning Kamp , "M. Warner Losh" , freebsd-arch@freebsd.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Sean Kelly > Date: Fri 25 Oct, 2002 > Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c write_pc98_disk.c > On Fri, Oct 25, 2002 at 11:15:47PM +0100, Mark Valentine wrote: > ... > > I guess I didn't expect the "compatibility slice" to ever go away... > > I've used FreeBSD since 4.0. I did not know that your "compatibility slice" > method even existed. I've managed to get along without for a long time. "It works until it doesn't..." > > Because DOS doesn't refer to its partition by its index in the MBR partition > > table, and apparently some tools therefore feel free to reorder the table on > > a whim. > > I've never come across any tool that did this. If it does, I would propose > that it is seriously broken. I'll accept that. It was so long ago I can't even remember what did it; maybe I'll find out again when I'm forced to go back to hard coded partition indexes in my fstab. > > ad0s3a is effectively a random place. > > It is almost frightening to me to think that your partition table changes > that much and you aren't aware of what is being moved and to where it is > moved. Other systems on the disk survive it, however. > > Sure, it's only an occasional nuisance. However, it reflects a flaw in > > the system, and is not its only manifestation (see my point about scripts > > and backups). > > What scripts do you need to modify? Once you mount a filesystem, the > scripts refer to the files on it by path. Do you have scripts that play > with the disk devices themselves? Once you modify /etc/fstab, there is > little left that needs done. For myself, generally scripts (actually config files) related to backups; I don't pretend to know where others bury partition device names. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message