From owner-cvs-all Fri Oct 25 10:14:48 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B000137B401; Fri, 25 Oct 2002 10:14:46 -0700 (PDT) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37ACD43E4A; Fri, 25 Oct 2002 10:14:40 -0700 (PDT) (envelope-from mi+celsius@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (250-217.customer.cloud9.net [168.100.250.217]) by corbulon.video-collage.com (8.12.6/8.12.6) with ESMTP id g9PHEQGx085739 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Fri, 25 Oct 2002 13:14:28 -0400 (EDT) (envelope-from mi+celsius@aldan.algebra.com) Received: from celsius.virtual-estates.com ([172.21.19.243]) by 250-217.customer.cloud9.net (8.12.6/8.12.6) with ESMTP id g9PHG0xm082733; Fri, 25 Oct 2002 13:16:09 -0400 (EDT) (envelope-from mi+celsius@aldan.algebra.com) Content-Type: text/plain; charset="koi8-u" From: Mikhail Teterin To: Poul-Henning Kamp , "M. Warner Losh" Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c write_pc98_disk.c Date: Fri, 25 Oct 2002 19:16:11 +0200 User-Agent: KMail/1.4.3 References: <20131.1035563872@critter.freebsd.dk> In-Reply-To: <20131.1035563872@critter.freebsd.dk> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200210251916.11326.mi+celsius@aldan.algebra.com> X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 25 October 2002 06:37 pm, Poul-Henning Kamp wrote: = 1: It confuses users. The reason why you don't hear much about = this now is that for four years we have installed systems = with consistent names by default. I, actually, find it more confusing that all my partitions were named da0s1X -- the ``s1'' part was repetative, and begged to be taken outside of the parentheses. Somehow, the ``da'' part was not as noticable -- probably, because it (or the ``sd'') was there when I first started using FreeBSD. = 2: It does not reflect what is on the disk, which adds = complexity and failure modes to our software, both userland = kernel and bootcode. But my disk has no other slices! It only has one, which -- for all intents and purposes, that I care about, occupies the entire drive. = 3: Aliasing disk devices is a bad idea. [...] mouse->psm0, da0a->da0s1a, da0s1a->ahc0/3 = 4: /dev/da0a is the legitimate name for a disk which has _only_ = [...] = At typical failuremode here is: "My disk wont boot", "Right = is the FreeBSD slice active in the MBR ?", "There is no = MBR!", "Yes there is", "No there isn't!" etc etc If that is a failure mode, it a communication failure. Something this thread is also showing. You contradict your own point 1: here, however -- there you imply it is only the users, who knew what they were doing, who are affected now. = 5: This entire thing is a bloody bikeshed! Nobody cares about = the fact that we get an Disk IO system which is multi-architecture, = modular, extensible, Giant-free etc etc, instead they focus = on the one little detail they _do_ understand, and make a lot = of noise, just to show how much they are "in the loop"! There was a bikeshed. You demolished it and built a new one, that can house all sorts of machinery, including the widest spread kind of bikes too. That wonderful machinery is yet to show up, but, in the meantime, the less widely used, but still quite popular bikes no longer fit -- and for no good reason, other than they are not the kind you yourself use... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message