[ECOS] Questions on ecosconfig

Nick Garnett nickg@ecoscentric.com
Fri Jan 16 16:48:00 GMT 2004


<kevin_lemay@agilent.com> writes:

> I had problems moving my .ecc files from 2.0 to the current CVS
> versions. This may have been something that I did but, I am looking
> for a consistent, reproducible way to generate the .ecc files that I
> need with the proper options.
>

Apart from things that may have changed name as a result of bug fixing
or new functionality, the main thing that will differ is the version
numbers in the cdl_configuration section at the front. Change those to
"current" and you should be OK.

> I was looking at ecosconfig, but I do not see how to set an option
> within a package (i.e. default boot script value).

ecosconfig doesn't really allow you to do that. Fine-grained changes
are meant to be done by editing the .ecc file.

Personally, for common config options I have a set of one or two entry
import files and an shell script to apply them. I seldom need to
explicitly edit the .ecc file.

> 
> I did look at the export file, but there appears to be much more
> than what I changed from the template in this file.
>

The export file will usually contains any changes that the inference
engine has made on your behalf, plus a few other things. However, an
export file is probably the best way of moving a configuration from
one version of eCos to another since there will be less to edit. Once
you have the file sorted out you can then use it to reproduce the
configuration in future. You could even make it into a template if you
want.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss



More information about the Ecos-discuss mailing list