All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Patch to call dev.d scripts also with $SYMLINK
Date: Tue, 05 Oct 2004 21:52:42 +0000	[thread overview]
Message-ID: <20041005215242.GA6147@kroah.com> (raw)
In-Reply-To: <414EDAC1.5050903@redhat.com>

On Tue, Oct 05, 2004 at 11:39:33PM +0200, Kay Sievers wrote:
> On Tue, Oct 05, 2004 at 02:18:44PM -0700, Greg KH wrote:
> > On Mon, Sep 20, 2004 at 03:27:29PM +0200, Harald Hoyer wrote:
> > > especially useful to set pam_console ownerships for e.g. /dev/cdrom, which 
> > > is a symlink to the $DEVNAME.
> > 
> > Hm, this patch doesn't apply anymore.  Care to redo it?
> 
> Why not just ask udevinfo for the symlinks pointing to the device node?
> That was the original idea, why we didn't put this in the dev.d/
> environment.
> 
>   [kay@pim ~]$ udevinfo -q symlink -n /dev/hdc
>   cdrom

Ah, even better.  Glad I didn't apply it :)

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-05 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 13:27 Patch to call dev.d scripts also with $SYMLINK Harald Hoyer
2004-10-05 21:18 ` Greg KH
2004-10-05 21:39 ` Kay Sievers
2004-10-05 21:52 ` Greg KH [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=20041005215242.GA6147@kroah.com \
    --to=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.