From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261830AbTDHPK3 (for ); Tue, 8 Apr 2003 11:10:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261835AbTDHPK3 (for ); Tue, 8 Apr 2003 11:10:29 -0400 Received: from smtpzilla2.xs4all.nl ([194.109.127.138]:30472 "EHLO smtpzilla2.xs4all.nl") by vger.kernel.org with ESMTP id S261830AbTDHPK2 (for ); Tue, 8 Apr 2003 11:10:28 -0400 Date: Tue, 8 Apr 2003 17:22:00 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: "Kevin P. Fleming" cc: linux-kernel@vger.kernel.org Subject: Re: 64-bit kdev_t - just for playing In-Reply-To: <3E91FEF8.20207@cox.net> Message-ID: References: <200303311541.50200.pbadari@us.ibm.com> <20030403133725.GA14027@win.tue.nl> <3E91FEF8.20207@cox.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, 7 Apr 2003, Kevin P. Fleming wrote: > However, there are significant hurdles to implementing this tool: > > - defining an adequately powerful file format to define the desired naming policy The kernel only exports information, which you can get from sysfs. This will unlikely become a requirement for 2.6, so how this done can still change a bit. > - getting the tool to run _both_ in early-userspace and real-userspace > environments, using the _same_ policy file (or copies thereof) Early-userspace is not that much of a problem, as it only has to map the device information from sysfs to a device name. The required configuration file can be quite simple, every device has a list of properties, which closely resembles sysfs (one property == one value). bye, Roman