From: Marius Bakke <mbakke@fastmail.com>
To: Simon Josefsson <simon@josefsson.org>, help-guix@gnu.org
Subject: Re: What LVM support is missing?
Date: Mon, 04 May 2020 18:10:33 +0200 [thread overview]
Message-ID: <87368f1y12.fsf@devup.no> (raw)
In-Reply-To: <87ftcfu9gv.fsf@latte.josefsson.org>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Simon Josefsson <simon@josefsson.org> writes:
> The manual is quite clear that LVM support is missing:
>
> https://guix.gnu.org/manual/en/html_node/Limitations.html
>
> This held me back from using guix as the OS for my virtualization
> servers since I use LVM for virtual machines. However, one evening I
> was curious how difficult it would be to fix the above limitation, so I
> started with a simple 'guix package -i lvm2' and that allowed me to get
> LVM to work and I can't really notice anything missing.
>
> Before producing a patch to correct the manual, could someone explain
> what LVM support was intended that was missing? Does a reference to LVM
> as a limitation of Guix still make sense?
What's missing is support in the configuration system: the ability to
declare a LVM mapped device in the OS configuration and expect 'guix
system init', 'guix system reconfigure' etc to work.
LVM 2.03 simplifies things a bit, but I don't know of any recent
attempts to add LVM support to the configuration system.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-04 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 13:16 What LVM support is missing? Simon Josefsson
2020-05-04 16:10 ` Marius Bakke [this message]
2020-05-06 7:33 ` Simon Josefsson
2020-05-04 16:37 ` Michael Rohleder
2020-05-06 7:40 ` Simon Josefsson
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=87368f1y12.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=simon@josefsson.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.
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).