Re: [RFC] mkfs config file bikeshed now!

["Darrick J. Wong" <darrick.wong@oracle.com>]

On Mon, Feb 26, 2018 at 04:15:06PM -0800, Luis R. Rodriguez wrote:
> On Mon, Feb 26, 2018 at 4:10 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
> >
> >
> > On 2/26/18 6:01 PM, Luis R. Rodriguez wrote:
> >>  IIRC with e2fsprogs profile parsers we could end up with something
> >> like:
> >>
> >> [defaults]
> >> foo=0
> >> bar=0
> >> [stuff]
> >>       some_release =  {
> >>               foo=1
> >>               bar=2
> >>       }
> >>       new_release = {
> >>               foo=2
> >>       }
> >
> > I can't tell what that means.  What's "stuff?"  Why would we need this sort of
> > nesting?
> 
> I'll leave the crafty examples to Darrick as he had some complex ideas
> in mind. On my part I was happy to not have to deal with the namespace
> stuff -- however I realized some may want it, so I had to mention both
> libraries libini_config and e2fsprogs profile parser do support it,
> just in different ways.

Well I /did/ have an even stupider parser in mind if segmented config
files got shot down...

/etc/xfs/mkfs/uek5.conf:
data.agcount 32
metadata.reflink 0

# mkfs.xfs -t uek5 /dev/sda

open("/etc/xfs/mkfs/${t_optarg}.conf")...

Then we can parse it with a simple fgets/strtok loop to tokenize the
input lines and feed them to the geometry arg parser.  But I'll go read
your paper all the way through first before I scribble more. :)

--D

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