Brian Cameron wrote: > > I updated the timeout for this case for November 10, 2009. > > This case has been "waiting need spec" for some time. The project > team has provided updated materials which they believe address > the outstanding issues. See attached. > > I also updated the case materials directory with the new one-pager > document named "onepager-fast-reboot.txt" (and renamed the old one to > "onepager-old.txt"). I updated the IAM file so it says "waiting > fast-track" instead of "waiting need spec".
Over all that sounds good, I'm particularly happy that this will be added in the upstream ConsoleKit. > A list of available BEs will also be provied in the GUI. If users > select a BE which is different from the default one, the restart > dialog will ask ConsoleKit to reboot into the selected BE. ConsoleKit > will check solaris.system.shutdown to identify if the user has enough > privilege. If so, ConsoleKit will use "bootadm set-menu default=n" > to update the default BE and then do a reboot. This part concerns me a little. It is quite a different policy decision to be able to reboot the existing BE than to change the default one. Yes the user could just select the alternate one from the GRUB menu in most cases. However I'd prefer to see an additional authorisation added for this check, it can be in the default set provided by the "Console User" property. I suggest something like "solaris.system.bootadm". This is similar to how suspend/resume has been dealt with. -- Darren J Moffat
