Tarl Neustaedter wrote: > The knowledge of which driver to use within Solaris > isn't needed until after this stage - so I don't think it belongs in the > boot command in the first place.
This is correct... and storing such driver info somewhere where a special program needs to update it is just plain broken. Solaris should be passed the _external_ info about its boot drive - and then should dynamically figure out how to talk to that external device. Any other approach will break when drivers change, paths to devices change, etc. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
