Bart Smaalders wrote: > Mark Carlson wrote: > >> Such a bootpath is not available from OBP, and also Solaris is >> unable to >> make up one for, >> 1) Different disk drivers, 'sd' or 'ssd' can be attached to an >> iSCSI disk >> 2) Different TPGT can be used to access the boot disk which >> causes different device path >> Therefore the property 'bootpath' is needed to record the device path >> which is used to boot/install in last time. The same mechanism is >> in use >> to support Solaris UFS boot on x86. > > Is this really the right model to emulate, given that UFS boot is > obsolete? ZFS boot doesn't require this on x86. > > Encoding the real boot path in a file that's part of the OS image you're > trying to boot seems problematic.
Correct. My previous comment on this was to ask the proposing team to find a better approach. Storing paths such as this breaks systems as soon as a minor configuration change impacts the path. This is a major issue on x86 that has kept OS images from being as portable as they should, and is really something we want to fix as opposed to broadening the impact as you're proposing. >> The Solaris >> Installer will be responsible to update this file during installation >> and upgrade. > > There is no deus ex machina available during OpenSolaris upgrade to > rummage around, updating secret private config files needed to boot. > > Is there really no better way to fix this? I'd like to see some more investigation here. Why can't this path be determined on-the-fly? At worst this should require tasting a couple of possible devices at mountroot time. -jan
