On 26/06/07, Eric Boutilier <[EMAIL PROTECTED]> wrote:
On Mon, 25 Jun 2007, Dave Miner wrote:
> Ian Murdock wrote:
>> ...
>>
>> What updates in Solaris require a reboot? For updates that do require
>> a reboot, having the last known good state available in the grub
>> menu would be the way to go here. FWIW, in Linux, we got it down to just
>> the kernel, and even that could be done in place with patches at one
>> point. I.e., that's our benchmark, or at least what people will expect..
>>
> It would be desirable, but your near-term is probably going to need reboots
> for most upgrades, because we haven't attempted to factor the system to avoid
> them...
If desktop/laptop users are the target of the 1st release (and in the
interest of overall project focus) then I'd think this feature
(minimizing reboots after upgrades) would belong in the "do-later"
bucket. My thought here is that when it comes to their desktop/laptop
systems (compared to server users) users are way more obliging about
reboots after upgrades.
Yes, especially since most users are probably used to "The 5,000,467th
security update for Windows has been installed." with only one option:
"Restart Now"...
--
"Less is only more where more is no good." --Frank Lloyd Wright
Shawn Walker, Software and Systems Analyst
[EMAIL PROTECTED] - http://binarycrusader.blogspot.com/
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss
