The original question:
> Why does Veritas volume manager create device entries for volumes in
> rootdg in /dev/vx/[r]dsk in addition to /dev/vx/[r]dsk/rootdg?
I received two different answers. Take your pick. Neither gives me a
warm fuzzy.
-- From: "Klorese, Roger B.A." <rogerk@triton.veritas.com>Seriously: on other platforms, they were put there before we had disk groups. Since we use a compatible source base where possible, we carry that compatibility but over to Solaris too. -- From: Joe Fu <jfu@enron.com>
During system reboot, there is length limitation on the directory pathname. Therefore Veritas created a link(which is shorter and fits to the system reboot requirement) pointing to the real device which exceeded the length requiremnet during system reboot. /dev/vx/dsk/rootdg is a link. -- Note that neither rootdg volume entries in /dev/vx/dsk or /dev/vx/rootdg/dsk is a link, nor is /dev/vx/rdsk/rootdg.
--
Mark A. Wagner markwag@execpc.com ------------------------------------------------------------------- The internet protocol does not provide a reliable communication facility. There are no acknowledgments either end-to-end or hop-by-hop. There is no error control for data...There are no retransmissions. There is no flow control. - RFC 791
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2
mQCNAzMeWrMAAAEEAOutjvoNxvX1168OPvz69hu9hkhJxxy0yVeJmsLrnjx3gyt6 lqxPtqio5wTHm8v7szRCM6N13SCXDfeMEokXtrMSQcKQV6IT10QQp2GNmSlZcCkV uh6JPGF0bjzH9SQTyeBMVV3+SYp+Y8xQF/Uy1/Z5/LSadz6EX/5W62U6Kh/9AAUR tCBNYXJrIFdhZ25lciA8bWFya3dhZ0BleGVjcGMuY29tPg== =fUQc -----END PGP PUBLIC KEY BLOCK-----
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:51 CDT