vxconfigd can dynamically map the root/boot volume to use
minor device 0. This would allow /dev/vx/rdsk/rootvolume
to always reference the root volume, no matter which disk
group it is in and no matter what volume was booted from.
--
Ronald S. Karr
tron |-<=>-| [EMAIL PROTECTED]
On November 2, 2007, A Darren Dunham wrote:
>On Fri, Nov 02, 2007 at 10:03:09AM -0400, Hudes, Dana wrote:
>> LU itself doesn't completely support VM. You can use a VM volume as the
>> target instead of a disk slice but its going to put a ufs filesystem in
>> there.
>
>That's not a big deal. Unless you're dealing with some development
>stuff on Solaris, you can only boot from UFS anyway.
>
>> I understand that Veritas provides supporting utilities for use with LU,
>> I haven't used them personally.
>
>I haven't seen that.
>
>One configuration detail used to be an issue, and I don't know if it's
>gone away in recent releases. The 'root' volume used to be special. It
>had a minor number of 0, so it was impossible to have two volumes in a
>diskgroup that could be a valid boot filesystem. That would give an
>LU-like tool more flexibility with VxVM volumes.
>
>--
>Darren Dunham [EMAIL PROTECTED]
>Senior Technical Consultant TAOS http://www.taos.com/
>Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >
>_______________________________________________
>Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
