Re: [Config4gnu-developer] flatfile not being written

[Justin Y. <ju...@sk...>]

On Mon, 2002-10-28 at 00:28, Gregory Richard Troisi Stoll wrote:
> I updated the flatfile parser/unparser to just have properties with name
> "module" (and so comments are not shown as well), so it looks much nicer.
> I have two questions.
> 
> 1) Now when I modify the properties and select "activate", the file is not
> written out to /etc/modules (and I'm running as root).  Did I somehow
> break this in the new parser/unparser, and if so, any suggestions of how
> to fix it?

Find your config4gnu.xml and look for the section for Boot Modules. 
Should be towards the end.  The writecommand tells CFG what to do to
write the file.  To help prevent CFG from really messing with your
system, it currently doesn't write ANY changes to /etc.  Instead, the
writecommands tell it to write to /tmp, so chances are your updated file
is in /tmp/modules.new.  If not, then I will have to look into it more. 
BTW, I would suggest *not* running CFG as root at this point, just in
case someone accidentally tells it to really overwrite your /etc files.

> 2) Presumably, since the flatfile format is used in a number of different
> places, we should either use a generic name for properties (like "item" or
> something), or we should have a mechanism for passing in specific names
> (like "module") to the parser and unparser.  I think passing in specific
> names would be a bit user-friendlier, since then it is clear what the user
> is viewing and changing.  Is there currently a way to do this?

Well, yeah, there is a problem with the names of things.  We want to
keep the XML tags to a minimum, so making a new tag is probably not the
way to go.  We have been kicking around the idea of taking the
name="blah" out of the <property> tag itself and instead making a <name>
tag under the <property> tag.  Then, we would add a <displayname> tag
under <property> which contains the name that the UI should display it
as (which may be Module, Alias, etc. OR a translation of the <name> into
the user's native language).  If you want to make your parser do this,
and use <displayname> to add this information, that would be fine.  I
would suggest then just leaving <name> empty (but still including it).

Justin


-- 
SkiingYAC.com
Custom Solutions
su...@sk...
http://www.SkiingYAC.com