Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263866AbTE0Prb (ORCPT ); Tue, 27 May 2003 11:47:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263867AbTE0Pra (ORCPT ); Tue, 27 May 2003 11:47:30 -0400 Received: from nat9.steeleye.com ([65.114.3.137]:36102 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S263866AbTE0Pra (ORCPT ); Tue, 27 May 2003 11:47:30 -0400 Subject: Re: [BK PATCHES] add ata scsi driver From: James Bottomley To: Jeff Garzik Cc: Linus Torvalds , Jens Axboe , Linux Kernel In-Reply-To: <20030527155053.GB21744@gtf.org> References: <1054047595.1975.64.camel@mulgrave> <20030527152113.GA21744@gtf.org> <1054049931.1975.129.camel@mulgrave> <20030527155053.GB21744@gtf.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 27 May 2003 12:00:28 -0400 Message-Id: <1054051233.1975.139.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1043 Lines: 23 On Tue, 2003-05-27 at 11:50, Jeff Garzik wrote: > Oh, no question. My main interest is having a persistent id for a > device's media. Then Linux can use that to allow mapping in case device > names or majors change at each boot (and similar situations). Well, OK, that's not an in-kernel issue. My current thought for this is that deriving the unique name can be awfully device specific (even in SCSI there are several fallback methods plus the usual black/white list of things that don't quite return entirely unique objects). Thus, I think the derivation probably belongs in userspace as part of hotplug. Once the unique ID is determined, it could be written to a well known place in the sysfs tree for all the rest of the OS (things like udev for persistent device naming) to use. James - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/