guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 1/4] gnu: Separate util-linux into three packages.


From: John Darrington
Subject: Re: [PATCH 1/4] gnu: Separate util-linux into three packages.
Date: Mon, 14 Nov 2016 18:46:28 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Mon, Nov 14, 2016 at 10:48:18AM +0100, Ludovic Court??s wrote:
     John Darrington <address@hidden> skribis:

     >      GuixSD doesn???t use the ???mount??? command to mount file systems 
so that
     >      shouldn???t have any influence.
     >
     > What does it use instead?
     
     The ???mount??? system call; see (gnu build file-systems).

I confess, I have not really thought about this before. But supposing somebody 
has in their /etc/config.scm:

  (file-systems 
   (cons*
    (file-system
      (device "my-root")
      (title 'label)
      (mount-point "/")
      (type "ext4"))
    (file-system
      (device "fileserver.example.com:/home")
      (title 'device)
      (mount-point "/home")
      (type "nfs4"))
    %base-file-systems))

Would the /home filesystem then get mounted on boot?
     
     > I'm irritated that util-linux has so many, completely unrelated things 
in it.  For example
     > it contains the "mount", "cal" and "col" commands.    Regardless of the 
NFS issues, I 
     > suggest we consider separating it anyway, into several packages all 
deriving from the common
     > source.
     
     The strategy is to stick to what upstream does, in general, and I???m not
     convinced splitting would buy us much (in terms of disk usage, for
     instance.)

In general I think that is a sensible strategy.  Splitting, would not buy us 
anything 
in terms of disk space, but I think it would mean less rebuilding when some 
configure 
option needs to be changed.

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: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]