linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Ikey Doherty <michael.i.doherty@intel.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Support a stateless configuration by default
Date: Mon, 8 Jun 2015 12:32:51 -0400	[thread overview]
Message-ID: <20150608163251.GA4026@thunk.org> (raw)
In-Reply-To: <1432306620-6368-1-git-send-email-michael.i.doherty@intel.com>

On Fri, May 22, 2015 at 03:57:00PM +0100, Ikey Doherty wrote: With
> this change, distribution defaults are now read from the
> distribution defaults directory,
> /usr/share/defaults/e2fsprogs. These files are expected to be the
> sensible defaults required for basic operation.
> 
> Site administrators may still override the default configuration by
> placing the files within the site config directory (i.e. /etc) - and
> those configuration values will be read instead. The distribution
> files within the defaults directory are percieved as immutable, and
> as such resiliant to upgrades over time.
> 
> A side effect of this stateless configuration is that a site
> admiministrator is able to reset their configuration to the sane
> defaults by simply removing the files they placed within the site
> configuration directory.
> 
> To users already making use of an altered configuration within /etc,
> this change is transparent and does not affect existing operation.
> 
> The fundamental goal within this change, and stateless itself, is to
> separate OS configuration from the system administrator
> configuration.

I'm willing to take a patch which checks /usr/share/defaults/e2fsprogs
first, but not to install the config file instead of /etc/mke2fs.conf.
This is *not* yet the default, and the vast majority of Linux systems
are still using /etc/mke2fs.conf.  If a particular distribution wants
to use a diferent packaging scheme, that's fine, but until it's the
common case, I'm not going to break existing systems by changing the
default installation location.

That being said, it should also be noted that mke2fs will work just
fine without /etc/mke2fs.conf being present (we take the default
mke2fs.conf and create default_profile.o which gets used if the
default profile isn't present), and we currently don't ship a default
e2fsck.conf file.  So you really don't have to do anything special to
get the stateless setup that you desire.

						- Ted

      reply	other threads:[~2015-06-08 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 14:57 [PATCH] Support a stateless configuration by default Ikey Doherty
2015-06-08 16:32 ` Theodore Ts'o [this message]

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=20150608163251.GA4026@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=michael.i.doherty@intel.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).