Knurpht - Gertjan Lettink schreef op 14-04-16 09:23:
Op woensdag 13 april 2016 17:10:17 CEST schreef Chris Murphy:
On Wed, Apr 13, 2016 at 3:50 PM, James Knott
wrote: On 04/13/2016 04:50 PM, Per Jessen wrote:
Umm, except when a system has been hibernated.
Since when do you get to choose another OS when coming out of hibernation?
I've always been greeted by the exact same GRUB boot menu options whether cold boot or resuming from suspend to disk. So... that's presumably how I could choose the wrong thing. That means your GRUB is controlled by "the other OS".
Shouldn't this sort of thing be a feature to begin with? I mean.... if you can start another OS while keeping the other one hibernated, why should you not be allowed to do it? I think maybe that is the question you need to ask first. If then the resulting system requires two swaps (for instance) that is a choice. Personally when I construct my filesystems (partitions) I put a swap after root. I rarely hibernate if ever but I plan for it by making it the same size as my memory. Then if I ever decide I don't want the swap or want to place it elsewhere, I have about 4-8GB of room to grow the root filesystem if I need it to. So for me swap is something I tie in with rootfs because my roots are usually quite small (this Kubuntu install has 16GB). If I were to install another distro on the same disk (like some version of OpenSUSE likely, since I am very content with Kubuntu 16.04 and don't really need anything else from that branch) the question whether I wanted another swap would come down to maybe two considerations: - Would I ever want this "hibernate one, boot another" scenario? - Does it bring me any benefit to use a different swap: is the swap of the other filesystem inaccessible? Encrypted or something? Do I want to hibernate at all. Personally I never hibernate but this is no laptop. I only use suspend. Personally I very often will not choose a second swap. Personally I don't really want it. If that means not having hibernate one, boot another, so be it. Dual boot is a horror to me anyway and I look more and more into virtualisation as a choice of how to deal with that. There are certainly virtualizers that can load another system from actual partitions, and if the user interface for that is good, it could maybe for the most part permanently replace actually dual booting something for me. Then maybe you can't have swap for the guest OS. Or you make a small one. I have often considered the question myself when installing another system and I have never chosen to date to create a nother swap, from my recollection. The idea of reusing the same partition feels much nicer to me. So unless the hibernate-boot-another scenario is important to you, I would suggest to not create additional swaps. As a default, I doubt really many people would use it that way, I don't think many people have a real concern for this, if you reboot, maybe expect to shut down your current system, but I don't know. I think there's not really anything bad about it and conceptually maybe it feels nicer to close one instance before opening another. Stop before you start, end before you begin. For instance, hibernating one instance and then loading another that has access to the same filesystems, immediately raises the concern of: what will happen if I change something the hibernated instance has open, or anything of the kind? If everything is logically separated, this never becomes a concern in your mind ever. But now, there may be instances where you need to think about it. Do you want that mental burden? When are you going to know when you need to think about it, and when are you going to know when you don't? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org