all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Ludovic Court??s <ludo@gnu.org>
Cc: 25286@debbugs.gnu.org, John Darrington <john@darrington.wattle.id.au>
Subject: bug#25286: cow-store destroys /tmp
Date: Mon, 2 Jan 2017 22:13:06 +0100	[thread overview]
Message-ID: <20170102211306.GA21120@jocasta.intra> (raw)
In-Reply-To: <87d1g5chtt.fsf@gnu.org>

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

On Mon, Jan 02, 2017 at 09:44:46PM +0100, Ludovic Court??s wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
     
     > 1. Boot from an installation-os image.
     > 2. cp /etc/issue /tmp
     > 3. ls -l /tmp    [observe that /tmp/issue exists]
     > 4. mount -t ext4 /dev/sda1 /mnt
     > 5. herd start cow-store /mnt
     > 6. ls -l /tmp  [observe that /tmp/issue has dissappeared]
     
     Indeed, ???cow-store??? bind-mounts /mnt/tmp (or whatever the target mount
     point is) to /tmp to make sure we have enough disk space if we need to
     build things.  This was done in commit
     0adabad72d58492f08975af0b6b837ebde32a51b in response to a bug report.
     
     Is it a problem for the installer?
     

It's not an insurmountable problem.  But it is a bit annoying.

J'

-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


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

      reply	other threads:[~2017-01-02 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 16:17 bug#25286: cow-store destroys /tmp John Darrington
2017-01-02 20:44 ` Ludovic Courtès
2017-01-02 21:13   ` John Darrington [this message]

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=20170102211306.GA21120@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=25286@debbugs.gnu.org \
    --cc=ludo@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.