From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Mingming Cao <cmm@us.ibm.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH, RFC] Add more intelligent handling of the mke2fs.conf installation process
Date: Wed, 16 Jul 2008 15:29:49 -0600 [thread overview]
Message-ID: <20080716212949.GV6239@webber.adilger.int> (raw)
In-Reply-To: <20080716175257.GF2167@mit.edu>
On Jul 16, 2008 13:52 -0400, Theodore Ts'o wrote:
> So if /etc/mk2fs.conf exists, but does not mention ext4dev, we will
> move it aside to /etc/mke2fs.conf.e2fsprogs-old and then install the
> new mke2fs.conf. If the /etc/mke2fs.conf file exists but does mention
> ext4dev, we install the new mke2fs.conf file as
> /etc/mke2fs.conf.e2fsprogs-new. In both we print warning to the user
> so they can manually make any changes as needed.
What about just adding the ext4/ext4dev stanzas into the existing file?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-07-16 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:24 Making it easier for end users to use ext4 Theodore Ts'o
2008-07-14 19:35 ` Eric Sandeen
2008-07-14 19:55 ` Theodore Tso
2008-07-14 21:27 ` Eric Sandeen
[not found] ` <1216172323.8292.23.camel@mingming-laptop>
[not found] ` <20080716023532.GO8185@mit.edu>
[not found] ` <1216227720.6424.7.camel@mingming-laptop>
2008-07-16 17:52 ` [PATCH, RFC] Add more intelligent handling of the mke2fs.conf installation process Theodore Tso
2008-07-16 18:24 ` Mingming Cao
2008-07-16 21:29 ` Andreas Dilger [this message]
2008-07-16 23:08 ` Theodore Tso
2008-07-15 5:22 ` Making it easier for end users to use ext4 Goswin von Brederlow
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=20080716212949.GV6239@webber.adilger.int \
--to=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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