public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jalvo@mbay.net (John Alvord)
To: linux-kernel@vger.kernel.org
Subject: Re: Switching Kernels without Rebooting?
Date: Thu, 12 Jul 2001 05:08:25 GMT	[thread overview]
Message-ID: <3b512f43.30115420@mail.mbay.net> (raw)
In-Reply-To: <Pine.GSO.4.21L-021.0107120031570.7765-100000@unix14.andrew.cmu.edu>
In-Reply-To: <Pine.GSO.4.21L-021.0107120031570.7765-100000@unix14.andrew.cmu.edu>

On Thu, 12 Jul 2001 00:48:15 -0400 (EDT), Frank Davis
<fdavis@andrew.cmu.edu> wrote:

>Hello all,
>  I believe that if such a project is to be undertaken, it first
>needs to be designed, then coded. I agree that is a difficult problem...As
>for its feasiblity, I'm unsure. Maybe the reason this topic comes up
>here from time to time is because it hasn't been shown to be a bad
>idea. It might be be, but if we don't start somewhere, then we'll never
>really know, and the debate will continue. Just my .02 cents.
>Regards,

This topic comes up once a twice a year.

Usually this topic comes to a grinding halt when someone points out
that drivers can be created modular. They can be loaded and unloaded
without rebooting Linux. One project used that technique to
load/unload different schedulers. While this satisfies only part of
the need, it is usually enough to satisfy the tinker-er.

A more recent development is UML - User Mode Linux - where you can run
a nearly complete Linux image in user mode. That way you can fiddle
with file systems to your hearts content without rebooting the main
system. I suspect that will satisfy others.

john alvord

  reply	other threads:[~2001-07-12  5:08 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  4:48 Switching Kernels without Rebooting? Frank Davis
2001-07-12  5:08 ` John Alvord [this message]
2001-07-13  9:10   ` Chuck Hemker
  -- strict thread matches above, loose matches on Subject: below --
2001-07-13  1:11 tas
2001-07-13  3:45 ` Ian Stirling
2001-07-12 15:32 Jesse Pollard
2001-07-12 12:23 Jesse Pollard
2001-07-12 14:55 ` Ralf Baechle
2001-07-12  1:03 Torrey Hoffman
2001-07-12  1:24 ` C. Slater
2001-07-12 10:07   ` Jesse Pollard
2001-07-12 12:11     ` Ian Stirling
2001-07-12 12:54       ` Jesse Pollard
2001-07-12 14:15         ` Michael H. Warfield
2001-07-12 23:17   ` Pavel Machek
2001-07-12 20:47 ` Wilfried Weissmann
     [not found] <994895240.21189@whiskey.enposte.net>
2001-07-12  0:10 ` Stuart Lynne
2001-07-11  9:52 David Balazic
2001-07-11 10:08 ` Laramie Leavitt
2001-07-11 19:12   ` H. Peter Anvin
2001-07-11 15:19 ` C. Slater
     [not found] <NOEJJDACGOHCKNCOGFOMOEKECGAA.davids@webmaster.com>
2001-07-10 20:43 ` C. Slater
2001-07-11  3:50   ` FORT David
2001-07-11  9:10   ` Helge Hafting
2001-07-11 15:41     ` C. Slater
2001-07-12 10:16       ` Helge Hafting
2001-07-11 22:12     ` Paul Jakma
2001-07-11 22:14       ` Rik van Riel
2001-07-11 22:36         ` C. Slater
2001-07-11 23:44           ` Andreas Dilger
2001-07-12  1:17             ` C. Slater
2001-07-12 15:39               ` Rik van Riel
2001-07-12 16:23                 ` Albert D. Cahalan
2001-07-12 17:37                   ` Mike Borrelli
2001-07-12 18:05                   ` Rik van Riel
2001-07-13 10:07                     ` Pau Aliagas
2001-07-12 18:48                   ` Chris Friesen
2001-07-12 10:12             ` Ralf Baechle
2001-07-12 15:32           ` Rik van Riel
2001-07-11 22:36         ` David Schwartz
2001-07-12  7:23         ` Kai Henningsen
2001-07-12 10:05           ` Helge Hafting
2001-07-13  6:50             ` Kai Henningsen
2001-07-12 17:58           ` Hua Zhong
2001-07-11 22:46       ` Kip Macy
2001-07-11 23:02         ` Rik van Riel
2001-07-12  0:31         ` Jesse Pollard
2001-07-12  1:10           ` Hua Zhong
2001-07-11 23:36       ` H. Peter Anvin
2001-07-12  7:23       ` Ville Herva
2001-07-10 18:42 C. Slater
2001-07-10 18:50 ` Chris Wedgwood
2001-07-10 21:11 ` Jesper Juhl

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=3b512f43.30115420@mail.mbay.net \
    --to=jalvo@mbay.net \
    --cc=linux-kernel@vger.kernel.org \
    /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