Thanks for these tips. You should put the examples in promises.cf or any of the files it inputs.
Francisco Reyes wrote: > milo...@gmail.com writes: > >> Live CD seems a better idea for me. > > Exactly. Live CD is the most widely usable. > >> the implementation (as long as you need my help at all). > > The Live CD should have two options, one to act as server and the second to > act as client. This way someone could quickly see a working environment and > start to make small changes to make it usable in their own operation. > > One of the biggest gripes I have so far with documentation I have seen is > that often times it fails to mention in what file one should put the > example. > > Take for instance: > http://www.cfengine.org/pages/starterkit > > Include it like this: > body common control > { > inputs => { "cfengine_stdlib.cf" }; > } > > > Include it where? I am sure that after one gets the basics one could figure > out where, but I was given that URL when I yet had absolutely no clue where > I should put that code. > > Then there is also > http://www.cfengine.org/manuals/cf3-solutions.html > Cfengine-Solutions > > Same issue. > No mention whatsoever where all the example code is supposed to live. > > Much of the docs at cfengine.org seem geared towards people upgrading or > that already have working knowledge of cfengine. > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine -- Mark Burgess ------------------------------------------------- Professor of Network and System Administration Oslo University College, Norway Personal Web: http://www.iu.hio.no/~mark Office Telf : +47 22453272 ------------------------------------------------- _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
