From: ludo@gnu.org (Ludovic Courtès)
To: yoosty@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Quick-start guide
Date: Wed, 08 Jun 2016 14:47:47 +0200 [thread overview]
Message-ID: <8760tjkft8.fsf@gnu.org> (raw)
In-Reply-To: <CAGSLf80VTq42L=oop9dZcZRJz3ROGPxc0AwUFcjSCDxGSpYm9Q@mail.gmail.com> (yoosty@gmail.com's message of "Sat, 4 Jun 2016 13:00:17 -0700")
Hello!
yoosty@gmail.com skribis:
> +@node Quick Setup
> +@section Quick Setup
> +
> +So you just want the quick-and-dirty guide? Assuming you have some
> familiarity
> +with GNU/Linux systems in general and have installed one several times
> before
> +you can probably get started with a few notes while citing
> +@pxref{GNU Distribution} as necessary. As this is a quick-setup guide
> we'll use
> +some example defaults.
> +
> +The general idea is that you will:
> +@itemize
> +@item @uref{https://gnu.org/software/guix/download/, Download} the USB
> installer
> +@item Transfer the image to a USB stick (@pxref{USB Stick Installation})
> +using dd
> +@item Boot the USB stick
> +@item Configure @pxref{Preparing for Installation,Networking}
> +@item Set your @xref{Preparing for Installation,Disk Partitioning}
> +(using an msdos label instead of a gpt label might be easier at the moment)
> +@item Mount your partitions (e.g. /mnt)
> +@item Run (again, e.g. /mnt) @command{herd start cow-store /mnt}
> +@item Create a system configuration file using
> +@xref{Proceeding with the Installation} and
> +@xref{Using the Configuration System} as guides. It is suggested to start
> +with the bare-bones template as you can easily re-configure your system
> +once it is up.
> +@item Using /mnt/root/guix_configs/config00.scm as the example config file
> +and /mnt as the example install mount point, run
> +@command{guix system init /mnt/root/guix_configs/config00.scm /mnt}
> +@item Cross your fingers and grab a beer
> +@item If you're using reasonably new hardware and a bare-bones config
> +then guix should be done before your beverage and you can run
> +@command{reboot}
> +@end itemize
[...]
At first sight this seems redundant with the “System Installation”
section, no?
What shortcoming are you trying to address?
Thanks for helping out!
Ludo’.
next prev parent reply other threads:[~2016-06-08 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 20:00 [PATCH] Quick-start guide yoosty
2016-06-08 12:47 ` Ludovic Courtès [this message]
2016-06-11 13:43 ` yoosty
2016-06-11 17:49 ` Leo Famulari
2016-06-12 15:14 ` myglc2
2016-06-12 20:46 ` Ludovic Courtès
2016-06-15 5:07 ` yoosty
2016-06-16 10:51 ` Ludovic Courtès
2016-06-24 4:55 ` yoosty
2016-06-24 12:36 ` Ludovic Courtès
2016-06-13 0:40 ` John Darrington
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=8760tjkft8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=yoosty@gmail.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.
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).