From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753462AbYIYF7e (ORCPT ); Thu, 25 Sep 2008 01:59:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751473AbYIYF70 (ORCPT ); Thu, 25 Sep 2008 01:59:26 -0400 Received: from einhorn.in-berlin.de ([192.109.42.8]:49405 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751030AbYIYF7Z (ORCPT ); Thu, 25 Sep 2008 01:59:25 -0400 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <48DB28BB.3090200@s5r6.in-berlin.de> Date: Thu, 25 Sep 2008 07:59:23 +0200 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080722 SeaMonkey/1.1.11 MIME-Version: 1.0 To: Kay Sievers CC: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org Subject: Re: Differend udev names with different kernels References: <20080924200127.GA2452@dose.home.local> <3ae72650809242012r7d144a64l35777f2a7bacbaa0@mail.gmail.com> <48DB1CC4.2040004@s5r6.in-berlin.de> In-Reply-To: <48DB1CC4.2040004@s5r6.in-berlin.de> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I wrote: >> On Wed, Sep 24, 2008 at 13:01, Tino Keitel wrote: >>> My firewire hard disk seems to have different names with different >>> kernels. >>> >>> With 2.6.26.3, it's name is >>> /dev/disk/by-id/ieee1394-0030e001e0006585:00043c:0000. >>> >>> With someting after 2.6.27-rc7, merged with Arjan's fastboot branch, >>> the disk has the same name. > > Then this is a regression of the fastboot patch or whatever. > > I will watch what will happen in 2.6.28-rc. > >>> With 2.6.27-rc7, it is called >>> /dev/disk/by-id/scsi-1WDC_WD10EACS-00D6B0_WD-WCAU41668315. Uh, sorry, I misunderstood. It is a regression of mainline then. > The scsi-* link may not be unique because it may be based on unsuitable > information generated by the SBP-2 bridge device's firmware. ... > I will look into it. -- Stefan Richter -=====-==--- =--= ==--= http://arcgraph.de/sr/