Google
  Web www.spinics.net

Re: /etc/fstab.d yes or not

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


On Fri, Jan 20, 2012 at 17:22, Roger Leigh <rleigh@xxxxxxxxxxxxx> wrote:
> On Fri, Jan 20, 2012 at 05:13:12PM +0100, Kay Sievers wrote:
>> On Fri, Jan 20, 2012 at 16:49, Roger Leigh <rleigh@xxxxxxxxxxxxx> wrote:
>> > On Fri, Jan 20, 2012 at 03:04:44PM +0100, Karel Zak wrote:
>> >>  I'd like to add support for /etc/fstab.d to libmount. The library is
>> >>  currently used by mount, umount and mount.nfs. The goal is to use it
>> >>  on more places.
>> >>
>> >>  The /etc/fstab.d directory has been requested by people who maintains
>> >>  large number of mountpoints etc.
>> >>
>> >>  The directory is not replacement for /etc/fstab, it's additional place
>> >>  where you can describe your filesystems.
>> >
>> > As a general comment, I would like to use fstab.d for replacing
>> > the initscripts which mount kernel filesystems in Debian initscripts
>> > (sysvinit).  We currently hardcode the logic to mount each filesystem
>> > and additionally hardcode the defaults, and permit the defaults to
>> > be overridden by the user via /etc/default/* or via entries in
>> > /etc/fstab.  This could be done much more straightforwardly using
>> > entries such as /etc/fstab.d/kernfs and /etc/fstab.d/tmpfs etc.
>>
>> It is just very wrong to expose kernel filesystems to system mounts.
>> Please invent your own config if you want that for packaging. The
>> kernel filesystems do not belong in fstab, and for the same reason not
>> in fstab.d/.
>
> To be fair, these can be split into two categories: kernel filesystems
> such as procfs, sysfs etc., and special-purpose tmpfs mounts.  The
> former could be kept in the init scripts, but the latter are commonly
> required to be customised (or disabled) by admins, and the fstab format
> is the natural way to express this.  This would include tmpfs mounts
> for e.g. /run, /run/lock, /run/shm, potentially /tmp] and others, each
> of which has separate limits.
>
> Inventing custom file formats for these (as is the current situation)
> is both opaque to the admin and less amenable to preservation/upgrading
> of the admins customisations and the defaults.

I'm not talking about custom file formats, better just add a mount -c,
and do mount -c /etc/kernelfs.d/*.conf, or whatever will fit systemv
needs.

This is nothing really to share between systemd and systemv here. This
problem just does not exist for systemd.

And for systemv it should not be solved in mount(8), but in a systemv
specific part.

A change in common tools at that level breaks much more than it solves.

Kay
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Site Home]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Memory]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Rubini]     [Photo]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]     [Video 4 Linux]     [Linux Resources]

Powered by Linux