All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: RUN rules to enable/disable printer queues
Date: Fri, 26 Aug 2005 15:50:53 +0000	[thread overview]
Message-ID: <dendou$ocb$1@sea.gmane.org> (raw)
In-Reply-To: <32962.66.92.218.83.1125017033.squirrel@mail.panix.com>

Kay Sievers wrote:
> udev has it's own database to remember the created nodes and symlinks.
> On remove everything that was created with add is removed without a
> explicit rule.

In the future, perhaps it would be possible to add a "destructor" to
the database, a program that would be automatically run before the
device is actually removed.  This would obviate the need for separate
rules.

-- 
====================================
Ian Pilcher                                        i.pilcher@comcast.net
====================================



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-08-26 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  0:43 RUN rules to enable/disable printer queues Zack Weinberg
2005-08-26  1:01 ` Kay Sievers
2005-08-26  3:06 ` Zack Weinberg
2005-08-26 11:46 ` Kay Sievers
2005-08-26 15:50 ` Ian Pilcher [this message]
2005-08-26 19:36 ` Kay Sievers

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='dendou$ocb$1@sea.gmane.org' \
    --to=i.pilcher@comcast.net \
    --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.