From: Matthew Burgess <matthew@linuxfromscratch.org>
To: linux-hotplug@vger.kernel.org
Subject: udev test failures in 069 and 070
Date: Thu, 15 Sep 2005 19:31:11 +0000 [thread overview]
Message-ID: <4329CBFF.9010509@linuxfromscratch.org> (raw)
Hi Kay et al,
Running `make check' on udev-069 (and udev-70) results in two failures
in the newly added santizing tests. I installed `tree' from
http://mama.indstate.edu/users/ice/tree/ in order to hopefully help
debug the problem, I assume that's the correct binary to be using?
Anyway, I think the failures come down to a lack of UTF-8 support
somewhere, but I can't tell whether it's in `echo' (vanilla 5.2.1),
`udev' or something else in my environment. Here's the output:
TEST 127: untrusted string sanitize (don't replace utf8)
device '/block/sda/sda1' expecting node 'uber'
add: error
udev-root/
`-- sda1
0 directories, 1 file
remove: ok
TEST 128: untrusted string sanitize (replace invalid utf8)
device '/block/sda/sda1' expecting node 'replaced'
add: error
udev-root/
`-- sda1
0 directories, 1 file
If it helps at all, here's the corresponding `echo' output:
bash-3.00# /bin/echo -e \\xc3\\xbcber
\xc3\xbcber
bash-3.00# /bin/echo -e \\xef\\xe8garbage
\xef\xe8garbage
My locale is 'en_GB.UTF-8'.
Thanks for any help you can provide,
Matt.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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
next reply other threads:[~2005-09-15 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 19:31 Matthew Burgess [this message]
2005-09-15 21:10 ` udev test failures in 069 and 070 Matthew Burgess
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=4329CBFF.9010509@linuxfromscratch.org \
--to=matthew@linuxfromscratch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.