Bug 790321

Summary:	Document supported hex encoding of blacklisted characters used in device/symlink names
Product:	Red Hat Enterprise Linux 6	Reporter:	Peter Rajnoha <prajnoha>
Component:	udev	Assignee:	Harald Hoyer <harald>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	low
Version:	6.3	CC:	agk, azelinka, ddumas, harald
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The udev(7) man page does not document the hex encoding of blacklisted characters used in device/symlink names. Consequence: Fix: Added a paragraph in the SYMLINK section of the udev(7) man page about character encoding. Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 10:28:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Rajnoha 2012-02-14 09:08:37 UTC

Please, document supported hex encoding for device/symlink names in the udev manpage so we can refer to it and so any users are aware of it.

Comment 1 RHEL Program Management 2012-05-03 05:13:48 UTC

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 2 Kay Sievers 2012-07-02 01:40:08 UTC

Added upstream:
  http://cgit.freedesktop.org/systemd/systemd/commit/?id=b1239c3fb3d19ff7273a8e5ead5c42f055d10b92

Comment 10 errata-xmlrpc 2013-02-21 10:28:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0435.html