Mike Kupfer <[EMAIL PROTECTED]> wrote:
> I agree that software outside of ON should not rely on the current
> libcmd.
>
> And this probably doesn't need to be said, but just so we're all on the
> same page: if the current libcmd goes away, some sort of library should
> take its place. Rewriting a
Mike Kupfer wrote:
"Roland" == Roland Mainz <[EMAIL PROTECTED]> writes:
Roland> Note: [libcmd] should not be used if possible. I have plans for it -
Roland> and I am not sure whether the current API will surive them
I agree that software outside of ON should not rely on the current
libcmd.
T
> "Roland" == Roland Mainz <[EMAIL PROTECTED]> writes:
Roland> Note: [libcmd] should not be used if possible. I have plans for it -
Roland> and I am not sure whether the current API will surive them
I agree that software outside of ON should not rely on the current
libcmd.
And this probably
Roland Mainz <[EMAIL PROTECTED]> wrote:
> > > why not having a lib function that would help parsing/reading/writing
> > > such a file ?
> >
> > There actually is an undocumented/private library much like that already for
> > reading the files in that format in /etc/default - libcmd.
> > http://c
Roland Mainz writes:
> > SMF was designed to help unify system/service configuration. It isn't
> > used to its full capabilities there yet, but expect to see more Solaris
> > system and service configuration moving into the SMF repository (also known
> > as SCF).
>
> Is this wise ? AIX already is
[EMAIL PROTECTED] wrote:
> Alan Coopersmith writes:
> > Yann POUPET wrote:
>
> > > Thus maybe writing config files with an XML format would help ?
> > >
> > > Furthermore, as I said before, there may be a lot of config files.
> > > Why not have ALL configuration into a single file ? That could be
Alan Coopersmith wrote:
> Yann POUPET wrote:
> > Since many (most ?) config files may be something like :
> >
> > # some comments
> > param1 = arg1
> > param2 = arg2
> > param3 = arg3
> > # another comment
> > param4 = arg4
> >
> > why not having a lib function that would help parsing/reading/writi
Alan Coopersmith writes:
> Yann POUPET wrote:
> > Thus maybe writing config files with an XML format would help ?
> >
> > Furthermore, as I said before, there may be a lot of config files.
> > Why not have ALL configuration into a single file ? That could be a hash, a
> berkeleydb file (I think
>
> > Thus maybe writing config files with an XML format would help ?
> >
> > Furthermore, as I said before, there may be a lot of config files.
> > Why not have ALL configuration into a single file ? That could be a hash, a
> > berkeleydb file (I think E17 uses such files for conf), or whateve
Yann POUPET wrote:
Since many (most ?) config files may be something like :
# some comments
param1 = arg1
param2 = arg2
param3 = arg3
# another comment
param4 = arg4
why not having a lib function that would help parsing/reading/writing such a
file ?
There actually is an undocumented/private
Yann POUPET wrote:
why not having a lib function that would help3 parsing/reading/writing such a
file ?
With a configuration file such as the example above, one could think about a
function that would return the value of arg1
arg = cfgfile_readparam("/file/location",param1)
We could also have a
Hello,
I guess this may have been discussed many times, but after a quick search in
the forum, I could not find any thread about it (but it was a really quick
search ...).
OpenSolaris, as well as most (all ?) unixes, uses configuration files for many
applications. All applications needing some
12 matches
Mail list logo
