From: Lennart Poettering <lennart@poettering.net>
To: Marti Raudsepp <marti@juffo.org>
Cc: systemd-devel <systemd-devel@lists.freedesktop.org>,
Simon Horman <horms@verge.net.au>,
kexec list <kexec@lists.infradead.org>
Subject: Re: Doing kexec reboot right in systemd
Date: Tue, 27 Mar 2012 12:01:36 +0200 [thread overview]
Message-ID: <20120327100132.GA15921@tango.0pointer.de> (raw)
In-Reply-To: <CABRT9RBa-x661VxvvinD6BPdFc0sharst-h9mgz0kht6aQr76Q@mail.gmail.com>
On Mon, 26.03.12 21:25, Marti Raudsepp (marti@juffo.org) wrote:
>
> On Mon, Mar 26, 2012 at 21:07, Lennart Poettering
> <lennart@poettering.net> wrote:
> > Marti, sorry for changing my mind on this: would be great if you could
> > prep a patch for this for systemd itself.
>
> D'oh, I already prepared a patch for kexec, although I haven't sent it
> out yet.
OK, I am fine with either.
> > Hmm, so since this would then belong in the shutdown path of systemd,
> > and only be added for the kexec shutdown path I actually think it would
> > make more sense to add this into systemd itself instead of kexec-tools,
> > to ensure the right ordering.
>
> Um, why is including in systemd necessary for guaranteeing order?
It isn't, but it's easier to keep early boot and late shutdown stuff in
systemd.
Lennart
--
Lennart Poettering - Red Hat, Inc.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-03-27 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 19:14 Doing kexec reboot right in systemd Marti Raudsepp
2012-03-22 22:36 ` Simon Horman
2012-03-26 18:07 ` Lennart Poettering
2012-03-26 18:25 ` Marti Raudsepp
2012-03-27 10:01 ` Lennart Poettering [this message]
2012-03-27 23:19 ` Simon Horman
2012-03-23 9:35 ` Bouchard Louis
2012-03-23 18:45 ` Marti Raudsepp
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=20120327100132.GA15921@tango.0pointer.de \
--to=lennart@poettering.net \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=marti@juffo.org \
--cc=systemd-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.