From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tansi.org (ns.km10532-04.keymachine.de [87.118.102.195]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 15 Jan 2010 04:57:38 +0100 (CET) Received: from gatewagner.dyndns.org (84-74-164-239.dclient.hispeed.ch [84.74.164.239]) by tansi.org (Postfix) with ESMTP id 3A1B34250002 for ; Fri, 15 Jan 2010 04:57:38 +0100 (CET) Date: Fri, 15 Jan 2010 04:58:05 +0100 From: Arno Wagner Message-ID: <20100115035805.GA31381@tansi.org> References: <20100113070157.GA13730@maude.comedia.it> <1263378036.3529.3.camel@Koma-Station.localdomain> <20100113131320.GA3993@tansi.org> <4B4DF253.5040201@whgl.uni-frankfurt.de> <20100113172946.GA6329@tansi.org> <4B4F600A.7090107@whgl.uni-frankfurt.de> <20100114214257.GB23608@tansi.org> <4B4F97BD.3020909@whgl.uni-frankfurt.de> <20100114224627.GA24444@tansi.org> <4B4FD035.2030705@whgl.uni-frankfurt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B4FD035.2030705@whgl.uni-frankfurt.de> Subject: Re: [dm-crypt] renaming of device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Fri, Jan 15, 2010 at 03:17:25AM +0100, Sven Eschenberg wrote: > Arno Wagner schrieb: >> On Thu, Jan 14, 2010 at 11:16:29PM +0100, Sven Eschenberg wrote: >>> Hi Arno, >> >>> Concerning udev - you could either modify the configuration for the >>> scsi subsystem, or you could copy it to you own rule file modify it >>> and override debian's defaults. >>> >>> This ways you are a little safer, when the distribution modifies some >>> rules (for some odd reason) and are sure that dmcrypt returns the >>> name you expect. In general this is true for most device names where >>> you have special needs. >>> >>> On my debian there are no rules for creating /dev/scsi/* names, at >>> least not for scsi disks. Might be you are stuck with an older udev >>> or some outdated configuration maybe? >> >> I don't know and do not really have time to investigate now. >> Come to think of it, it could also have some connection to a >> recent kernel upgrade, I am running 2.6.32.2 from kernel.org. >> I did not notice the issue before, so maybe the kernel now also >> creates device files and there was something about a device >> pseudo filesystem or the like in the patchnotes. > > Ah, I guess you unfortunately actiavted kernel managed tmpfs in /dev, > which is an experimental feature. Check for CONFIG_DEVTMPFS in your > kernel config, I bet it is turned on. Good idea, but no. Must be something in the udev configuration after all. Not that I found anything. Or anything in the logs. Hmm. Oh, well. It is not that important. But I really hate this badly documented obscure "automagical" stuff. As soon as anything breaks, it really sucks. On the side of where cryptsetup finds the device for a specific major and minor number, it is indeed a simple recursive directory traversal. Unfortunately it is in libdevmapper.c, i.e. in the system lib of that name. That means it cannot easily be changed. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier