John Henning wrote: > Dear Esteemed Central American Alligators,
I'm actually a Floridian gator, but ... > > Danek Duvall suggested I write to you to mention a user > surprise. > > Years of habit led me to believe that the install procedure > for 2009.06 would automatically reboot. > > The last thing from my window from yesterday was > > Please refer to /tmp/install_log file for details > After reboot it will be located at /var/sadm/system/logs/install_log > > > So when I logged in this morning I thought it was post-reboot. When you say logged in, you don't mean that you logged into the installed system correct? i.e. you're still referring to the console of the installed system ..? (Just want to make sure I'm getting your context.) > I did _not_ understand that it was up to me to do the reboot. > In fact, we were still in the installation environment: > > Filesystem size used avail capacity Mounted on > /devices/ramdisk-root:a > 160M 154M 5.1M 97% / > > > and lots of stuff did not work as expected. > > User error? It was my "fault" for not noticing that this install > procedure relies on me to do the reboot (which was explained > just above the lines I excerpted - but since it differs from > what I was used to, it was easy to miss.) You can modify your install manifest to include the auto-reboot flag so that it reboots automatically after a successful automated installation. > > This problem could have been prevented by, for > example, a generous application of white space > and stars, to draw a box that would have > highlighted that user action is awaited. Please feel free to file an enhancement for this at defect.opensolaris.org under product category installer/autoinstall. Or if you'd like, I can file one for you. thanks, -ethan
