From: Jon Smirl <jonsmirl@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: remove nodes in a directory
Date: Fri, 09 Jan 2004 20:28:16 +0000 [thread overview]
Message-ID: <20040109202817.5427.qmail@web14910.mail.yahoo.com> (raw)
In-Reply-To: <20040109191121.48518.qmail@web14905.mail.yahoo.com>
The init scipts aren't the problem, same problem happens when I remove my kernel
module.
On add I have a rule like this:
REPLACE, KERNEL="card*", NAME="dri/card%n"
This causes the device node to be created in:
/udev/dri/card0
The remove event does not delete this device node.
If I get rid of the rule it works fine.
Where do the add/remove of the device nodes in the udev directory occur? When
this code is removing the device node it needs to transform the name through the
rules first. It should also clean up an empty subdirs.
--- Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Fri, Jan 09, 2004 at 11:11:21AM -0800, Jon Smirl wrote:
>
> > When I stopped udev to switch I noticed that it does not remove /dri/card0.
> I
> > removed the rule that puts card0 in a subdir and it was removed ok. So it
> looks
> > like udev stop is not applying rules for finding things in subdirs.
>
> Do you mean the init script with "stop"? I never tried it :)
>
> udev is not evaluating any rule if you call it with the remove action,
> it asks its data base for the filename. I expect the problem somewhere
> else.
>
> Could you provide the debug for the failing remove action?
>
> thanks,
> Kay
==Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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-01-09 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 19:11 remove nodes in a directory Jon Smirl
2004-01-09 20:10 ` Kay Sievers
2004-01-09 20:12 ` Greg KH
2004-01-09 20:28 ` Jon Smirl [this message]
2004-01-09 20:35 ` Kay Sievers
2004-01-09 20:41 ` Jon Smirl
2004-01-09 20:50 ` Kay Sievers
2004-01-09 21:20 ` Jon Smirl
2004-01-09 23:09 ` Greg KH
2004-01-09 23:47 ` Kay Sievers
2004-01-10 3:07 ` Jon Smirl
2004-01-10 18:49 ` Jon Smirl
2004-01-13 0:59 ` Greg KH
2004-01-13 1:53 ` Jon Smirl
2004-01-13 2:03 ` Greg KH
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=20040109202817.5427.qmail@web14910.mail.yahoo.com \
--to=jonsmirl@yahoo.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 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).