From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/.udev/failed/devices@... problems
Date: Wed, 08 Mar 2006 00:45:24 +0000 [thread overview]
Message-ID: <20060308004524.GB20933@wonderland.linux.it> (raw)
In-Reply-To: <aa83d1ee0602021903k6af15b1ey3302fd3f5e179c8a@mail.gmail.com>
On Mar 08, Liontos Aristotelis <liontos.aristotelis@gmail.com> wrote:
> So is there a way to capture the modprobe error output that you need
> and email it to you ? (in order to use it when you will try to fix
> this ?).
By setting debug logging level, but I already know the error message and
so does everybody who understand how udev works.
--
ciao,
Marco
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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:[~2006-03-08 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 3:03 /dev/.udev/failed/devices@... problems Liontos Aristotelis
2006-02-03 3:31 ` Liontos Aristotelis
2006-02-03 4:17 ` Greg KH
2006-02-03 13:48 ` Liontos Aristotelis
2006-02-18 1:49 ` Greg KH
2006-02-18 7:01 ` Janusz Borowski
2006-02-18 21:50 ` Kay Sievers
2006-02-21 16:23 ` Liontos Aristotelis
2006-03-07 15:30 ` Liontos Aristotelis
2006-03-07 16:21 ` Kay Sievers
2006-03-07 17:16 ` Marco d'Itri
2006-03-07 17:26 ` Kay Sievers
2006-03-08 0:28 ` Liontos Aristotelis
2006-03-08 0:45 ` Marco d'Itri [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=20060308004524.GB20933@wonderland.linux.it \
--to=md@linux.it \
--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).