Date: Mon, 16 Nov 2015 14:02:57 -0800 From: "Simon J. Gerraty" <sjg@juniper.net> To: Dan Partelly <dan_partelly@rdsor.ro> Cc: Adrian Chadd <adrian.chadd@gmail.com>, freebsd-current <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <18325.1447711377@chaos> In-Reply-To: <EF093D34-B08D-430B-87D1-5B7612DFAB9A@rdsor.ro> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <CAJ-Vmokfo_BGWji9TrgQ40oRxqht9-2iEZVon7aQxR_93Ufxyg@mail.gmail.com> <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro> <26127.1447610752@chaos> <EF093D34-B08D-430B-87D1-5B7612DFAB9A@rdsor.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Partelly <dan_partelly@rdsor.ro> wrote: > >> The ability to get machine parsable output from OS components is a bi= g part of the success of Junos CLI, netconf etc. > = > Once you get machine parsable output, and feed it to your GUIs , WEB, > other tools, and modify it, how do you feed it back to your underlying > OS ? We didn't make any changes to the way tools are run as there was no need. All requests - whether from CLI, NETCONF etc, are channeled into the MGD (management daemon) to verify input, permissions etc (Junos implements very fine grained permission system), and act accordingly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18325.1447711377>