> - if a RHEL 5.6 system is upgraded to 5.7, do existing
> persistent names get changed to the 'user-friendly'
> persistent names?  If so, this would 'break' an existing
> NetWorker configuration, requiring some re-configuration.

Yes and yes, that's what happened to me.

> - do I assume correctly that NetWorker for Linux will be
> able to use these new-format persistent names?

Yes, they work fine.

I fixed it with nsradmin -d /nsr/res/nsrdb (with NetWorker shut down). There 
might be a way to fix the paths via the supported text/web interfaces without 
deleting/recreating the jukebox, with concomitant annoyance in pool directives, 
but I couldn't immediately find it.

> - is there a way to instruct udev to NOT use these new 
>'user-friendly' names in an upgrade situation (which would
> preserve the existing names, and so would NOT 'break' an
> existing NetWorker configuration)?

No idea. I haven't even verified if the names come from kernel or udev, though 
I'd assume the latter. I scanned rpm -q --changelog and the RHEL 5.7 release 
notes and didn't see anything obviously relevant.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER