public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: David Lang <david.lang@digitalinsight.com>
Cc: John Nilsson <pzycrow@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Some experience of linux on a Laptop
Date: 25 Jun 2001 02:38:22 -0600	[thread overview]
Message-ID: <m1u2159cox.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0106242308100.7535-100000@dlang.diginsite.com>
In-Reply-To: <Pine.LNX.4.33.0106242308100.7535-100000@dlang.diginsite.com>

David Lang <david.lang@digitalinsight.com> writes:

> if you don't preserve things running in userspace what advantage do you
> have over rebooting?

I use it as part of a bootloader.  Allowing me to boot one kernel
directly from another.   I guess it really is a soft reboot that never
touches any BIOS.  I don't know if anyone else would get value from it.
 
> if you do preserve userspace stuff then you need to also preserve the
> kernel state related to each user process (including network connections,
> etc), and here you are back into the problem that the kernel structures
> may change on you.

Preserving userspace without out any help from user space is quite
a tricky business.  Though with user space help it is fully doable
though it may be a lot of work.

What I have doesn't address perserving user space.  I offered because
I didn't know what was wanted.  An easy kernel upgrade without touching
running processes or a just a fast way to get into a new kernel.

Eric

  reply	other threads:[~2001-06-25  8:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24 20:51 Some experience of linux on a Laptop John Nilsson
2001-06-24 20:35 ` David Lang
2001-06-25  3:48   ` Eric W. Biederman
2001-06-25  6:09     ` David Lang
2001-06-25  8:38       ` Eric W. Biederman [this message]
2001-06-24 21:08 ` Fabian Arias
2001-06-24 21:22 ` Android
2001-06-24 21:22   ` Andrzej Krzysztofowicz
2001-06-25 17:47   ` Joseph Pingenot
2001-06-24 21:48 ` Alan Cox
2001-06-24 22:11   ` Jeff Chua
2001-06-24 22:15     ` Alan Cox
2001-06-24 22:11   ` William Stearns
2001-06-24 22:38   ` Hua Zhong
2001-06-25  3:45   ` Eric W. Biederman
2001-06-24 21:57 ` Daniel Phillips
2001-06-24 22:12   ` Alan Cox
2001-06-24 22:27     ` Daniel Phillips
2001-06-24 21:59 ` Rik van Riel
2001-06-24 22:26 ` Jeff Chua
2001-06-24 23:14 ` Luigi Genoni
2001-06-24 23:17 ` Keith Owens
2001-06-25  9:04 ` Helge Hafting
2001-06-25 10:09 ` PALFFY Daniel
2001-06-27  9:07 ` Julien Laganier
  -- strict thread matches above, loose matches on Subject: below --
2001-06-25  0:25 Dieter Nützel
2001-06-25  9:21 ` Luigi Genoni
2001-06-25 13:19 John Nilsson
     [not found] <fa.inojkfv.1tiu4gb@ifi.uio.no>
     [not found] ` <fa.gblj07v.1blumpa@ifi.uio.no>
2001-06-29 20:12   ` John Golubenko

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=m1u2159cox.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pzycrow@hotmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox