From: Jesse Stockall <stockall@magma.ca>
To: linux-hotplug@vger.kernel.org
Subject: Re: Log actions releated to /etc/dev.d scripts
Date: Fri, 15 Oct 2004 18:11:35 +0000 [thread overview]
Message-ID: <1097863895.5114.54.camel@homer.blizzard.org> (raw)
In-Reply-To: <1097845120.5114.32.camel@homer.blizzard.org>
On Fri, 2004-10-15 at 13:54, Kay Sievers wrote:
>
> Maybe it is disabled on your distribution, no on mine.
>
Right, both Gentoo and Debian have it disabled, so I assumed that most
others did too.
> The logged messages are the absolute minimum. Everything else is
> "development debug" only.
>
> If it's really needed we may introduce a debug-level value in the
> config instead of the debug-switch, but that will increase the size
> of the udev binary.
>
Well increasing the size isn't really a good thing, but I can foresee a
need for this type of information to be available to users as the
distros move to udev and the /etc/dev.d scripts. However perhaps this
can wait till others start clamouring for it.
Jesse
-------------------------------------------------------
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
prev parent reply other threads:[~2004-10-15 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 12:58 Log actions releated to /etc/dev.d scripts Jesse Stockall
2004-10-15 17:06 ` Kay Sievers
2004-10-15 17:26 ` Jesse Stockall
2004-10-15 17:54 ` Kay Sievers
2004-10-15 18:11 ` Jesse Stockall [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=1097863895.5114.54.camel@homer.blizzard.org \
--to=stockall@magma.ca \
--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).