unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 30667@debbugs.gnu.org
Subject: bug#30667: 'guix system vm' must keep mount_tag-length limited below 32 bytes for --expose and --share
Date: Thu, 1 Mar 2018 19:05:50 +0100	[thread overview]
Message-ID: <20180301190550.4e403961@alma-ubu> (raw)

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

I prepared a QEMU VM with:

./pre-inst-env  guix system vm \
--expose=/home/bjoern/digikam-testpool/=/image-pool \
../guix-systems/digikam-test.scm

Starting the VM it complained:

$> /gnu/store/zg5a42vcz4qf6h3yrdrijyaxkbhr967s-run-vm.sh 
qemu-system-x86_64: -virtfs local,path=/home/bjoern/digikam-testpool/,security_model=none,mount_tag=TAG_home_bjoern_digikam-testpool_: mount tag 'TAG_home_bjoern_digikam-testpool_' (33 bytes) is longer than maximum (31 bytes)

I haven't looked into the Guix code, but I suppose there is somewhere
a place where the command line and the '/etc/fstab' file is filled
with the mount tags.

Here we should check the tag-length and shrink it (uniquely) if
it is more than 31 bytes in size.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2018-03-01 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 18:05 Björn Höfling [this message]
2018-03-08 10:56 ` bug#30667: 'guix system vm' must keep mount_tag-length limited below 32 bytes for --expose and --share Ludovic Courtès
2018-03-10 14:46   ` Björn Höfling

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=20180301190550.4e403961@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=30667@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).