From: Wolf <wolf@wolfsden.cz>
To: help-guix@gnu.org
Subject: Few questions regarding the installation
Date: Sat, 17 Dec 2022 01:01:48 +0100 [thread overview]
Message-ID: <Y50G7LILgVP0BD6R@ws> (raw)
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
Hello,
I started experimenting with Guix (currently just trying to install
new system inside a qemu) and I have couple questions regarding the
installation process.
For my setup, I want to use LVM, so I'm glad it is distributed on the
installation image. However, I have a hard time actually using it. It
seems to be available both as lvm2 and lvm2-static:
root@gnu ~# find / -name pvcreate -executable
/gnu/store/84nrv3kl3vvsrwknnccnhjal6z7iksxc-lvm2-static-2.03.11/sbin/pvcreate
/gnu/store/vsxqa1l3p800flfzrq9vzq3v8bi0pfb7-lvm2-2.03.11/sbin/pvcreate
But it is not on the path:
root@gnu ~# pvcreate
bash: pvcreate: command not found
I'm currently calling it using
# /gnu/store/*-lvm2-s*/sbin/pvcreate /dev/mapper/foo
But I will be the first one to admit that it is not a great way. So
what would be a better way to either call it or add it into the path?
On IRC I was advised to try guix install lvm2-static, which does work
(after sourcing the profile), however it does download the package
from the internet. That seems pointless, since I already have one
locally (as seen in the output of find above), so I would prefer to
use that one.
Another question is how to undo the effect of running herd start
cow-store /mnt. I did try the obvious (herd stop cow-store), but that
does not seem to do the trick. So, how can I do it?
Thank you,
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-12-17 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 0:01 Wolf [this message]
2022-12-17 0:37 ` Few questions regarding the installation Felix Lechner via
2022-12-17 2:41 ` Tobias Geerinckx-Rice
2022-12-18 23:21 ` Wolf
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=Y50G7LILgVP0BD6R@ws \
--to=wolf@wolfsden.cz \
--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.
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).