Re: [RFC] mkfs config file bikeshed now!

[Theodore Ts'o <tytso@mit.edu>]

So number one, unlike everyone else, I didn't reinvent the wheel.  I
grabbed the same wheel I wrote for MIT Kerberos years before.  :-)

Number two, for examples for I wanted the nesting, from MIT Kerberos:

[realms]
         ATHENA.MIT.EDU = {
             kdc = kerberos.mit.edu
             kdc = kerberos-1.mit.edu
             kdc = kerberos-2.mit.edu:750
             admin_server = kerberos.mit.edu
             master_kdc = kerberos.mit.edu
             default_domain = mit.edu
         }
         EXAMPLE.COM = {
             kdc = kerberos.example.com
             kdc = kerberos-1.example.com
             admin_server = kerberos.example.com
         }

And from the file system world, from /etc/mke2fs.conf:

[fs_types]
	ext3 = {
		features = has_journal
	}
	ext4 = {
		features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
		inode_size = 256
	}
	small = {
		blocksize = 1024
		inode_size = 128
		inode_ratio = 4096
	}
	...


It's been handy inside Google since we have different file system
configs for different use cases, so we do things like:

	mke2fs -T foo-use /dev/sdX

and
	mke2fs -T bar-use /dev/sdX


... where foo-use and bar-use would be subsections under fs_types.

But hey, to be clear, I'm not the one trying to claim everyone should
use my library (even though it's the best looking and above-average,
ala Lake Wobegon. :-)

       	       	     	    	     	  - Ted