On 2/26/18 5:56 PM, Darrick J. Wong wrote: >>> For example, say we had a /etc/xfs.conf file shipping with xfsprogs: >> /etc/mkfs.xfs.conf please, this configures mkfs and nothing else, right? > Ok. I mean, I might let that be $sysconfdir/mkfs.xfs.conf or something, > but I agree about the filename component of the path. > *nod* Also a $sysconfdir/mkfs.xfs.conf.d/ scanning scheme might be a useful feature. Or if we ban inheritance between sections (please), as darrick stated offline maybe just allowing configfile specification on the commandline so that you could point to /etc/xfs/mkfs/$FOO_OS.conf The point would be that over-arching OS config file package could drop in all the relevant config files for its defaults rather than munging it all together in one config file. I.e. if ceph wants one thing and glusterfs wants another they could each supply their own mkfs.xfs config file w/o hassle. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
