Re: two issues with suspend to disk in Suse 10.2
Wilfried Maschtera <[email protected]> Tue, 1 May 2007 19:03:16 +0200
| Newsgroups | gmane.linux.suse.laptop |
|---|---|
| Message-ID | <[email protected]> |
On Tue, May 01, 2007 at 02:04:30PM +0200, Martin Hofius wrote: > Am Dienstag, 1. Mai 2007 12:03 schrieb Pramod: > > Hi, > > I have a Samsung X20 notebook with Suse 10.2 installed and I use KDE. > > I have a couple of problems I would like to solve. > > > > 1) I would like to have the option of suspending Linux and resuming > > Windows and vice versa > > without booting either OS (as it used to be with Suse 10.0). At the > > moment the default for > > Linux is the session from which the suspend is called. So it resumes > > to Suse by default. How can I make Grub give me the choice I want? It > > looks like (to me, a non-expert) in /etc/pm/hooks/99Zgrub Linux is set > > as the default using grubonce. > > Hi Pramod, > sorry I have no other useful hints, but: are Your shure to know what You are > doing??? I remember the choice after suspend was disabled by SuSE to prevent > the destroying of Your data... > When one of the both systems is suspended, also the state information of the > file systems are saved. If You would start an other system and change files > in that filesystem, You may image what happens? > If it was possible in SuSE 10.0 I gues it was a bug!?! Why should it be a bug? In my opinion if the state information of the systems are stored in different locations suspending one system and resuming another one is not risky but of course you should mount files from a suspend system read/writeable. I think, windows will not use the linux swap. Sometimes I suspend my linux and boot windows and then resume linux again. Up to now I had no problems. Indeed I assume you can have several linuxes and do the same provided each linux has its own swap partition. Kind regards, Wilfried > > greetings > martin > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >