Date: Fri, 25 Oct 2002 15:22:01 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mark Valentine <mark@thuvia.demon.co.uk> Cc: Dag-Erling Smorgrav <des@ofug.org>, jhb@freebsd.org (John Baldwin), cvs-all@freebsd.org, cvs-committers@freebsd.org, Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, Bakul Shah <bakul@bitblocks.com>, Bruce Evans <bde@zeta.org.au> Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_dis Message-ID: <17783.1035552121@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 25 Oct 2002 14:07:36 BST." <200210251307.g9PD7al6069458@dotar.thuvia.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200210251307.g9PD7al6069458@dotar.thuvia.org>, Mark Valentine write
s:
>I guess we differ here in that I'm saying we *should* hide this implementation
>detail by default for consistency with other platforms,
You're making quite an assumption here it seems: BSD disklabels may not
even be present on all platforms, and each partitioning scheme is free
to choose its own naming.
GPT labels for instance seems to use "${disk}${unit}[sp]%d"
And finally you overlook that we may have to forego both MBR and BSD
disklabels on any architecture where we want to use moderately large
storage devices (2^31 * 512 bytes, possibly twice that).
There simply isn't "any consistency with other platforms" to point to
here, if we disregard stuff from the antique hardware society.
Now, this is a nice technicolor bikeshed we got here, but can we
get on with something of real importance, like, making a FreeBSD
5.0-RELEASE ?
Thankyou!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17783.1035552121>