Nicolas Williams wrote: > On Mon, Sep 14, 2009 at 03:27:45PM -0400, Tarl Neustaedter wrote: > >> Nicolas Williams wrote: >> >>> [...] >>> If it's provided by the target then the OBP should pass it to the OS. >>> >>> >> If that's the consensus, we'll modify FWARC 2008/466 to accommodate - >> probably create a new chosen property to export it. Or Solaris could >> fetch the information by itself. >> Solaris setup the bootpath before triggering discovery - logging to the iSCSI target for this case, therefore a correct value is very helpful here. As it is already available during the logging process made by OBP, to pass it to OS would be a good practice. >> >>> That leaves the driver choice. Anything wrong with what I proposed? >>> >> I have no opinion about putting it in the boot_archive. I disagree with >> requiring OBP having to know which driver Solaris is going to use - the >> ... >> > > I never said that the OBP should know which driver Solaris should use. > > I said that the choice of driver should: a) be defaulted, b) be settable > via boot archive and/or boot option. Administering a choice of driver > via boot archive seems reasonable to me. Storing the full boot path in > the boot archive is not (since it is redundant, causing yet one more > place to update when a system's root migrates). > This should be an working approach, I just feel it might be a bit complex as probably needs to figure out the administrative method, which may involve the installer, and other utilities. Since there are 2 options only I think that it is a practical way to do the selection based on trail-and-error with the default 'ssd' driver. If the TPGT value is available, the worst case would be one false attempt to match the path, which is proven with trivial impact to the boot process as the relogin and rediscovery will not take place.
Best regards, Jack > >> And I don't see how to fit it in with the DHCP options. The string >> defined by RFC 4173 does not allow for any expansion of arguments, >> nowhere to fit more information unless we're going to have SPARC Solaris >> requiring special options in DHCP. >> > > I didn't mention DHCP, but it's certainly an option: just add yet > another DHCP option. > > Nico >
