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 ; Sun, 10 Jan 2010 16:16:44 +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 4DCD3243069A for ; Sun, 10 Jan 2010 16:16:44 +0100 (CET) Date: Sun, 10 Jan 2010 16:16:59 +0100 From: Arno Wagner Message-ID: <20100110151659.GA2635@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dm-crypt] renaming of device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Cryptsetup seems to report the device in /dev/scsi/* if they are present, instead of the device name mappings were created with. So I created with /dev/sdd and status tells me I have /dev/scsi/sdh4-0c0i0l0, which is really a problem because it could cause me to confuse devices and map them twice or the like. Is there an easy way to map this back or turn off this behaviour or list both device names? What I do at the moment is to look at major and minor of the reported device and than look up which traditional device this matches. If this is a fundamental problem, I will likely write a wrapper (something like crypt-status) that does the lookup for me, but maybe there is an easier solution? 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