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 Mon, 23 Jan 2012 14:03:41 +0100, Kay Sievers <kay.sievers@xxxxxxxx> wrote
> On Mon, Jan 23, 2012 at 13:21, Karel Zak <kzak@xxxxxxxxxx> wrote:
>> On Fri, Jan 20, 2012 at 06:59:47PM +0100, Kay Sievers wrote:
>>> > 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 planned (I talked about it on dracut list few months ago). It
>>  means:
>>
>>    mount --fstab=<path> /mountpoint
>>
>>  to override the default /etc/fstab path. The <path> could be also a
>>  directory. So you can maintain our mountpoints in multiple files and
>>  mount(8) will be able to search in the files if --fstab=<path> is
>>  explicitly specified. I think this should be enough for initramfs
>>  scripts.
>>
>>  The problem is that the configuration won't be visible if
>>  --fstab is not specified -- this is possible to resolve probably
>>  by regular /etc/fstab.d only ;-)
> 
> It creates many times more problems that anybody has today.
> 
>>> This is nothing really to share between systemd and systemv here. This
>>> problem just does not exist for systemd.
>>
>>  Well, Masatake has RHEL customers who want to deploy systems with
>>  rpm/yum, %post scripts are poor solution because it's not too
>>  reliable and verification with rpm -V doesn't work. Do we have any
>>  answer for this use case?
> 
> We don't need one. System mounts just do not belong into packages,
> they are mandatory and hard-coded, or set by the admin and
> host-specific configured, and never to be dropped by RPM. RPM is not
> to be used for host-only system config.

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. 

Masatake YAMATO
 
> 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
--
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