From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ben@callahans.org: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of error output]
Date: Wed, 10 Dec 2003 01:07:21 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107102209601277@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107053730019909@msgid-missing>
On Thu, Dec 04, 2003 at 11:43:08AM +0100, Marco d'Itri wrote:
> Debian bug report.
>
> --
> ciao, |
> Marco | [3453 fu5T9iT/VZLEk]
> Date: Wed, 19 Nov 2003 16:06:50 -0500
> From: root <ben@callahans.org>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> Subject: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of
> error output
>
> Package: hotplug
> Version: 0.0.20031008-1
> Severity: normal
>
>
> If there's an unparseable line in /lib/modules/modules.usbmap, usb.agent
> generates hundreds (in my case, over 600) lines of output during the
> boot; specifically, it repeatedly prints out the environment, which
> includes all the functions it has just loaded.
modules.usbmap is generated from depmod. It should NEVER be edited by
hand.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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
prev parent reply other threads:[~2003-12-10 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 10:43 [ben@callahans.org: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of error output] Marco d'Itri
2003-12-10 1:07 ` Greg KH [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=marc-linux-hotplug-107102209601277@msgid-missing \
--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 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).