Hi Dave, Thanks for your response. It may just be a difference between x86 and SPARC, if that's the case then I can live with that. I'll put together a listing of platforms:paths over next few days as I get b175b ramped up in my lab and send it on to you for the RFE.
- Brian Brian Phipps | Software Engineer | +1.503.495.7716 Oracle World Wide Operations On Oct 21, 2011, at 9:05 AM, Dave Miner wrote: > On 10/20/11 20:06, Brian Phipps wrote: >> Hi All, >> >> Currently, in one of my manifests I'm using the following target definition: >> >> <disk whole_disk="true"> >> <disk_name name="/SYS/MB/HDD0" name_type="receptacle"/> >> <slice name="0" in_zpool="rpool" action="create" force="true"> >> <size val="279gb"/> >> </slice> >> <slice name="1" action="create" force="true"/> >> </disk> >> >> My question is, can I use something more generic than "/SYS/MB/HDD0" for >> the receptacle? Maybe something like "HDD0" since I'm finding that the >> preceding path changes on differing machine types. Some have /SYS/HDD0 >> and some have /SYS/MB/HDD0. >> > > Brian, I believe (based on code inspection) that right now you have to > exactly match the receptacle path. This is one of those new features that > probably needs some shaking out, both in getting consistency on the system > labeling and perhaps us providing some more flexible matching. Do you have > details on the systems that are exhibiting the differences so we can look > into the issue with the platform teams? We'd certainly be happy to consider > an RFE for more flexible matching, though. > > Dave
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
