linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Patch] udev: new dasd_id tool
Date: Tue, 28 Nov 2006 16:33:28 +0000	[thread overview]
Message-ID: <1164731608.3613.92.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <20061127141551.406c28a1.sameske@de.ibm.com>

On Tue, 2006-11-28 at 17:22 +0100, Volker Sameske wrote:
> > The current multipath already uses the current dasd_id in /lib/udev?
> 
> Yes, the current mp-tools package calls the symlink /sbin/dasd_id
> 
> > Well, we usually don't care about backwards compat in that direction. A
> > udev version can simply require a minimal kernel version, and this
> > should be fine.
> > 
> > But how do we handle people already using the current persistent links?
> > Your new tool creates different names for the same devices on recent
> > kernels, right?
> 
> Yes. If the new uid is available in a distribution dasd_id returns:
> 
> ID_BUSÌw
> ID_TYPE=disk
> ID_SERIAL=IBM.75000000092461.4d00.34
> 
> if not, you'll get:
> 
> ID_BUSÌw
> ID_TYPE=disk
> ID_SERIAL=0X4D34

So, how do we handle possible users who use the old name? Always create
both links? Warn on update?

> > Right, that's always good to avoid.
> So you can see my problem :)

Yes and no, it would be fine in its own package too, I think. But let's
solve the real problems first ...

Thanks,
Kay


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-11-28 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 13:15 [Patch] udev: new dasd_id tool Volker Sameske
2006-11-27 15:52 ` Kay Sievers
2006-11-27 17:05 ` Volker Sameske
2006-11-27 17:41 ` Kay Sievers
2006-11-27 17:53 ` Patrick Mansfield
2006-11-28  8:54 ` Kay Sievers
2006-11-28 15:29 ` Volker Sameske
2006-11-28 15:53 ` Kay Sievers
2006-11-28 16:22 ` Volker Sameske
2006-11-28 16:33 ` Kay Sievers [this message]
2006-11-29  6:55 ` Volker Sameske
2006-11-29  9:11 ` Kay Sievers
2006-11-29 12:03 ` Volker Sameske

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1164731608.3613.92.camel@pim.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).