From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and irda-usb trouble
Date: Wed, 22 Dec 2004 01:23:46 +0000 [thread overview]
Message-ID: <20041222012346.GA13726@kroah.com> (raw)
In-Reply-To: <AC07842E-5395-11D9-8CA9-000D932A03A8@beefstew.net>
On Tue, Dec 21, 2004 at 08:12:43PM -0500, Chris Horn wrote:
>
> I'm sorry: one more message. I mis-typed what I want - and I see from your
> message that I need to clarify my problem. I meant:
>
> "Is there anything I can do to get udev (or whatever is responsible) to NOT
> delete nodes I've added by hand?"
Well, the kernel device that caused that device to be created was
removed from the system (that's what happens with palm devices.) So
udev _has_ to delete the device node as if it didn't, it would be a
security problem.
Just have udev create the node you want for your pilot, and then you
don't have to do anything by hand :)
thanks,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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
next prev parent reply other threads:[~2004-12-22 1:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 21:17 udev and irda-usb trouble Chris Horn
2004-12-21 23:50 ` Kay Sievers
2004-12-22 0:05 ` Chris Horn
2004-12-22 0:26 ` Greg KH
2004-12-22 0:43 ` Chris Horn
2004-12-22 0:52 ` Greg KH
2004-12-22 0:54 ` Chris Horn
2004-12-22 1:01 ` Greg KH
2004-12-22 1:12 ` Chris Horn
2004-12-22 1:23 ` Greg KH [this message]
2004-12-22 1:23 ` Kay Sievers
2004-12-22 1:35 ` Chris Horn
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=20041222012346.GA13726@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.