| 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
| ||
|
Date: Tue, 18 Mar 2008 11:06:50 -0500 From: Eric Sandeen <sandeen@...hat.com> To: Theodore Tso <tytso@....EDU> CC: linux-ext4@...r.kernel.org Subject: Re: [E2FSPROGS, RFC] New mke2fs types parsing 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 -- 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
Powered by blists - more mailing lists