Hey man i love the command line just as much as you do but mkdir -p /etc/e-smith/templates-custom/etc/smb.conf
/sbin/e-smith/expand-template /etc/smb.conf
is zzz I like the "Panel" but even that is not as feature rich as just going to the program you want and editing the config files.
So, improve the panels to add the features. However, keep in mind that the panels are there to simplify the server management for the typical untrained local admin - there are
intentionally less knobs available in the manager than in the raw configuration files.
The design underneath allows us the hide the complexity of the configuration files and services, while allowing for the complex custom changes for those who need them.
I dont know, I guess the whole "copy files from linux /etc directory, make them fragments, place them in /etc templates directory, make user create fragments in /templates-custom dir, expand said template to update configuration file that changes said linux /etc files is getting to me because the documentation is scattered all over the place and i'm used to going step by step.. unlike a linux "howto" that leaves you scratching yer head like this does..arrgg.....
I think you're missing the point that this is the system design - we want a guaranteed configuration and it's much easier to generate a configuration file from templates than it is to attempt to parse and modify in-place a huge number of varied format configuration files. In that direction lies madness.
The regular (and deep) directory structure is designed to make the code simpler and make customisation possible in a regular manner.
If you need to do it more than once, roll the changes into an RPM. Then you never have to do it again and everyone can benefit.
Yes, the developer documentation is lacking and needs to be improved. It is a matter of time and there aren't enough hours in the day. Feel like pulling the developer documentation together?