From owner-freebsd-current Tue Mar 12 5: 8: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4F3F437B402 for ; Tue, 12 Mar 2002 05:07:57 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2CD7Xnp025021; Tue, 12 Mar 2002 14:07:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Rasmus Skaarup Cc: current@FreeBSD.ORG Subject: Re: GEOM code ready for testing In-Reply-To: Your message of "Tue, 12 Mar 2002 14:05:29 +0100." <20020312135947.A19503-100000@skaarup.org> Date: Tue, 12 Mar 2002 14:07:33 +0100 Message-ID: <25020.1015938453@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020312135947.A19503-100000@skaarup.org>, Rasmus Skaarup writes: >> Well, the recognition/configuration issue is not one GEOM magically can >> solve for you, but GEOM promises that if you can recognize it and >> configure it, GEOM will not get in your way for doing what you want. > >But what if the name of the device somehow depended on the ID on the >device? So you could recognize the same disk on multiple hosts, and having >the same name for the device on each host. > >But this should maybe be left up to the method to assign? The methods decide the names of their g_geom and g_providers. If you look in the BSD and MBR modules, you can see how they simply tack a letter or "s%d" onto the name from below. There is nothing to prevent you from creating an entirely new name if you want to. -- 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 freebsd-current" in the body of the message