On 12/10/2012 03:30 PM, Ted Gould wrote: > On Mon, 2012-12-10 at 14:23 -0500, Stéphane Graber wrote: >> Would the above work for you or do you see any potential problem with >> that or think of a better way to deal with the 12.04->14.04 upgrade >> scenario? > > I think so. And to be further more precise, it really is only someone > who upgrades to 14.04, logs out of their session and back in without > rebooting. If there were a critical issue there, I'd rather just make > it so someone can't log back in to a full session until there's a > reboot. Seems like someone would only do this by mistake in almost all > situations.
Right, the other reason why I didn't want to make upstart just fail to start entirely in such case is for people who for whatever reason are asked to test an older kernel which may not have the feature. Same thing for someone who would run a raring container on a precise host, although userspace would support the feature in such case, they kernel won't. So in such case I think it's best to offer a session with a few restricted features (and have a way to detect it) than just plain fail. > Thanks for working on this Stéphane, very excited about it! Cool, will get back to implementing all that then :) Thanks for the feedback! > --Ted -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: OpenPGP digital signature
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
