unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: What ARM hardware should we buy and where should we host it?
Date: Sat, 15 Sep 2018 00:02:03 +0200	[thread overview]
Message-ID: <87tvmr91r8.fsf@tobias.gr> (raw)
In-Reply-To: <87a7oj6a9f.fsf@elephly.net>

Ricardo,

Ricardo Wurmus wrote:
>> Ricardo Wurmus wrote:
>>> We are looking for volunteers who could either host a machine 
>>> at
>>> home or
>>> in a data centre that they could get emergency access to.
>>
>> I've got plenty of cool, dry space for homeless boxen. No 
>> racks,
>> though.
>
> This is good!  Do you have somewhat convenient access to the 
> space in
> case the machines become unresponsive?

I tend to flee the city during week-ends and holidays, of course, 
but usually, yes.

> Would you be willing to host an Overdrive 1000 box or two?

Sure! Let me know what you decide and what I need to do.

> If so, I think we should be looking for a vendor that can 
> deliver to your place.

Righty-ho. If all else fails there's always the FOSDEM sneakernet.

Kind regards,

T G-R

  reply	other threads:[~2018-09-14 22:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 11:37 What ARM hardware should we buy and where should we host it? Ricardo Wurmus
2018-09-03 16:28 ` Tobias Geerinckx-Rice
2018-09-14 21:26   ` Ricardo Wurmus
2018-09-14 22:02     ` Tobias Geerinckx-Rice [this message]
2018-09-03 17:59 ` Vagrant Cascadian
2018-09-03 18:11   ` Steve McIntyre
2018-09-04 18:03   ` Leo Famulari
2018-09-05  0:05     ` Steve McIntyre
2018-09-11 21:33 ` Andreas Enge
2018-09-14 21:37   ` Ricardo Wurmus
2018-09-15 13:42     ` Andreas Enge
2018-09-14 20:22 ` Vagrant Cascadian
2018-09-14 21:28   ` Ricardo Wurmus

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=87tvmr91r8.fsf@tobias.gr \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).