This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgHarald Welte has submitted this change and it was merged. Change subject: common/vty: "programs should not use the telnet VTY" ...................................................................... common/vty: "programs should not use the telnet VTY" Change-Id: Ic7e8c3663a2bfaf8dcb5752bf55ccb822b111c31 --- M common/chapters/vty.adoc 1 file changed, 9 insertions(+), 1 deletion(-) Approvals: Harald Welte: Looks good to me, approved Jenkins Builder: Verified diff --git a/common/chapters/vty.adoc b/common/chapters/vty.adoc index 17150b6..995fd2f 100644 --- a/common/chapters/vty.adoc +++ b/common/chapters/vty.adoc @@ -1,9 +1,17 @@ [[vty]] == The Osmocom VTY Interface -All interaction with Osmocom software is typically performed via an +All human interaction with Osmocom software is typically performed via an interactive command-line interface called the _VTY_. +NOTE: Integration of your programs and scripts should *not* be done via the +telnet VTY interface, which is intended for human interaction only: the VTY +responses may arbitrarily change in ways obvious to humans, while your scripts' +parsing will likely break often. For external software to interact with Osmocom +programs (besides using the dedicated protocols), it is strongly recommended to +use the Control interface instead of the VTY, and to actively request / +implement the Control interface commands as required for your use case. + The Osmocom VTY is used to * explore the current status of the system, including its configuration -- To view, visit https://gerrit.osmocom.org/4345 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ic7e8c3663a2bfaf8dcb5752bf55ccb822b111c31 Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder