On 01/20/2012 04:56 PM, Kay Sievers wrote: > > It's an old glibc API, and /etc/fstab is ABI, not a service config > file, which now can read more than one file. It's a very different > problem. It an ABI change, not a config extension. > Can't we have our cake and eat it too? I mean why not have both? The subsystem that you currently plan to parse the /etc/fstab.d/ will intelligently add the /etc/fstab.d/ entries to /etc/fstab before actually processing and mounting /etc/fstab. So the rpm guys have their /etc/fstab.d/ convenience and the rest of the ABI is kept intact. (If you can't bit them join them) Since /etc/fstab is hand edited as well. There are lots of smart things that can be done like a remark (#) marker at the end of the file that all /etc/fstab.d/ entries get to be added after. (And a comment for the user) and some smart duplicate removal of, and so on ... Even a marker per line added. Just my $0,017 Boaz -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
