From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: disk-image and partitions
Date: Tue, 7 May 2019 11:10:00 +0900 [thread overview]
Message-ID: <8a9f3932-5f63-c148-b0ad-428e6981c81a@s.rendaw.me> (raw)
In-Reply-To: <871s1c20w4.fsf@gmail.com>
On 5/6/19 3:48 AM, Chris Marusich wrote:
> rendaw <7e9wc56emjakcm@s.rendaw.me> writes:
>
>> I think I'd like to use disk-image but a number of things were unclear
>> from the documentation:
>>
>> 1. What and how many partitions are created?
>>
>> Reading the -t parameter I assume it's an image with just 1 root
>> partition. If I need UEFI will an efi partition be created?
>>
>> 2. How can I refer to the created partitions in the config?
>>
>> Digging through the source it seems that in some modes of operation the
>> root partition is automatically created and there's a local uuid value
>> that's generated and shared between the partition + filesystem config,
>> but I didn't see that exposed anywhere.
>>
>> I have various additional storage attached so I can't guarantee device
>> order (sda/sdb/sdc).
>>
>> Thanks!
> You had a lot of questions, and it's been a couple weeks. Were you able
> to get all your questions answered, or is there still something you need
> help with?
>
Thanks, I think I've managed to figure this out. For anyone reading the
thread I've put my findings in
https://gitlab.com/rendaw/blog/blob/master/how_to_guix_for_those_who_dont.md
next prev parent reply other threads:[~2019-05-07 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 9:16 disk-image and partitions rendaw
2019-04-16 20:40 ` rendaw
2019-04-21 13:38 ` rendaw
2019-05-05 18:48 ` Chris Marusich
2019-05-07 2:10 ` rendaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-15 11:22 rendaw
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=8a9f3932-5f63-c148-b0ad-428e6981c81a@s.rendaw.me \
--to=7e9wc56emjakcm@s.rendaw.me \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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 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.