Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard dkms systemd
Date: Mon, 5 Nov 2018 16:51:40 +0100	[thread overview]
Message-ID: <CAHmME9pRgYP6hSRVNUDN7pHwNFYdSyN-wZuu0FMW_hzcVoXEYA@mail.gmail.com> (raw)
In-Reply-To: <87sh0gdomi.fsf@fifthhorseman.net>

On Mon, Nov 5, 2018 at 7:47 AM Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
>  * echoing suggestions to stdout to rmmod/modprobe just before actually
>    doing the thing seems like a recipe for it happening twice.  I think
>    i wouldn't make that prompt if the administrator has already asked
>    the system to do the upgrade.

I was just re-reading this and noticed the same. Good point.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2018-11-05 15:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 20:59 Lucian Cristian
2018-10-20 21:07 ` Robert-André Mauchin
2018-10-21 12:12 ` Jordan Glover
2018-10-21 15:49   ` Lucian Cristian
2018-11-02 13:52     ` Daniel Kahn Gillmor
2018-11-02 23:27       ` Reuben Martin
2018-11-04  3:24         ` Daniel Kahn Gillmor
2018-11-04 15:35           ` Jason A. Donenfeld
2018-11-05  6:28             ` Daniel Kahn Gillmor
2018-11-05 11:27               ` Fabian Grünbichler
2018-11-06  7:16                 ` Daniel Kahn Gillmor
2018-11-06 13:04                   ` Fabian Grünbichler
2018-11-07  2:29                     ` Daniel Kahn Gillmor
2018-11-05 15:51               ` Jason A. Donenfeld [this message]
2018-11-03 11:54       ` Matthias Urlichs
2018-11-04  3:22         ` Daniel Kahn Gillmor
2018-10-21 13:01 ` Jonathon Fernyhough

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=CAHmME9pRgYP6hSRVNUDN7pHwNFYdSyN-wZuu0FMW_hzcVoXEYA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=dkg@fifthhorseman.net \
    --cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).