Date: Wed, 16 Apr 2003 23:06:02 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sbin/sunlabel Makefile Message-ID: <45523.1050527162@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 16 Apr 2003 23:55:06 %2B0300." <20030416205506.GB10181@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030416205506.GB10181@sunbay.com>, Ruslan Ermilov writes: >disklabel will soon be enabled on sparc64 too, once >the endianness fixes are committed. This is needed >to cross-release architectures that use BSD labels, >that is i386 and Alpha. I guess we should paint the big picture, just to make sure we don't get a confused bikeshed at this point. The plan/goal, such as it is: All disk partition programs, should work on all architectures/endianess. (presently: fdisk, disklabel, sunlabel, gpt) Some of these programs will need to grow "-m $architecture" like arguments, for instance disklabel which needs to be able to tell the difference between an i386 and alpha layout. fdisk(8) may also need to learn i386/pc98. Make release tools will learn to DTRT, this may include KLD'ing GEOM modules. As for the naming of bsdlabel/disklabel. I am all for a repo-copy disklabel->bsdlabel, with a compatibility symlink on alpha/i386/pc98. Thinking a bit more about it, I think we should not symlink anything else to that name on other architectures, but rather have a small shellscript which explains what the tool is called on the present platform. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45523.1050527162>