Re: /etc/fstab.d yes or not

[Kay Sievers <kay.sievers@xxxxxxxx>]

On Mon, Jan 23, 2012 at 15:14, Masatake YAMATO <yamato@xxxxxxxxxx> wrote:
> On Mon, 23 Jan 2012 14:37:22 +0100, Kay Sievers <kay.sievers@xxxxxxxx> wrote
>>> What I want is packaging the system mounts.
>>> Consider setting up multiple hosts which mount the same nfs filesystem
>>> to the same mount point. It the mount point is in a rpm package, it
>>> can be used both in kickstart file and from yum command line. In
>>> addition yum update can be used when the name or ip of nfs server is
>>> changed; Just create the new release of the rpm package which holds
>>> new mount point deification. In stead of nfs, you can consider smb or
>>> iso images as examples.
>>
>> That sounds very wrong to do. This is admin territory and not package
>> management.
>
> I'm thiking about the admin manages packages which are installed to
> the host.
>
>> There are tools sync and deploy /etc setting per-machine
>> across big networks, and RPM is surely not the right thing to use
>> here.
>
> (RPM works fine daily "yum update" done by users on the world.)
> Of course I'm thinking about the admin runs her/his own yum repository.
>
>> RPM is for the operating system, not for host configuration. Most
>> stuff in /etc is marked as config for that exact reason. First, static
>> system-config does not belong in /etc, second non-admin editable files
>> just do not belong in /etc. It's all wrong, just as the misguided
>> entire fstab.d/ feature to start with.
>
> It is not so simple.
>
> $ rpm -qf /etc/yum.repos.d/fedora.repo
> fedora-release-14-1.noarch
>
> Admin can edit fedora.repo, but generally it is assumed as static
> file.
>
> $ rpm -q --queryformat "%{NAME}: %{FILEFLAGS:fflags}\n" -f /etc/udev/rules.d/*.rules
> hplip-common:
> hplip-common:
> libfprint:
> qemu-system-x86:
> alsa-utils:
> hal: c
> libdrm: c
> vbetool:
> bluez:
> fuse:
> gpsd: cn
>
> Some are marked as config as you said. The other are not. I think the packages
> may think their rules files as static data.

Yes, and the udev rules in /etc are admin-only, it should be empty,
static RPM-provided rules belong into /lib/udev/rules.d/. Many of them
moved already in later OS releases. Everything else in the list is a
bug, or legacy nobody cared so far.

Some stuff in /etc is hard to fix/change because it is like that since
forever, but that is no reason to add new stuff to that broken model.

And inventing new static files in /etc is as wrong as packaging static
system mounts with RPM and as wrong as the entire fstab.d/ thing.

Please just don't do anything like that, it's not where we want to be
or want to go in the future.

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