WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 2/2] have blktap use a dynamic major

To: "Steven Rostedt" <srostedt@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 2/2] have blktap use a dynamic major
From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
Date: Thu, 28 Sep 2006 12:48:31 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Sep 2006 12:49:28 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=rUr+aQywxjBqvybQw368EDqZEWS5K1vRvMpZX+O2hTF4mRpDbyDu/moJPRsa+8yWtad8LRPquc8RYwPbG6HZBYkzdTXcAwtN6pjTz2CfjSqOlymj7W48ugfXsECld8bSM0QIw3Kjg2tpQKXWjtUHn4hL3w47NvqbXRxq1CR4RVo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <451AA50B.5020507@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <451AA3D8.4030909@xxxxxxxxxx> <451AA50B.5020507@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Applied, thank you.

On 9/27/06, Steven Rostedt <srostedt@xxxxxxxxxx> wrote:
blktap currently uses a hardcoded major of 254 for the device.  This is
not robust in anyway and needs to be dynamic.

Note: it is better not to have the daemon create the node, and have udev
create it instead. But since the daemon currently creates the node
anyway, it is still the way this is done.  That change needs to be made
at another time.

-- Steve

Signed-off-by: Steven Rostedt <srostedt@xxxxxxxxxx>





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel