unity-design team mailing list archive

[David Siegel <david.siegel@xxxxxxxxxxxxx>]

Mark Shuttleworth wrote:
> Alex Launi wrote:
> > On Sat, Jul 4, 2009 at 4:03 AM, Mark Shuttleworth <mark@xxxxxxxxxx 
> > <mailto:mark@xxxxxxxxxx>> wrote:
> >
> >     Updates-on-login are interesting, but I think fatally flawed
> >     because of the common requirement to reboot after updates.
> >
> >
> > This is actually the case where update on login works best. Any other 
> > time rebooting is totally interruption. You're working, you need to 
> > decide whether or not rebooting is important enough, and then if you 
> > do decide to reboot, you need to save all of your state, and actually 
> > do the deed. Immediately after boot you don't have this problem. 
> > Instead of starting to work and then being disturbed, you delay 
> > starting until you can really start, without interruption.
>
> 's a fair point.

Also, as there is no user state before login, we can reboot the machine without 
user confirmation. With fast-boot and KMS, we completely remove the pain from 
rebooting after updates -- in fact, the user probably won't even notice the 
reboot (we should suppress startup sounds on the reboot).

David