I'm sponsoring the following self-review case for the Clearview team.
Requested release binding is minor.
Nevada currently has two paths for in.mpathd: a binary in /usr/lib/inet, and
a
/sbin/in.mpathd symlink. The reasons for this have roots in the bad old days
of static linking. For Clearview IPMP (PSARC/2007/272) we need to be able to
start in.mpathd before /usr is mounted, so we proposed reversing these, so
that the binary is in /sbin and the symlink is in /usr/lib/inet.
However, testing has revealed that SVR4 packaging cannot cope with converting
a symlink to a file -- and further, in.mpathd is better suited to the new
/lib/inet directory (which currently houses nwamd). As such, we propose to
place in.mpathd in /lib/inet. Sadly, both the /usr/lib/inet/in.mpathd and
/sbin/in.mpathd paths have been documented in the in.mpathd(1M) manpage over
the years[1] and some third-party and unbundled software is dependent on
those paths (and needs to remain so until in.mpathd is brought under SMF), so
we propose to leave those paths behind as symlinks to /lib/inet/in.mpathd.
[1] This mistake will not be repeated again. That is, the
/lib/inet/in.mpathd
path will not be documented.
--
meem
