On 21 February 2012 20:31, Darrell Anderson <humanreadable@...> wrote: >> I'm trying to envision when I or others might want those >> options to appear and what value they add. First, I don't >> think equivalent options with LILO are possible because LILO >> needs to be "rebuilt" after editing the lilo.conf file. >> Normal users can't do that on-the-fly. Similarly, editing >> the GRUB menu.lst file on-the-fly is impossible too. >> >> The only time those options could actually have effect is >> when the user is logged in and using TDE as root. Using TDE >> as root does not bother me although I know some people have >> heart attacks and start frothing with such topics. >> Regardless, the point here is I don't see when those options >> become useful in the TDE shutdown dialog. >> >> As mentioned, what is so challenging as to wait until the >> GRUB menu appears and then selecting the desired option? >> Further, when the default option needs to be changed, then >> somebody with admin privileges can login and edit the >> menu.lst file. >> >> I have both options in my menu.lst file so I can test both >> command line and graphical logins. I am struggling to see >> why those options are in the shutdown dialog when they can't >> be changed anyway by normal users. > > Do we need a bug report to properly resolve this conversation? > > Darrell > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-devel-unsubscribe@... > For additional commands, e-mail: trinity-devel-help@... > Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > yes please. we need a universal method (daemon or otherwise) of controlling all these different mechanisms from one interface. I am holding off on kicker code because I _refuse_ to integrate my kicker with udev or hal. writing it in for every app doesn't seem like the solution, creating a single interface does. Calvin