All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [E2FSPROGS, RFC] New mke2fs types parsing
Date: Tue, 18 Mar 2008 11:06:50 -0500	[thread overview]
Message-ID: <47DFE89A.3080402@redhat.com> (raw)
In-Reply-To: <20080318135254.GA27000@mit.edu>

Theodore Tso wrote:

> So what do people think about this proposal as an alternative to
> what's been discussed?
> 
> The filesystem type comes from defaults.fstype in mke2fs.conf, which
> can be overridden by /sbin/mkfs.*, which in turn can be overriden by
> the -t option.  If the the filesystem type does not begin with the
> string "ext" it will be rejected with an error.  Call this the
> "fs_type".
> 
> In addition, a list of types can be specified by the user using the -T
> flag.  Call it "type_list", and it consists of one or more usage types
> separated by commas.  If a type_list is not specified by -T, mke2fs
> use a single type based on the size of the block device, selected from
> the list "floppy, small, default".
> 
> Mke2fs will search mke2fs.conf for configuration parameters first by
> looking at the fs_type, and then successively in the usage types found
> in type_list.  Parameters found later override earlier parameters.
> 
> I can get behind this, as it's compatible with what came before, and
> simpler in the general case, and still as expressive for power users
> who want to do really complex things in their mke2fs.conf file.
> 
> What do people think?

Ted, this sounds good to me.

-Eric

  reply	other threads:[~2008-03-19 21:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 14:06 [E2FSPROGS, RFC] New mke2fs types parsing Theodore Ts'o
2008-02-20 18:51 ` Eric Sandeen
2008-02-20 22:20   ` Theodore Tso
2008-02-20 22:28     ` Eric Sandeen
2008-02-21  8:52     ` Andreas Dilger
2008-02-21 13:35       ` Theodore Tso
2008-03-17 21:29     ` Eric Sandeen
2008-03-18  2:20       ` Theodore Tso
2008-03-18  3:23         ` Eric Sandeen
2008-03-18  4:23           ` Theodore Tso
2008-03-18  5:16             ` Eric Sandeen
2008-03-18 11:01               ` Theodore Tso
2008-03-18 13:11                 ` Eric Sandeen
2008-03-18 13:52                   ` Theodore Tso
2008-03-18 16:06                     ` Eric Sandeen [this message]
2008-03-20 19:17                     ` Eric Sandeen
2008-03-20 20:49                       ` Theodore Tso
2008-03-19  3:36                 ` Andreas Dilger

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=47DFE89A.3080402@redhat.com \
    --to=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.