From owner-freebsd-current@FreeBSD.ORG  Thu Mar 24 20:13:43 2005
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 ED4FD16A4CE; Thu, 24 Mar 2005 20:13:43 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7DD4B43D31; Thu, 24 Mar 2005 20:13:43 +0000 (GMT)
	(envelope-from scottl@samsco.org)
Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j2OKC2Mm075663;
	Thu, 24 Mar 2005 13:12:02 -0700 (MST)
	(envelope-from scottl@samsco.org)
Message-ID: <42431EC6.1020303@samsco.org>
Date: Thu, 24 Mar 2005 13:10:46 -0700
From: Scott Long <scottl@samsco.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dan Nelson <dnelson@allantgroup.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>
	<20050324195628.GC10908@dan.emsphone.com>
In-Reply-To: <20050324195628.GC10908@dan.emsphone.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org
cc: Vladimir Grebenschikov <vova@fbsd.ru>
cc: freebsd-mobile@freebsd.org
cc: Julian Elischer <julian@elischer.org>
cc: "Matthew N. Dodd" <mdodd@freebsd.org>
cc: "current@freebsd.org" <current@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
	<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: Thu, 24 Mar 2005 20:13:44 -0000

Dan Nelson wrote:
> 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?
> 

Let me reinforce this since there seems to be quite a bit of confusion.
The 'stop' and 'eject' actions of camcontrol operate in the context of
how they are defined in the SCSI world.  That is, they send a particular
command to the target that makes the target do the intended action.
They do __not__ imply that CAM will detach the logical device, flush the
buffer-cache, etc.  There is a whole lot less magic here than I think
that everyone is hoping for.

Scott