[PC-BSD Testing] Config editing
yerenkow at uct.ua
Wed Dec 17 10:48:19 PST 2008
On 17.12.2008 20:25, Fabrizio Parrella wrote:
> not sure if this can help.. but give a look at the webmin script.. they
> already handle most of the configuration files that you described.. you may
> be able to grab some of their code and reuse it.
> webmin is written in Perl.
Thanks for link, omg, there 13000+ files :)
And each module have own, regular expression based config loader/saver,
that's have not much useful at least now.
Webmin is good thing, maybe we should use it in PC-BSD for configuring
Or include in installation DVD, and recommend it to user.
> ----- Original Message -----
> From: "A.Yerenkow"<yerenkow at uct.ua>
> To: "PC-BSD Testing list"<testing at lists.pcbsd.org>
> Sent: Wednesday, December 17, 2008 12:45 PM
> Subject: Re: [PC-BSD Testing] Config editing
>> Well guys, I gathered 200+ configs from my working PC-BSD and analysed
>> them :)
>> I now can categorise all configs into 8 different logic types:
>> - (Tab/Space)-based tables (newsyslog.conf, fstab)
>> - Simple keyValue without section (rc.conf, resolv.conf)
>> - Simple keyValue with section 1 level deep (smb.conf, php.ini)
>> - Xorg conf (xorg.conf)
>> - Apache-type (httpd.conf)
>> - Section with braces type, multi depth (named.conf, nginx.conf, wep.conf)
>> - login.conf type (login.conf) (Not really different, but my parser have
>> own opinion about newline and comments ;) )
>> - zfs.conf (have not sufficient info, look later, very similar to simple
>> and of course XML ones - I didn't count them, because they are in valid
>> easy parseable format already.
>> Currently I have working parser and some GUI, which can handle smb.conf
>> and other simple types, which preserves all correct comments and can
>> parse and understand that some values are valid sections and keyValue
>> pairs, only commented;
>> I'm working now on difficult parser cases, such as:
>> some key: value1, value2, /** comments **/, value 3
>> some key: value #comment
>> After part1 (parsing/editing/saving) completed, I'm going to part 2
>> (validating, advance validating) - such as check if specified path/file
>> exists, if entered value sane, etc. And after that, I'll try which is
>> hard ever - parse broken/mistyped configs.
>> So, I think soon we'll have one GUI for many cases while normal,
>> full-featured GUI not available.
>> BTW, I'll need some help for testing, any volunteers? :)
>> Testing mailing list
>> Testing at lists.pcbsd.org
> Testing mailing list
> Testing at lists.pcbsd.org
More information about the Testing