From: Vincent Legoll <vincent.legoll@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [opinion] CVE-patching is not sufficient for package security patching
Date: Wed, 24 Mar 2021 21:24:40 +0100 [thread overview]
Message-ID: <CAEwRq=qnHcbWeKxiPQZ2NxtBmwKx=t8t7qsPLMyTWEjArOY4aw@mail.gmail.com> (raw)
In-Reply-To: <YFuYKgZgcf44KswI@jasmine.lan>
Hello,
On Wed, Mar 24, 2021 at 8:51 PM Leo Famulari <leo@famulari.name> wrote:
> > We bought a handful of Overdrive 1000 in the past (they are no longer
> > sold), and hosting was always an obstacle.
>
> I volunteer to host one or two workstation-type 64-bit ARM machines.
I already volunteered (privately) to host the same (1 or 2 WS power-class),
currently on ADSL uplink (so not for substitute distribution, only building),
FTTH in the future, no UPS though.
--
Vincent Legoll
next prev parent reply other threads:[~2021-03-24 20:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 11:10 [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-16 11:17 ` Jonathan Brielmaier
2021-03-16 11:27 ` Léo Le Bouter
2021-03-16 19:15 ` Leo Famulari
2021-03-16 23:19 ` Mark H Weaver
2021-03-16 23:49 ` Leo Famulari
2021-03-17 11:54 ` Guix moving too fast? zimoun
2021-03-17 6:07 ` [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-17 6:21 ` Léo Le Bouter
2021-03-20 11:19 ` Ludovic Courtès
2021-03-22 13:44 ` raingloom
2021-03-23 16:22 ` Joshua Branson
2021-03-23 23:53 ` Mark H Weaver
2021-03-23 17:56 ` Leo Famulari
2021-03-23 22:54 ` Ricardo Wurmus
2021-03-24 19:51 ` Leo Famulari
2021-03-24 20:24 ` Vincent Legoll [this message]
2021-03-24 20:32 ` Léo Le Bouter
2021-03-24 20:55 ` Leo Famulari
2021-03-25 14:22 ` Mathieu Othacehe
2021-03-25 18:19 ` Leo Famulari
2021-03-30 8:42 ` Buying AArch64 hardware? Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=qnHcbWeKxiPQZ2NxtBmwKx=t8t7qsPLMyTWEjArOY4aw@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).