From: Leo Famulari <leo@famulari.name>
To: 26916@debbugs.gnu.org
Subject: bug#26916: doc: Suggest using `guix download` instead of curl
Date: Sat, 13 May 2017 20:51:26 -0400 [thread overview]
Message-ID: <20170514005126.GA31975@jasmine> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 193 bytes --]
A minor fix! I think it's better to suggest using `guix download` over
`curl` as a network connectivity test, since `guix download` will always
be available, while curl usually must installed.
[-- Attachment #1.2: 0001-doc-Suggest-a-network-test-command-that-will-definit.patch --]
[-- Type: text/plain, Size: 1051 bytes --]
From 27211ce5b121ca45d9bc1e6dfd0ecba4abffa25c Mon Sep 17 00:00:00 2001
From: Leo Famulari <leo@famulari.name>
Date: Sat, 13 May 2017 20:47:09 -0400
Subject: [PATCH] doc: Suggest a network test command that will definitely be
available.
* doc/guix.texi (Running GuixSD in a VM): Suggest the use of `guix
download` to test network connectivity.
---
doc/guix.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 5227ad4ba..873fcf7b7 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -15679,7 +15679,7 @@ to your system definition and start the VM using
@command{`guix system vm config.scm` -net user}. An important caveat of using
@command{-net user} for networking is that @command{ping} will not work, because
it uses the ICMP protocol. You'll have to use a different command to check for
-network connectivity, like for example @command{curl}.
+network connectivity, for example @command{guix download}.
@subsubsection Connecting Through SSH
--
2.13.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-05-14 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 0:51 Leo Famulari [this message]
2017-05-14 12:55 ` bug#26916: doc: Suggest using `guix download` instead of curl 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=20170514005126.GA31975@jasmine \
--to=leo@famulari.name \
--cc=26916@debbugs.gnu.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.
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).