Primarily, I'll look at
- what facilities exist on the default configuration MP to enable a
configuration query process
- which additional facilities will be required to enable configuration
gathering and configuration change distribution at the MP (these additional
facilities would be candidates for inclusion in the base MP configuration of
the production-level MP)
- the methods for applying configuration changes, including the current
package management process, and various ad-hoc update processes
- the base configuration of the MP to establish the initial configuration
values
- "use case" validation, specifically in the area of using one MP as a
connector to all the other factory-configured MPs during the configuration
gathering phase of the tool
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
| ey david my name is victor tejada i am a computer sciences students i am developing my thesis on mesh network to use VoIP in rural community is a very interesting project to test a mesh potato what is the requirement to be a tester of mesh potato GOD BLESS YOU DIOS te Bendiga y Guarde --- On Tue, 12/1/09, David Rowe <da...@rowetel.com> wrote: |
|
|
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.