linux-ext4 - Re: [E2FSPROGS, RFC] New mke2fs types parsing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47BC76A9.307@redhat.com>
Date:	Wed, 20 Feb 2008 12:51:21 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	"Theodore Ts'o" <tytso@....EDU>
CC:	linux-ext4@...r.kernel.org
Subject: Re: [E2FSPROGS, RFC] New mke2fs types parsing

Theodore Ts'o wrote:
> The following patch is a work in progress, but I'm sending it out so
> folks can take a look at it and comment on the general approach.
> 
> What this does is change how mke2fs -T works so it can take a comma
> separated list, so you can do things like this:
> 
> 	  mke2fs -T ext4,small,news

Is there some hierarchy of what these options are and how they fit
together?  i.e. small & news might go together (in bizarro world...) but
"small,large" wouldn't make sense - nor would -T ext3,ext4.  Or, if
somebody stores mail & news on the same fs, nad they say -T mail,news
but the mail & news types have conflicting directives...

how will you define what an acceptable composite of subtypes will be?

Thanks,

-Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html