From: "Ludovic Courtès" <ludo@gnu.org>
To: Joshua Branson <jbranso@dismail.de>
Cc: 42317@debbugs.gnu.org
Subject: [bug#42317] [PATCH] doc: cookbook: Adding a section "Running Guix on a Linode Server
Date: Mon, 07 Sep 2020 15:59:11 +0200 [thread overview]
Message-ID: <871rjdit74.fsf@gnu.org> (raw)
In-Reply-To: <20200901104505.31147-1-jbranso@dismail.de> (Joshua Branson's message of "Tue, 1 Sep 2020 06:45:04 -0400")
Hi Joshua,
Thanks for following up on this! Minor comments:
Joshua Branson <jbranso@dismail.de> skribis:
> +@node Running Guix on a Linode Server
> +@section Running Guix on a Linode Server
> +@cindex linode
> +
> +Start with a recommended Debian server. We recommend using the default
^
I’d start the sentence with something like “To run Guix on a server
hosted by @uref{https://www.linode.com/, Linode}, start with a …”.
(That makes it clear what we’re talking about, what Linode is, etc.)
> +distro as a way to bootstrap Guix. Create your @code{SSH} keys.
[...]
> +Be sure to add your @code{SSH key} for easy login to the remote server.
[...]
> +Power the @code {Linode} down. In the @code{Linode's}
I realize I wasn’t clear: @code is for code snippets. When referring to
Linode (the service/company) or SSH (the protocol), just write it as is,
without @code.
You would use @code for a command (like @code{rm -rf /foo}) and @file
for a file name (like @file{/dev/sdc}). Text enclosed in @code or @file
is rendered with a fixed-width font and possibly a different background
color.
> +"..." and select "Edit", then on that menu add to /dev/sdc the "Guix"
^
@file here.
> +root@@<your-server-ip-here>}. (You can find your server ip address in
^
@var{your-server-ip-here}
And s/ip/IP/.
Let me know if you can take care of those last (I promise!) changes.
Thank you!
Ludo’.
next prev parent reply other threads:[~2020-09-07 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 0:41 [bug#42317] Adding a "Running Guix on a Linode" to the cookbook Joshua Branson via Guix-patches via
2020-07-21 20:51 ` Christopher Lemmer Webber
2020-08-07 17:15 ` Joshua Branson via Guix-patches via
2020-08-07 21:11 ` Christopher Lemmer Webber
2020-08-08 21:57 ` Joshua Branson via Guix-patches via
2020-08-07 17:16 ` Joshua Branson via Guix-patches via
2020-08-08 21:58 ` Joshua Branson via Guix-patches via
2020-08-31 10:33 ` Ludovic Courtès
2020-09-01 2:08 ` Joshua Branson via Guix-patches via
2020-09-01 10:45 ` [bug#42317] [PATCH] doc: cookbook: Adding a section "Running Guix on a Linode Server Joshua Branson via Guix-patches via
2020-09-07 13:59 ` Ludovic Courtès [this message]
2020-09-07 15:10 ` Joshua Branson via Guix-patches via
2020-09-08 14:31 ` [bug#42317] [PATCH] doc: cookbook: Adding a section "Running Guix on a Linode Server" Joshua Branson via Guix-patches via
2020-09-09 7:21 ` bug#42317: " 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=871rjdit74.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42317@debbugs.gnu.org \
--cc=jbranso@dismail.de \
/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).