From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 157 release
Date: Wed, 02 Jun 2010 12:08:57 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1006020806240.10905@lynx> (raw)
In-Reply-To: <1275480242.1695.1.camel@yio.site>
On Wed, 2 Jun 2010, Kay Sievers wrote:
> Here comes a new udev version. Thanks to all who have contributed to
> this release.
i have one minor observation about the test utility. in
udev-test.pl:
if ($rules->{exp_add_error}) {
print " as expected\n";
} else {
print "\n";
system("tree $udev_root"); <-- this line
print "\n";
$error++;
sleep(1);
}
obviously, if something goes wrong during the test, that script
presumes that the "tree" utility is installed. on a stock ubuntu
10.04 system, it isn't so that system() call fails.
is it worth verifying that "tree" is installed first before running
the test?
rday
--
====================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
====================================
next prev parent reply other threads:[~2010-06-02 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 12:04 [ANNOUNCE] udev 157 release Kay Sievers
2010-06-02 12:08 ` Robert P. J. Day [this message]
2010-06-02 12:17 ` Kay Sievers
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=alpine.DEB.2.00.1006020806240.10905@lynx \
--to=rpjday@crashcourse.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