linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Suspend on one machine, resume elsewhere
Date: Mon, 21 Jul 2003 13:41:33 -0700	[thread overview]
Message-ID: <m2adb7bojm.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <20030720225342.GA866@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]

>>>>> "Pavel" == Pavel Machek <pavel@ucw.cz>:
 Pavel> Hi!
 > If you want to migrate programs between machines, run UMLinux, same
 > config, on both machines. Ouch and you'll need swsusp for UMLinux,
 > too
 >
 > That might be more important than you think.
 >>
 Pavel> :-). Well, it is also harder than you probably think, because
 Pavel> UML is *very* strange architecture and it is not at all easy to
 Pavel> save/restore its state. There were some patches in that area,
 Pavel> but it never worked (AFAIK).
 >>
 >> ... but there are many people who dream about swsusp for UMLinux.
 >>
 >> Particularly some laptop users who want to suspend (at least the
 >> most critical long-running applications) and/or find Linux way too
 >> unstable and requiring frequent reboots.
 >>
 >> The day UMLinux gets swsusp, I'm moving my XEmacs, mozilla and some
 >> other toys into a UML machine and staying there. Hopefully then a
 >> single problem with a USB driver, keventd running wild, or other
 >> frequently encountered breakage won't be taking my entire world
 >> down.

 Pavel> Well, then you may as well help porting swsusp to UML ;-).

 Pavel> OTOH, single problem with suspend *will* then bring your entire
 Pavel> world down :-(. You would be able to rollback, through.  

But that's significantly better than any USB problem or any ALSA problem
or any ACPI problem bringing down my entire world, which is the current
situation with Linux 2.4.

I have the impression that the core developers are unaware of the fact
of how unstable Linux has become, particularly on laptops. I guess if
you do kernel work and reboot often, you never notice that. Besides,
doing stability work is "unfashionable"...

--J. (duly trying to report all bugs encountered)

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-07-21 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 20:20 RE:Re: Thoughts wanted on merging Softwa pavel
2003-07-15 21:22 ` [Swsusp-devel] " Karol Kozimor
2003-07-16  8:37   ` Pavel Machek
2003-07-16 10:37     ` root
2003-07-16 10:40       ` Suspend on one machine, resume elsewhere [was Re: [Swsusp-devel] RE:Re: Thoughts wanted on merging Softwa] Pavel Machek
2003-07-16 17:51         ` Ingo Oeser
2003-07-16 18:15           ` Pavel Machek
2003-07-16 19:17             ` Alan Cox
2003-07-16 22:39               ` Antonio Vargas
2003-07-17 11:49                 ` Alan Cox
2003-07-17 16:29                   ` Pavel Machek
2003-07-17 16:45                     ` Alan Cox
2003-07-19 18:22             ` Suspend on one machine, resume elsewhere Jan Rychter
2003-07-20 22:53               ` Pavel Machek
2003-07-21 20:41                 ` Jan Rychter [this message]
2003-07-23  5:13                   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2adb7bojm.fsf@tnuctip.rychter.com \
    --to=jan@rychter.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Suspend on one machine, resume elsewhere' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).