mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: Andrej.Borsenkow@mow.siemens.ru (Borsenkow Andrej)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Persistent device numbers
Date: Thu, 2 Aug 2001 12:20:35 +0200	[thread overview]
Message-ID: <200108021020.f72AKZC17605@ns.caldera.de> (raw)
In-Reply-To: <000901c11b1c$a87b1f40$21c9ca95@mow.siemens.ru>

In article <000901c11b1c$a87b1f40$21c9ca95@mow.siemens.ru> you wrote:
> As far as I understand, currently kernel assigns device numbers dynamically.
> It means, that actual, user visible, controller/drive name may change if
>
> - hardware configuaration is changed (added ot removed controller, added or
> removed drive)
>
> - for some reasons order of initialisation in kernel changes (which may
> result in nasty surprise after update)
>
> Moreover, it near to impossible to know which name device gets in advance
> (or why it gets this name).
>
> Most commercial systems (O.K. those I looked into) have some sort of logical
> device numbering that assigns fixed name based on some unique hardware
> address (cf /etc/path_to_inst in Solaris). Hardware address usually is a
> path needed to access device - i.e. Bus/Slot/Channel[/drive id], so that you
> can set
>
> PCI0/Slot3/Channel1 == eth3
>
> and this never changes if you add or remove any card.
>
> Do I miss something and Linux has such mechanism?

For some device-types this is provided be userspace tools.  E.g. LVM
provides persistan names for it's deice by stroing name and UUID on disk,
'normal' filesystems can be mounted by UUID or label and Andi Kleen has
a tool that allows naming network interfaces by MAC addresses.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  parent reply	other threads:[~2001-08-02 10:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  6:30 Borsenkow Andrej
2001-08-02  9:50 ` Chris Wedgwood
2001-08-02 10:20 ` Christoph Hellwig [this message]
2001-08-02 17:06   ` Greg KH
2001-08-02 14:37 ` Alan Cox
2001-08-02 20:05   ` Kurt Garloff
2001-08-08  7:27   ` Borsenkow Andrej
     [not found] <mailman.996733981.23626.linux-kernel2news@redhat.com>
2001-08-02 17:15 ` Pete Zaitcev

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=200108021020.f72AKZC17605@ns.caldera.de \
    --to=hch@ns.caldera.de \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®