From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: My experiences with partitioning according to the manual
Date: Tue, 19 Sep 2017 13:47:41 +0200 [thread overview]
Message-ID: <871sn26hb6.fsf@gnu.org> (raw)
In-Reply-To: <cb4100cf-89f3-c4f0-0928-7667b3b44614@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 18 Sep 2017 10:18:29 +0200")
Hi Hartmut,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> I'm not sure if it's worth, updating the manual, since the graphical
> installer may be here soon. But I want to share my experience to show
> that we strongly need the graphical installer :-)
That makes sense. :-) Thanks for sharing!
> *
>
> The first example is of a partitioning program is "cfdisk". I do non
> know this program, tried it and failed terrible. cfdisk seems to
> expect some script (huh?) to execute.
“cfdisk” (without any arguments) pops up an ncurses interface that’s
reasonably easy to use, at least for someone already familiar with
partitioning.
What makes you think that it expects a script?
> *
>
> The first step in the instructions should be to (optionally)
> initialize the partition table (for the case this is a fresh disk).
>
> o
>
> Should this a GPT partition table?
>
> o Which commands to issue?
> o parted mklabel gpt
There’s probably room for improvement, though we chose to not
(re)document everything about partitioning—it’s something that belongs
elsewhere IMO.
In fact, I tried to revive the “GNU Storage Guide”, which exists at
<https://alioth.debian.org/projects/storage-guide>, but the Debian folks
never managed to grant me access to this thing (!). See also
<https://lists.gnu.org/archive/html/guix-devel/2016-06/msg00127.html>.
At this point we might be better off starting anew…
> *
>
> How to align the first partition (with parted)?
I don’t remember having to worry about this. Did you have troubles?
> *
>
> How big should the boot partition be? Mine seems to have been too
> small, so I got warnings when formatting as FAT32.
I think the recommendation is to have 50+ MiB for /boot/efi. Marius,
could you confirm? We should definitely write it down.
> * FMPOV for the users it would be easier to have a list of commands to
> issue, like this:
>
> # parted /dev/sda
> mkpart primary fat32 1024s 20MB
> mkpart primary ext2 20MB 100%
> set 1 esp on
> name 1 boot
> name 2 my-root
> quit
>
> # mkfs.fat -F32 /dev/sda1
> # mkfs.ext4 -L my-root /dev/sda2
We don’t have the Parted commands because the manual suggests cfdisk.
I’ve added the ‘mkfs.fat’ command.
Thank you!
Ludo’.
next prev parent reply other threads:[~2017-09-19 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 8:18 My experiences with partitioning according to the manual Hartmut Goebel
2017-09-19 11:47 ` Ludovic Courtès [this message]
2017-09-19 13:37 ` Hartmut Goebel
2017-09-22 14:18 ` Ludovic Courtès
2017-09-20 15:47 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sn26hb6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.