Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #16912
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.os.linux.advocacy, alt.comp.os.windows-11 |
| Subject | Re: Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) |
| Date | 2025-02-08 23:42 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <vo8q4j$8tqo$2@dont-email.me> (permalink) |
| References | (2 earlier) <4iJnP.222162$HO1.112840@fx14.iad> <vo5u8q$3lvnm$1@dont-email.me> <esypP.13$NwV6.6@fx39.iad> <vo6u10$3ue2q$1@dont-email.me> <m0ojr4Fakt5U3@mid.individual.net> |
Cross-posted to 2 groups.
On 8 Feb 2025 08:44:20 GMT, vallor wrote:
> On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro
> <ldo@nz.invalid> wrote in <vo6u10$3ue2q$1@dont-email.me>:
>
>> Doesn’t RHEL support kexec, which
>> allows the old Linux kernel to pass control to the new one without
>> actually disrupting the userland?
>
> You're thinking of live kernel patching. kexec_load(2) load a kernel
> that you can have execute if the current kernel crashes. You do this
> for debugging, usually.
Bit more than that <https://manpages.debian.org/kexec_load(2)>:
The kexec_load() system call loads a new kernel that can be
executed later by reboot(2).
And one of the functions of the latter
<https://manpages.debian.org/reboot(2)> is:
LINUX_REBOOT_CMD_KEXEC
(RB_KEXEC, 0x45584543, since Linux 2.6.13). Execute a kernel
that has been loaded earlier with kexec_load(2).
Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-01 21:55 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-01 19:07 -0500
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-01 20:11 -0500
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:24 +0000
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-02-02 04:05 +0000
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) CrudeSausage <crude@sausa.ge> - 2025-02-02 07:19 -0500
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-02-02 07:55 -0500
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 23:22 +0000
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Paul <nospam@needed.invalid> - 2025-02-02 00:08 -0500
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Java Jive <java@evij.com.invalid> - 2025-02-02 13:57 +0000
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 23:19 +0000
Re: Dimdows Decay Syndrome Continues Mark Lloyd <not.email@all.invalid> - 2025-02-02 19:26 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-02 14:49 -0500
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-02 15:29 -0500
Re: Dimdows Decay Syndrome Continues chrisv <chrisv@nospam.invalid> - 2025-02-02 15:26 -0600
Re: Dimdows Decay Syndrome Continues Java Jive <java@evij.com.invalid> - 2025-02-03 02:50 +0000
Re: Dimdows Decay Syndrome Continues rbowman <bowman@montana.com> - 2025-02-03 04:03 +0000
Re: Dimdows Decay Syndrome Continues Jeff Barnett <jbb@notatt.com> - 2025-02-02 23:17 -0700
Re: Dimdows Decay Syndrome Continues Java Jive <java@evij.com.invalid> - 2025-02-03 13:16 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-07 20:03 -0500
Re: Dimdows Decay Syndrome Continues Andy Burns <usenet@andyburns.uk> - 2025-02-08 20:12 +0000
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-08 21:06 -0500
Re: Dimdows Decay Syndrome Continues CrudeSausage <crude@sausa.ge> - 2025-02-02 07:11 -0500
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 21:34 +0000
Re: Dimdows Decay Syndrome Continues CrudeSausage <crude@sausa.ge> - 2025-02-07 20:29 -0500
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 06:36 +0000
Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) vallor <vallor@cultnix.org> - 2025-02-08 08:44 +0000
Re: Kexec (and HyperV) Paul <nospam@needed.invalid> - 2025-02-08 06:41 -0500
Re: Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 23:42 +0000
Re: Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) vallor <vallor@cultnix.org> - 2025-02-09 00:25 +0000
Re: Dimdows Decay Syndrome Continues CrudeSausage <crude@sausa.ge> - 2025-02-08 09:05 -0500
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 23:44 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-08 19:05 -0500
Re: Dimdows Decay Syndrome Continues vallor <vallor@cultnix.org> - 2025-02-09 13:58 +0000
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-08 21:18 -0500
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-07 21:05 -0500
Re: Dimdows Decay Syndrome Continues Physfitfreak <physfitfreak@gmail.com> - 2025-02-01 21:53 -0600
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 21:41 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-07 19:14 -0500
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-07 20:26 -0500
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-07 20:50 -0500
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-07 21:57 -0500
Re: Dimdows Decay Syndrome Continues Frank Slootweg <this@ddress.is.invalid> - 2025-02-08 15:22 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-08 11:24 -0500
Re: Dimdows Decay Syndrome Continues Frank Slootweg <this@ddress.is.invalid> - 2025-02-08 18:36 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-08 13:49 -0500
Re: Dimdows Decay Syndrome Continues Physfitfreak <physfitfreak@gmail.com> - 2025-02-08 13:48 -0600
Re: Dimdows Decay Syndrome Continues rbowman <bowman@montana.com> - 2025-02-08 19:43 +0000
Re: Dimdows Decay Syndrome Continues Frank Slootweg <this@ddress.is.invalid> - 2025-02-08 20:41 +0000
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-02-08 16:12 -0500
Re: Dimdows Decay Syndrome Continues rbowman <bowman@montana.com> - 2025-02-09 00:35 +0000
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 23:54 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-08 19:07 -0500
Re: Dimdows Decay Syndrome Continues rbowman <bowman@montana.com> - 2025-02-09 00:40 +0000
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-18 21:51 +0000
Re: Dimdows Decay Syndrome Continues Joel <joelcrump@gmail.com> - 2025-02-18 17:11 -0500
Re: Dimdows Decay Syndrome Continues rbowman <bowman@montana.com> - 2025-02-19 01:06 +0000
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-17 21:37 +0000
Re: Dimdows Decay Syndrome Continues Frank Slootweg <this@ddress.is.invalid> - 2025-03-18 13:31 +0000
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-03-18 11:08 -0400
Re: Dimdows Decay Syndrome Continues CrudeSausage <crude@sausa.ge> - 2025-03-18 11:04 -0400
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-03-18 19:29 -0400
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-06-02 22:53 +0000
Re: Dimdows Decay Syndrome Continues Paul <nospam@needed.invalid> - 2025-06-02 23:27 -0400
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-27 22:03 +0000
Re: Dimdows Decay Syndrome Continues Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-09 00:15 +0000
csiph-web