From: Kay Sievers <kay.sievers@vrfy.org>
To: Masatake YAMATO <yamato@redhat.com>
Cc: kzak@redhat.com, rleigh@codelibre.net,
util-linux@vger.kernel.org, ssato@redhat.com
Subject: Re: /etc/fstab.d yes or not
Date: Mon, 23 Jan 2012 14:37:22 +0100 [thread overview]
Message-ID: <CAPXgP10LHyDJt_v5w1JyY4q0ouunVxJHr3QLgdL5VBPG28qOBQ@mail.gmail.com> (raw)
In-Reply-To: <20120123.222636.550210626606480400.yamato@redhat.com>
On Mon, Jan 23, 2012 at 14:26, Masatake YAMATO <yamato@redhat.com> 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. 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 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.
Kay
next prev parent reply other threads:[~2012-01-23 13:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 14:04 /etc/fstab.d yes or not Karel Zak
2012-01-20 14:20 ` Masatake YAMATO
2012-01-20 14:56 ` Kay Sievers
2012-01-20 15:57 ` Roger Leigh
2012-01-20 16:08 ` Kay Sievers
2012-01-24 0:19 ` Boaz Harrosh
2012-01-24 9:47 ` bastien ROUCARIES
2012-01-20 14:43 ` Attila Kinali
2012-01-20 14:59 ` Karel Zak
2012-01-20 15:03 ` Voelker, Bernhard
2012-01-20 15:20 ` Kay Sievers
2012-01-20 15:49 ` Roger Leigh
2012-01-20 16:13 ` Kay Sievers
2012-01-20 16:22 ` Roger Leigh
2012-01-20 17:59 ` Kay Sievers
2012-01-23 12:21 ` Karel Zak
2012-01-23 13:01 ` Masatake YAMATO
2012-01-23 13:03 ` Kay Sievers
2012-01-23 13:26 ` Masatake YAMATO
2012-01-23 13:37 ` Kay Sievers [this message]
2012-01-23 14:14 ` Masatake YAMATO
2012-01-23 14:32 ` Kay Sievers
2012-01-23 13:55 ` Theodore Tso
2012-01-23 22:07 ` Alan Cox
2012-01-24 1:06 ` Ted Ts'o
2012-01-20 18:20 ` Denys Vlasenko
2012-01-20 18:29 ` Kay Sievers
2012-01-20 18:47 ` Al Viro
2012-01-24 11:02 ` /etc/fstab.d yes or not (resolved) Karel Zak
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=CAPXgP10LHyDJt_v5w1JyY4q0ouunVxJHr3QLgdL5VBPG28qOBQ@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=kzak@redhat.com \
--cc=rleigh@codelibre.net \
--cc=ssato@redhat.com \
--cc=util-linux@vger.kernel.org \
--cc=yamato@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).