From owner-freebsd-current@FreeBSD.ORG  Tue May  6 00:52:43 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B622837B401; Tue,  6 May 2003 00:52:43 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B8ED543F3F; Tue,  6 May 2003 00:52:42 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h467qfLr051915;
	Tue, 6 May 2003 09:52:41 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Cliff L. Biffle" <cbiffle@safety.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 06 May 2003 00:48:16 PDT."
             <200305060048.16181.cbiffle@safety.net> 
Date: Tue, 06 May 2003 09:52:41 +0200
Message-ID: <51914.1052207561@critter.freebsd.dk>
cc: Doug Barton <DougB@freebsd.org>
cc: current@freebsd.org
Subject: Re: gbde failure attaching /dev/fd0 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2003 07:52:44 -0000

In message <200305060048.16181.cbiffle@safety.net>, "Cliff L. Biffle" writes:

>gbde: Attach to fd0 failed: Provider needed

Sorry, I have not yet released the adaptation class which allows you
to attach floppies and zip drives to the GEOM mesh, I'm having a hard
time finding a suitable way to deal with their "come and go" ability.

For now I would use a malloc backed md(4) device and dd(1) the encrypted
image to the floppy after close.

This also reduces a host of shadow write issues which are far more
severe on floppies than on harddisks.

-- 
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.