From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug-light
Date: Mon, 27 Jun 2005 03:58:01 +0000 [thread overview]
Message-ID: <42BF7949.2070204@ums.usu.ru> (raw)
In-Reply-To: <20050626212149.GA16474@wonderland.linux.it>
Marco d'Itri wrote:
>I uploaded to http://www.bofh.it/~md/debian/ my set of *.rc and *.agent
>hotplug scripts, some based on the original ones and some written by me
>from scratch.
>With the goal of making them as simple as possible, I removed from the
>original scripts any support for 2.4 kernels and code made obsolete by
>udev, like waiting for sysfs files and the whole /sbin/hotplug.
>Please comment.
>
>
Thanks! Comments are below.
The original hotplug scripts have "dmfe" blacklisted. Your scripts
don't. Why?
Neither set of the scripts has "8139cp" blacklisted. Shame on me, I
still cannot test that 8139cp and 8139too work together, and I don't
know the most relevant mailing list to ask that.
As to buffering in logger.agent to avoid interleaving events in the log,
I used the following approach: if there is a SEQNUM, log each event into
its own file: event.$SQENUM.
+1 to the proposal to move net.agent out of the package, into
distro-specific initscripts.
Not sure about ide-generic in ide.rc. Any real use case for it?
In ieee1394.rc, there is a cosmetic typo probably caused by
copy-and-paste from input.rc. s/input/ieee1394/
Also serio.agent mentions ieee1394.
modalias.rc and pnp.rc don't (and can't) handle blacklists. I propose
putting a note in the README upon this subject (possibly mentioning the
relevant backlist support in module-init-tools), because this can load
watchdogs. Anyway, I feel uncomfortable with two blacklists.
--
Alexander E. Patrakov
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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:[~2005-06-27 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 21:21 hotplug-light Marco d'Itri
2005-06-27 3:58 ` Alexander E. Patrakov [this message]
2005-06-28 8:37 ` hotplug-light Marco d'Itri
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=42BF7949.2070204@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).