From owner-freebsd-current@FreeBSD.ORG Thu Mar 24 19:56:38 2005 Return-Path: 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 C20C416A4CE; Thu, 24 Mar 2005 19:56:38 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6477443D49; Thu, 24 Mar 2005 19:56:38 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j2OJuSmm089490; Thu, 24 Mar 2005 13:56:28 -0600 (CST) (envelope-from dan) Date: Thu, 24 Mar 2005 13:56:28 -0600 From: Dan Nelson To: Julian Elischer Message-ID: <20050324195628.GC10908@dan.emsphone.com> References: <1110800717.1296.19.camel@localhost> <200503231411.46948.jhb@FreeBSD.org> <20050323154642.J37251@sasami.jurai.net> <42421D8D.5060502@elischer.org> <20050323205841.N37251@sasami.jurai.net> <77e48641fc04164b4c81cce75c42a38b@FreeBSD.org> <42431806.3060302@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42431806.3060302@elischer.org> X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: Vladimir Grebenschikov cc: "Matthew N. Dodd" cc: "current@freebsd.org" cc: freebsd-mobile@freebsd.org Subject: Re: Reattach/redetect allways connected umass device - is it possible ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 19:56:38 -0000 In the last episode (Mar 24), Julian Elischer said: > John Baldwin wrote: > >On Mar 23, 2005, at 9:00 PM, Matthew N. Dodd wrote: > >>On Wed, 23 Mar 2005, Julian Elischer wrote: > >>>eject should imply a detach.. > >>>i.e. I think your patch should call the detach code from the eject > >>>code. > >> > >>Eject is for devices that support removable media. > > that doesn't mean that an eject shouldn't do all teh work for a > detach as well. I would be extremely surprised if a "camcontrol eject cd0" removed /dev/cd0 :) Eject is for devices whose media can be removed, but the device itself stays. Or are you just saying detach should do an eject (possibly a stop also) first? -- Dan Nelson dnelson@allantgroup.com