From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Error in 'udev'
Date: Sat, 09 Apr 2005 14:57:16 +0000 [thread overview]
Message-ID: <1113058636.6996.8.camel@localhost.localdomain> (raw)
In-Reply-To: <4257E0C1.7070307@az1.de>
On Sat, 2005-04-09 at 16:03 +0200, Andreas Schindler wrote:
> There is IMHO an error in the rules parsing code of 'udev'.
> The error shows up parsing multi-line rules. Investigating
> the udev_rules_parse code i found a dereferencing error.
> Please look at the attached mini-tarball. I include a rules
> file that triggers the error.
I can't reproduce this. Your rule is processed as expected here.
What version of udev do you use?
Thanks,
Kay
Btw:
o Produce the diff with "diff -u -p" and send only the
context-diff, no need to send the changed and original files.
o Please don't attach compressed stuff. It's a pain to
look at. Just attach multiple files.
o Mention the version of udev used to create the patch.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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:[~2005-04-09 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 14:03 Error in 'udev' Andreas Schindler
2005-04-09 14:57 ` Kay Sievers [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=1113058636.6996.8.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).