On Thu, Feb 16, 2006 at 06:42:13PM +0100, Michael Biebl wrote: > I noticed another problem with this sanity check. > Let's say the user receives this error message. He then decides to edit > the config file of his boot loader, e.g. grub or lilo. Now powersave > should allow to STD, because on the start the resume parameter would be > used correctly. > But as it is now he has to reboot in order to enable STD, as the > information is read from /proc/commandline.
Yes, i know this and i accepted this inconvenience. Maybe i am a bit too paranoid ;-) > I know that it would get messy to also check the possible boot loader > config files. I just wanted to point out this problem. Right now (with the posted patch), he can temporarily change the config variable to ignore the resume parameter and change it back after the next reboot. If the user knows what he is doing, he can work around this. If he doesn't, he is probably better off just rebooting once to be safe :-) -- Stefan Seyfried \ "I didn't want to write for pay. I QA / R&D Team Mobile Devices \ wanted to be paid for what I write." SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen _______________________________________________ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
