[opensuse] No grub menu in11.1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, That's it, I get no grub menu (on 11.1). The system boots automatically, but I can not read the screen, it is so fast. I believe that I have this since some time ago, that hibernation failed on restore, and it has left grub set up to auto-boot on one of the entries, and has not replaced the original grub setting because the restore crashed. I'm unsure on how to replace whatever changed in grub, because I don't know what hibernation to disk changes. It is not menu.lst, I think. - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklOzFQACgkQU92UU+smfQUdVQCfT1TEDtVlkYX7IYBmIhDrx0G/ s98An2MHpYzSYJh8ZgLitLBPMo6xVj39 =eKO0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-12-22 at 00:08 +0100, Carlos E. R. wrote:
That's it, I get no grub menu (on 11.1). The system boots automatically, but I can not read the screen, it is so fast.
Can you not set the timeout in menu.list? timeout=5 or something of the type. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael S. Dunsavage wrote:
On Mon, 2008-12-22 at 00:08 +0100, Carlos E. R. wrote:
That's it, I get no grub menu (on 11.1). The system boots automatically, but I can not read the screen, it is so fast.
Can you not set the timeout in menu.list?
timeout=5 or something of the type.
The timeout is and was 8. The menu is ignored: what the screen flashes is not the menu, is some text with the entry that will boot. - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklO3xUACgkQU92UU+smfQWSOACgibmOHzSsvc2zl07B8ThLemEB imYAnjz7glS9NvPI+CRxNwxhv0qsjv26 =Br2a -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The timeout is and was 8. The menu is ignored: what the screen flashes is not the menu, is some text with the entry that will boot.
Could the pause key stop it maybe? I'm not sure if it will pause there or not, but maybe you can hit print screen quick and get it to print out. Have you tried reconfiguring grub again and see if that works? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael S. Dunsavage wrote:
The timeout is and was 8. The menu is ignored: what the screen flashes is not the menu, is some text with the entry that will boot.
Could the pause key stop it maybe? I'm not sure if it will pause there or not, but maybe you can hit print screen quick and get it to print out.
I doubt it, it is too fast. And print would probably fail, nowdays I have a network printer. Anyway, what it displays is the expected text after suspend to disk: it changes grub somehow so that the menu is ignored and boots the same kernel that is currently running.
Have you tried reconfiguring grub again and see if that works?
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it. - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklO7rQACgkQU92UU+smfQV26wCdEEOwwrglGLtT+DS3ZQUVJ2CC 8CMAn3dRp57/kzQlgFRlX3SkH+2+N1+D =zQ52 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael S. Dunsavage wrote:
The timeout is and was 8. The menu is ignored: what the screen flashes is not the menu, is some text with the entry that will boot.
Could the pause key stop it maybe? I'm not sure if it will pause there or not, but maybe you can hit print screen quick and get it to print out.
I doubt it, it is too fast. And print would probably fail, nowdays I have a network printer. Anyway, what it displays is the expected text after suspend to disk: it changes grub somehow so that the menu is ignored and boots the same kernel that is currently running.
Have you tried reconfiguring grub again and see if that works?
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it. - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklO7rQACgkQU92UU+smfQV26wCdEEOwwrglGLtT+DS3ZQUVJ2CC 8CMAn3dRp57/kzQlgFRlX3SkH+2+N1+D =zQ52 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-12-22 at 02:34 +0100, Carlos E. R. wrote:
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it.
I did a quick Google search, since I don't have a notebook and I don't hibernate my PC's. http://mandrivausers.org/index.php?showtopic=43595 http://forums.opensuse.org/archives/sf-archives/archives-install-boot/340152... http://manpages.ubuntu.com/manpages/dapper/man8/hibernate.8.h (look @ the -g switch) seems like it could help you. In general it seems that hibernate to disk is putting an image on the drive and telling grub to just load that. Possibly fixing it would be to do a complete hard shut down. So, possibly shutdown -h NOW or something of that nature. Hope that helps. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/22 Michael S. Dunsavage
On Mon, 2008-12-22 at 02:34 +0100, Carlos E. R. wrote:
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it.
You can prevent 'resume' simply by altering the resume device and writing 'noresume' there. The thing is a red herring though. There's a feature in GRUB that lets you tell it which option to boot up, it's saved to a disk block, similarly GRUB can change it's default to the last booted kernel. That's what GRUB will be reading, and instant booting from. Resume occurs later in kernel boot, and (unfortunately) you can screw things up royally by booting into a different OS inbetween. Perhaps that was changed, conflating the two features in end user mind, but if you are shutting the machine down to power off, stuff is not saved to resume space. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 02:12 -0000, Rob OpenSuSE wrote:
2008/12/22 Michael S. Dunsavage
: On Mon, 2008-12-22 at 02:34 +0100, Carlos E. R. wrote:
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it.
You can prevent 'resume' simply by altering the resume device and writing 'noresume' there.
_if_ menu.lst is read, and I think it isn't.
The thing is a red herring though. There's a feature in GRUB that lets you tell it which option to boot up, it's saved to a disk block, similarly GRUB can change it's default to the last booted kernel.
Ah. This looks like it. Do you know the name of this feature, so that I can search for it in the documentation?
That's what GRUB will be reading, and instant booting from. Resume occurs later in kernel boot, and (unfortunately) you can screw things up royally by booting into a different OS inbetween.
Ha! I know: I've been bitten by that one. Twice. Or having several grub menus and starting the wrong one... and remember that usually the same swap partition is shared by different linuxes. Ouch, it hurts. Booting to a totally different OS can be "safe", though.
Perhaps that was changed, conflating the two features in end user mind, but if you are shutting the machine down to power off, stuff is not saved to resume space.
I've both done s2disk (works) and halt (works). But when I boot next, it always boot to the default kernel (I think it is the default kernel, too fast to read). There is a file, "/boot/grub/default", that contains +++ 16384 ++- But it is dated today. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPA/wACgkQtTMYHG2NR9WWQACfQh2nqITPCRdawblqda/AXjdh pZQAoJihdi3mwH8HPSQf0z7ApbfgsR+0 =/mTD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/12/22 04:05 (GMT+0100) Carlos E. R. composed:
it always boot to the default kernel (I think it is the default kernel, too fast to read).
Fix it so the default kernel can't be found and see what happens. -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi,
On Mon, Dec 22, 2008 at 5:55 AM, Felix Miata
On 2008/12/22 04:05 (GMT+0100) Carlos E. R. composed:
it always boot to the default kernel (I think it is the default kernel, too fast to read).
I vaguely remember that the file, something like "default", is created in /boot/grub. If this file exists, grub would not present the menu. This is how it works when you are using "reboot" menu in KDE and select specific OS there. The default file is written and no OS selection menu is shown. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 08:15 +0200, Mark Goldstein wrote:
I vaguely remember that the file, something like "default", is created in /boot/grub. If this file exists, grub would not present the menu. This is how it works when you are using "reboot" menu in KDE and select specific OS there. The default file is written and no OS selection menu is shown.
I do have that file. I could try renaming it... done, will see on next boot. Mmm... searching for default on "info grub" finds a "savedefault" command. And a program named "grub-set-default". But I don't see how to disable it! If it is that. Another posibility is the "grubonce" program, but the explanation in the manual doesn't match what I have. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPj8cACgkQtTMYHG2NR9U96ACeOJ4xVrMNysAXcCo4TPmZJ7T5 1ksAn0sx+T0Ocx1GXreAgCRhG8e5pGE1 =mUYF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2008-12-21 at 22:55 -0500, Felix Miata wrote:
On 2008/12/22 04:05 (GMT+0100) Carlos E. R. composed:
it always boot to the default kernel (I think it is the default kernel, too fast to read).
Fix it so the default kernel can't be found and see what happens.
I guess it would not boot, and leave me on the grub command line prompt, as it does when it has problems. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPi1UACgkQtTMYHG2NR9W4+gCZAV0uC5h8+Nn//rBlMbwIMKLr zTUAnjwNgLDWcw6ZeZlY6mOGNRaBS5No =rnN8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/22 Carlos E. R.
On Monday, 2008-12-22 at 02:12 -0000, Rob OpenSuSE wrote:
2008/12/22 Michael S. Dunsavage
: On Mon, 2008-12-22 at 02:34 +0100, Carlos E. R. wrote:
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it.
You can prevent 'resume' simply by altering the resume device and writing 'noresume' there.
_if_ menu.lst is read, and I think it isn't.
When I read about that GRUB feature, it was a matter of storing which option was last used, and presumbably a flag. To not read menu.list, the whole information on the boot would have to be changed. So can't you force it to read the menu.list, by installing GRUB into the /boot partition you want used, activating it, and using Generic boot code in the MBR?
The thing is a red herring though. There's a feature in GRUB that lets you tell it which option to boot up, it's saved to a disk block, similarly GRUB can change it's default to the last booted kernel.
Ah. This looks like it. Do you know the name of this feature, so that I can search for it in the documentation?
Sorry, I don't. I'd expect it to be near the changing default to last booted kernel, rather than static selection and all that. There again, I can't remember being offered that feature in a SuSE release, it was probably either the mighty Debian or when tinkering with Gentoo. I tried to stay out of this thread, as I wasn't 100% on these details, but hope what I could suggest helps in the end. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 12:44 -0000, Rob OpenSuSE wrote:
2008/12/22 Carlos E. R. <>:
_if_ menu.lst is read, and I think it isn't.
When I read about that GRUB feature, it was a matter of storing which option was last used, and presumbably a flag. To not read menu.list, the whole information on the boot would have to be changed.
Could be. Or it could be just reading a default entry without a prompt.
So can't you force it to read the menu.list, by installing GRUB into the /boot partition you want used, activating it, and using Generic boot code in the MBR?
Perhaps, but before going that step I wanted to know more. I'd like to know how s2disk does the trick and undo it - and I seriously doubt that s2disk touches the boot record, that's something delicate to do.
The thing is a red herring though. There's a feature in GRUB that lets you tell it which option to boot up, it's saved to a disk block, similarly GRUB can change it's default to the last booted kernel.
Ah. This looks like it. Do you know the name of this feature, so that I can search for it in the documentation?
Sorry, I don't. I'd expect it to be near the changing default to last booted kernel, rather than static selection and all that. There again, I can't remember being offered that feature in a SuSE release, it was probably either the mighty Debian or when tinkering with Gentoo.
I tried to stay out of this thread, as I wasn't 100% on these details, but hope what I could suggest helps in the end.
No, thanks anyway, ideas spur more ideas, in the end we all learn something :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPkwUACgkQtTMYHG2NR9WwbgCfTKMa7/jzZxteaZPBIffv+Wpt RaMAnRXZ22Um3R7FcgxoobvyIgq94go4 =gZ/H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/22 Carlos E. R.
Perhaps, but before going that step I wanted to know more. I'd like to know how s2disk does the trick and undo it - and I seriously doubt that s2disk touches the boot record, that's something delicate to do.
The clean way, is to invoke the boot loader, GRUB to do it. Then knowledge of boot loading is kept in one place. The GRUB documentation, online guides and explanations and the GRUB source code, is going to be the place to dig around in, if you want to know how it's done. Obviously the s2disk source, though if you have an executuable, sometimes simply doing 'strings <file>' might just show up a give away. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 13:33 -0000, Rob OpenSuSE wrote:
2008/12/22 Carlos E. R.
: Perhaps, but before going that step I wanted to know more. I'd like to know how s2disk does the trick and undo it - and I seriously doubt that s2disk touches the boot record, that's something delicate to do.
The clean way, is to invoke the boot loader, GRUB to do it. Then knowledge of boot loading is kept in one place.
Yes, but we have to know what grub command they used in order to undo it. I don't think they change the boot sector, that can damage other systems.
The GRUB documentation, online guides and explanations and the GRUB source code, is going to be the place to dig around in, if you want to know how it's done.
I have looked at the grub docuementation and didn't find this. As to the source code... that's to complex for me. Somebody must know what they did. I have tried something, I'm going to reboot and see. If it fails, I'll open a bugzilla, because the investigation of another bugzilla that they are waiting from me is impeded till I can boot properly. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPmQMACgkQtTMYHG2NR9VVkQCfXi9fjgDy08ELv4ZP+nSy8Gft Wv8An3J9Is5XDskanPQOUNv+zDzwZkmR =gZz6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/22 Carlos E. R.
On Monday, 2008-12-22 at 13:33 -0000, Rob OpenSuSE wrote:
2008/12/22 Carlos E. R.
: Perhaps, but before going that step I wanted to know more. I'd like to know how s2disk does the trick and undo it - and I seriously doubt that s2disk touches the boot record, that's something delicate to do.
The clean way, is to invoke the boot loader, GRUB to do it. Then knowledge of boot loading is kept in one place.
Yes, but we have to know what grub command they used in order to undo it. I don't think they change the boot sector, that can damage other systems.
GRUB reads files in the /boot filesystem, so the logical place is a file in the /boot/grub directory. Such as the 'default' suggested. In my /boot/grub/default, I have '4'. There's an option to use "default saved" rather than a number in menu.list, so you can default to the last booted kernel. info:grub shows the manual in a Konqueror window. Other desktops should show info files to. So this is what I think is happening. You're probably not picking up the GRUB menu.list you expect, it's instant booting either the default or the only option. In the end I think you're going to have to install it, to use the menu.list that you want used and have checked. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2008-12-21 at 20:56 -0500, Michael S. Dunsavage wrote:
On Mon, 2008-12-22 at 02:34 +0100, Carlos E. R. wrote:
Not yet... I suppose that reinstalling grub would work, but the best thing would be to know what hibernate changes and undo it.
I did a quick Google search, since I don't have a notebook and I don't hibernate my PC's.
Ahhh! (1)
http://forums.opensuse.org/archives/sf-archives/archives-install-boot/340152...
Yes, interesting. One person ask how to hibernate, and then get the grubmenu and boot into windows instead. They answer that this is not possible and not wanted. Well, I know it was possible, I did it. But they changed the method and know I don't know how to do it. Doesn't help in the current situation.
http://manpages.ubuntu.com/manpages/dapper/man8/hibernate.8.h (look @ the -g switch)
Very interesting, but there is no such script in suse.
seems like it could help you. In general it seems that hibernate to disk is putting an image on the drive and telling grub to just load that. Possibly fixing it would be to do a complete hard shut down. So, possibly shutdown -h NOW or something of that nature.
Hope that helps.
(1) The code is in /usr/lib/pm-utils/sleep.d/99Zgrub. It is using "/usr/sbin/grubonce" for the trick. On restore it uses "/var/run/suspend.grubonce.default", but that file is missing. Ah, the trick is deleting "/boot/grub/default", so that is Ok. I'll try that. I'll report back, I've to do other things now. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPnX8ACgkQtTMYHG2NR9VvVwCgl/EeK+hUGicp8om9resdoRi5 wEMAn1ukDySZwScfYPPYc2PzEupppyia =TZ3P -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 15:00 +0100, I wrote:
On Sunday, 2008-12-21 at 20:56 -0500, Michael S. Dunsavage wrote:
Ahhh! (1) ... (1) The code is in /usr/lib/pm-utils/sleep.d/99Zgrub.
It is using "/usr/sbin/grubonce" for the trick.
On restore it uses "/var/run/suspend.grubonce.default", but that file is missing. Ah, the trick is deleting "/boot/grub/default", so that is Ok. I'll try that.
I'll report back, I've to do other things now.
That was it. I¡ll explain what happens. When hibernate runs, the script '/usr/lib/pm-utils/sleep.d/99Zgrub' saves file '/boot/grub/default', if it exists, to '/var/run/suspend.grubonce.default', then runs 'grubonce' with the appropriate options, and the file '/boot/grub/default is created. When system is restored, the file '/var/run/suspend.grubonce.default', if it exists, is moved to '/boot/grub/default', and if not, then '/boot/grub/default' is deleted. In my case, as the restore failed, I had a '/boot/grub/default' file, which impedes the menu being read. And, when I hibernated, it created a new 'default' file, and it was restored from the backup when system cam back - so the file never disappeared. Solution: delete '/boot/grub/default'. Also, for those wanting to be able to hibernate Linux and boot Windows, they have to disable the script '/usr/lib/pm-utils/sleep.d/99Zgrub'. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPtxwACgkQtTMYHG2NR9WEVgCdHEFAChYCntZ/DY1jRLfd/ROv +4sAnjc4K1XSqcBsG2wOW7vDGPa1BC+1 =QGcw -----END PGP SIGNATURE-----
2008/12/22 Carlos E. R.
On Monday, 2008-12-22 at 15:00 +0100, I wrote:
On Sunday, 2008-12-21 at 20:56 -0500, Michael S. Dunsavage wrote:
Solution: delete '/boot/grub/default'.
Also, for those wanting to be able to hibernate Linux and boot Windows, they have to disable the script '/usr/lib/pm-utils/sleep.d/99Zgrub'.
That risks devices being left in a different state, to how the hibernate system expects. There was notes on LWN about the resume trying it's best, but probably the "if it breaks you get to keep both pieces" saying applies there. There's also suggestions to only mount read-only the 'other' systems partitions, to avoid corruption. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 16:06 -0000, Rob OpenSuSE wrote:
2008/12/22 Carlos E. R. <>:
Also, for those wanting to be able to hibernate Linux and boot Windows, they have to disable the script '/usr/lib/pm-utils/sleep.d/99Zgrub'.
That risks devices being left in a different state, to how the hibernate system expects. There was notes on LWN about the resume trying it's best, but probably the "if it breaks you get to keep both pieces" saying applies there. There's also suggestions to only mount read-only the 'other' systems partitions, to avoid corruption.
Yes, of course it is dangerous, but the danger is simply that of mounting r/w a partition that was opened when suspended. Thus, if from linux you: umount all windows partitions s2disk reboot to windows do not mount any linux partitions reboot to suspended linux you are safe. I have done this often in the past: now I run a virtual windows instead. However, I would not dare to hibernate linux and boot to another linux: the other linux might run fsck on the suspended partitions. Havoc! It is like saying: don't cross the road, it is dangerous. Ok, fine, but if the danger is well known and the cars avoided, you can cross. Kids better wait for their parents ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklPwycACgkQtTMYHG2NR9UPbwCfU1IYgNT4RlV/nWoP+KhMf8vh moMAn0+HgdC+yzJmx04A+hMNeWv0zHgS =7SRQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/12/22 Carlos E. R.
On Monday, 2008-12-22 at 16:06 -0000, Rob OpenSuSE wrote:
2008/12/22 Carlos E. R. <>:
Also, for those wanting to be able to hibernate Linux and boot Windows, they have to disable the script '/usr/lib/pm-utils/sleep.d/99Zgrub'.
That risks devices being left in a different state, to how the hibernate system expects. There was notes on LWN about the resume trying it's best, but probably the "if it breaks you get to keep both pieces" saying applies there. There's also suggestions to only mount read-only the 'other' systems partitions, to avoid corruption.
Yes, of course it is dangerous, but the danger is simply that of mounting r/w a partition that was opened when suspended. Thus, if from linux you:
umount all windows partitions s2disk reboot to windows do not mount any linux partitions reboot to suspended linux
you are safe. I have done this often in the past: now I run a virtual windows instead. However, I would not dare to hibernate linux and boot to another linux: the other linux might run fsck on the suspended partitions. Havoc!
It is like saying: don't cross the road, it is dangerous. Ok, fine, but if the danger is well known and the cars avoided, you can cross.
People in a hurry using Google might find your solution, and such might stumble across it, without realising the risks. If they do that, they should know it's risky and not be surprised if they run into trouble. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 17:08 -0000, Rob OpenSuSE wrote:
It is like saying: don't cross the road, it is dangerous. Ok, fine, but if the danger is well known and the cars avoided, you can cross.
People in a hurry using Google might find your solution, and such might stumble across it, without realising the risks. If they do that, they should know it's risky and not be surprised if they run into trouble.
:-) Things found like that should not be used on a hurry, have to be meditated. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklP5dAACgkQtTMYHG2NR9X53wCdELNGIcxBP8p4XHuXkrWrt3bM L+cAmwQlMH/twi1L1U9YnyLOy9PMBUTY =SrBg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 17:08 -0000, Rob OpenSuSE wrote:
People in a hurry using Google might find your solution, and such
By the way... I'm getting most of your emails duplicated. I don't know if it is your side or mine :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklP5okACgkQtTMYHG2NR9WMHQCfSFjF1IEOv53EMJCqGnKy5eJ8 VeUAn1uhJ4gTYUYq33ker057gzSJGq1U =ttxc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R.
-
Carlos E. R.
-
Felix Miata
-
Mark Goldstein
-
Michael S. Dunsavage
-
Rob OpenSuSE