Bug 128617 - [powersave] optional do not modify MBR
Summary: [powersave] optional do not modify MBR
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Alpha 1
Hardware: All Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User ZhJd0F0L3x
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-16 07:45 UTC by Alexander Lavrinenko
Modified: 2006-10-18 12:58 UTC (History)
4 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Lavrinenko 2005-10-16 07:45:16 UTC
Right now powersaved modifies mbr upon suspend-to-disk in order to make sure 
that next boot will use proper kernel. This is smart, but I have 2 OSs 
installed - one is SuSE 10.1 and second is WinXP that came with my laptop. 
And after linux s-t-d I'd like to get boot menu again. Please make mbr 
modification upon suspend configurable in YaST and not hardcoded 
in /usr/lib/powersave/scripts/prepare_suspend_to_disk. Right now I had to 
comment out the following line in this file: 
grub-once $NEXT_BOOT > /dev/null 2>&1 
 
Thanks in advance.
Comment 1 Thomas Renninger 2005-10-17 09:34:55 UTC
This is for security reasons. If you modify the filesystem that you suspended while working with an other OS, you are in big trouble and may loose all your data.
I don't like the current solution myself...
We should at least provide a config variable for it (there is already one?)...
Seife?
Comment 2 Danny Al-Gaaf 2005-10-17 19:40:34 UTC
Yes there is: POWERSAVE_BOOT_LOADER in /etc/sysconfig/powersave/common. If you set this to 'OTHER' this should not happen on resume.

Close the bug?
Comment 3 Alexander Lavrinenko 2005-10-18 18:39:17 UTC
Good, just set it to "OTHER". Can we have this option configurable within yast somewhere in "Power Management" section?
Comment 4 Forgotten User ZhJd0F0L3x 2005-10-30 09:25:48 UTC
i really do not want to have this easily configurable without reading the documentation. It really is a great way to lose your data if you boot other operating systems and mount filesystems while one OS is suspended, so i'd like to keep this as an "expert" option and not easily accessible in YaST.

I'll reassign this to PM to decide what to do.
Comment 5 Alexander Lavrinenko 2005-11-02 19:47:50 UTC
I have only 2 OSs installed on my laptop - WinXP Home and suse 10.1. I think it's possible to detect if there's other linux kernel boot option in grub and only in this case only modify bootloader. In my case I'd really like to suspend-to-disk in linux and choose windows on very next boot from grub boot menu instead of booting directly in linux...
Comment 6 Forgotten User ZhJd0F0L3x 2005-11-02 21:11:47 UTC
yes, and i want to prevent exactly this to save unexperienced users from losing your data.
Users who know what they are doing will surely find the bootloader variable and change it to somehting different than GRUB :-)
Comment 7 Andreas Jaeger 2005-11-24 10:26:19 UTC
Let's document this a bit better but I agree with Stefan, we have to avoid dataloss here.
Comment 8 Forgotten User ZhJd0F0L3x 2005-12-05 14:47:24 UTC
Well, i am open to suggestions on how to improve the documentation.
Would a powersave FAQ on opensuse.org make sense?
Comment 9 Andreas Jaeger 2005-12-05 16:10:05 UTC
Yes, such a page would be fine...
Comment 10 Anja Stock 2006-06-13 06:46:10 UTC
Stefan? What is the status here?
Comment 11 Forgotten User ZhJd0F0L3x 2006-06-13 12:32:14 UTC
somebody needs to write the FAQ :-)
Comment 12 Stefan Behlert 2006-10-18 12:39:09 UTC
Has this been done meanwhile?
Comment 13 Forgotten User ZhJd0F0L3x 2006-10-18 12:58:12 UTC
No. Anyway, it's not a bug, it's a feature.