From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 08:47:49 2004 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 5A2E716A4CE for ; Thu, 14 Oct 2004 08:47:49 +0000 (GMT) Received: from sv02.webonaut.com (kirk.webonaut.com [212.41.243.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C4E943D45 for ; Thu, 14 Oct 2004 08:47:48 +0000 (GMT) (envelope-from klammer@webonaut.com) Received: from localhost (localhost [127.0.0.1]) by sv02.webonaut.com (Postfix) with ESMTP id A8AF17642C for ; Thu, 14 Oct 2004 10:47:42 +0200 (CEST) Received: from sv02.webonaut.com ([127.0.0.1]) by localhost (sv02.webonaut.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09129-06 for ; Thu, 14 Oct 2004 10:47:37 +0200 (CEST) Received: from [192.168.0.9] (sisko.webonaut.com [212.41.243.28]) by sv02.webonaut.com (Postfix) with ESMTP id 02FF776428 for ; Thu, 14 Oct 2004 10:47:36 +0200 (CEST) Message-ID: <416E3D29.5040307@webonaut.com> Date: Thu, 14 Oct 2004 10:47:37 +0200 From: Franz Klammer User-Agent: Mozilla Thunderbird 0.8 (X11/20041211) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at webonaut.com Subject: umass -> da device mapping info 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, 14 Oct 2004 08:47:49 -0000 hi! freebsd needs a umass -> da device mapping information. what i mean is the following: after inserting a usb memory stick (as example) the devices pass0, da0 and da0s1 are created. but how i find out what umass device is mapped to the devices above? i suggest a new sysctl variable: dev.umass.0.%mappedto=da0 or better: dev.da.0.%mappedfrom=umass0 or something like this. currently the only command that "tells" me the umass device is "camcontrol devlist -v": umass-sim0 everything i s easy if there is no existing daX device and only one usb mass device is used but in every other case it's very diffcult to write an automated script. that information can also be very usefull in usbd.conf as variable in the attach command not only ${DEVICE} which in case of umassX didn't really exist. franz.