mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Gary_Lerhaupt@Dell.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] devlabel: consistent device access through symlinking
Date: 07 Sep 2002 15:34:43 +0200	[thread overview]
Message-ID: <1031405684.12089.96.camel@sonja.de.interearth.com> (raw)
In-Reply-To: <20BF5713E14D5B48AA289F72BD372D6812BBB5@AUSXMPC122.aus.amer.dell.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Am Fre, 2002-09-06 um 19.40 schrieb Gary_Lerhaupt@Dell.com:

> Attached is a program I have been working on to allow for consistent access
> to storage devices.  It works by creating symlinks to actual storage device
> names.  When coupled with the UUID of the disk in question, the symlink can
> consistently point to the right data even if the device name changes.
> Devices can thus be referenced by their symlink only and this symlink is
> user-definable.  

Except that for source RPMs sucking big time the stuff is REALLY cool!
I could also see benefits for other devices like HID where the current
ordering is done after a first come - first serve approach where the
minor device numbers follow the order the devices appear on the bus
which is quite easy to mess up and never consistent; Applying your
scheme to and-class devices also would allow to link whatever device
to a fixed device node which could solve many problems as far as
I can see.

Can you elaborate how you retrieve the IDs of a firewire or USB
controller?
 
-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-09-07 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 17:40 Gary_Lerhaupt
2002-09-07 13:34 ` Daniel Egger [this message]

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=1031405684.12089.96.camel@sonja.de.interearth.com \
    --to=degger@fhm.edu \
    --cc=Gary_Lerhaupt@Dell.com \
    --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®