Date: Sun, 15 Nov 2015 21:48:51 +0200 From: Dan Partelly <dan_partelly@rdsor.ro> To: "Simon J. Gerraty" <sjg@juniper.net> Cc: Adrian Chadd <adrian.chadd@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <EF093D34-B08D-430B-87D1-5B7612DFAB9A@rdsor.ro> In-Reply-To: <26127.1447610752@chaos> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
HI Simon, Thanks for the write-up . One question: >> The ability to get machine parsable output from OS components is a = big 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 ?=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF093D34-B08D-430B-87D1-5B7612DFAB9A>