From: "Thompson, David" <dthompson2@worcester.edu>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] build: file-systems: Allow for bind mounting regular files.
Date: Sun, 2 Aug 2015 08:43:10 -0400 [thread overview]
Message-ID: <CAJ=RwfbgKQ=3yetHsEpGFdSaHhAazYozQ3Mv5fR=VYS0uvObGA@mail.gmail.com> (raw)
In-Reply-To: <87bnepriup.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Sun, Aug 2, 2015 at 8:10 AM, Alex Kost <alezost@gmail.com> wrote:
> David Thompson (2015-08-01 22:17 +0300) wrote:
>
>> diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm
>> index c58d23c..f0d6f70 100644
>> --- a/gnu/build/file-systems.scm
>> +++ b/gnu/build/file-systems.scm
>> @@ -305,6 +305,10 @@ the following:
>> fsck code device)
>> (start-repl)))))
>>
>> +(define (regular-file? file-name)
>> + "Return #t if FILE-NAME is a regular file."
>> + (eq? (stat:type (stat file-name)) 'regular))
>
> There are similar procedures in (guix build utils): 'directory-exists?',
> 'executable-file?' and 'symbolic-link?'. So I think it is better to put
> 'regular-file?' there. WDYT?
Sure, that makes sense. Done.
- Dave
[-- Attachment #2: 0001-build-file-systems-Allow-for-bind-mounting-regular-f.patch --]
[-- Type: text/x-patch, Size: 2283 bytes --]
From 1b2413bd06b1e769edfbe4d170de41398015a67d Mon Sep 17 00:00:00 2001
From: David Thompson <dthompson2@worcester.edu>
Date: Sat, 1 Aug 2015 13:43:33 -0400
Subject: [PATCH] build: file-systems: Allow for bind mounting regular files.
* guix/build/utils.scm (regular-file?): New procedure.
* gnu/build/file-systems.scm (mount-file-system): Create a regular file
instead of a directory when bind mounting a regular file.
---
gnu/build/file-systems.scm | 11 ++++++++++-
guix/build/utils.scm | 5 +++++
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm
index c58d23c..f0b4b79 100644
--- a/gnu/build/file-systems.scm
+++ b/gnu/build/file-systems.scm
@@ -339,7 +339,16 @@ run a file system check."
(flags (mount-flags->bit-mask flags)))
(when check?
(check-file-system source type))
- (mkdir-p mount-point)
+
+ ;; Create the mount point. Most of the time this is a directory, but
+ ;; in the case of a bind mount, a regular file may be needed.
+ (if (and (= MS_BIND (logand flags MS_BIND))
+ (regular-file? source))
+ (begin
+ (mkdir-p (dirname mount-point))
+ (call-with-output-file mount-point (const #t)))
+ (mkdir-p mount-point))
+
(mount source mount-point type flags options)
;; For read-only bind mounts, an extra remount is needed, as per
diff --git a/guix/build/utils.scm b/guix/build/utils.scm
index 676a012..b9543ed 100644
--- a/guix/build/utils.scm
+++ b/guix/build/utils.scm
@@ -38,6 +38,7 @@
directory-exists?
executable-file?
symbolic-link?
+ regular-file?
call-with-ascii-input-file
elf-file?
ar-file?
@@ -110,6 +111,10 @@
"Return #t if FILE is a symbolic link (aka. \"symlink\".)"
(eq? (stat:type (lstat file)) 'symlink))
+(define (regular-file? file-name)
+ "Return #t if FILE-NAME is a regular file."
+ (eq? (stat:type (stat file-name)) 'regular))
+
(define (call-with-ascii-input-file file proc)
"Open FILE as an ASCII or binary file, and pass the resulting port to
PROC. FILE is closed when PROC's dynamic extent is left. Return the
--
2.4.3
next prev parent reply other threads:[~2015-08-02 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 19:17 [PATCH] build: file-systems: Allow for bind mounting regular files David Thompson
2015-08-02 12:10 ` Alex Kost
2015-08-02 12:43 ` Thompson, David [this message]
2015-08-02 12:51 ` Thompson, David
2015-08-02 13:31 ` Andreas Enge
2015-08-03 12:47 ` Alex Kost
2015-08-06 12:22 ` Thompson, David
2015-08-07 7:06 ` Alex Kost
2015-08-18 15:52 ` Ludovic Courtès
2015-08-18 16:43 ` Thompson, David
2015-08-08 18:28 ` Thompson, David
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='CAJ=RwfbgKQ=3yetHsEpGFdSaHhAazYozQ3Mv5fR=VYS0uvObGA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=alezost@gmail.com \
--cc=guix-devel@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.