From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix system disk-image: preset user profiles (packages & arbitrary data)
Date: Tue, 26 Jun 2018 13:35:04 +0200 [thread overview]
Message-ID: <87muvh6as7.fsf@gnu.org> (raw)
In-Reply-To: <871scxb7gc.fsf@gmail.com> (Pierre Neidhardt's message of "Sat, 23 Jun 2018 21:58:59 +0200")
Hello Pierre,
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> I'd like to built a live disk-image for a USB stick I carry around with
> me. Booting it would result in the exact configuration I have on my
> machine.
FWIW I did that a year or two ago with hacky modifications to the code.
It would be nice to make it accessible through the command-line
interface and API.
> I'm also wondering now if the USB stick is writable. That would solve
> it then.
As you found out, ‘disk-image’ creates a “volatile” image, where the
root file system is mounted read-only, with a writable overlayfs on top
of it. The main use case for this is the installation image where you
want to make sure you’re not going to modify what’s on the USB disk.
There are two things we could do:
• Add an option to make the root file system persistent (easy).
• Add an option to allow users to specify additional partitions in the
disk image (which would be writable). If you look at ‘qemu-image’
in (gnu system vm), you’ll see there’s already a list of partitions
there, and this is what needs to be modified.
My preference goes to the second option; it’s a bit more work, but it’s
not too hard.
HTH!
Ludo’.
next prev parent reply other threads:[~2018-06-26 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 19:58 guix system disk-image: preset user profiles (packages & arbitrary data) Pierre Neidhardt
2018-06-25 12:59 ` Pierre Neidhardt
2018-06-26 11:35 ` Ludovic Courtès [this message]
2018-06-26 13:01 ` Pierre Neidhardt
2018-06-28 13:00 ` Pierre Neidhardt
2018-07-02 15:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muvh6as7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@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.