From: Andreas Dilger <adilger@clusterfs.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] - Make mke2fs.c defaults match mke2fs.conf defaults
Date: Mon, 7 May 2007 14:27:00 -0700 [thread overview]
Message-ID: <20070507212700.GF8181@schatzie.adilger.int> (raw)
In-Reply-To: <463F838D.9030508@redhat.com>
On May 07, 2007 14:52 -0500, Eric Sandeen wrote:
> Theodore Tso wrote:
> > How likely do you think the case will be that mke2fs.conf would be
> > missing? I'm trying to figure out how high priority of an item this
> > really is.
>
> Well, not too likely, although for some reason I guess it happened in
> the installer root in FC6 or so. That's what raised the issue.
Ah, good point - there are probably lots of installers and rescue disks
that grab mke2fs but don't know anything about /etc/mke2fs.conf.
> > We could enhance the profile code so that it could read in the profile
> > from a memory buffer, and simply compile /etc/mke2fs.conf into mke2fs,
> > but that adds bloat --- the question is how necessary do we think that
> > really is?
>
> I guess it doesn't really sound *necessary* - it's just that if we have
> 2 different "defaults" and they drift, it can be confusing...
Since the shipped mke2fs.conf is only on the order of a few hundred bytes
I don't think it is a huge issue to include it. I like the idea of it
being compiled into the code and yet consistent with the default install.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-05-07 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 16:31 [PATCH] - Make mke2fs.c defaults match mke2fs.conf defaults Eric Sandeen
2007-05-07 19:47 ` Theodore Tso
2007-05-07 19:52 ` Eric Sandeen
2007-05-07 21:27 ` Andreas Dilger [this message]
2007-05-08 3:38 ` Theodore Tso
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=20070507212700.GF8181@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).