From owner-freebsd-current@freebsd.org  Tue Nov 17 06:29:32 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E452DA305B2
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 17 Nov 2015 06:29:32 +0000 (UTC)
 (envelope-from dan_partelly@rdsor.ro)
Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10])
 by mx1.freebsd.org (Postfix) with ESMTP id A8A311BE5
 for <freebsd-current@freebsd.org>; Tue, 17 Nov 2015 06:29:32 +0000 (UTC)
 (envelope-from dan_partelly@rdsor.ro)
Received: from [192.168.1.100] (unknown [79.119.24.18])
 by mail.rdsor.ro (Postfix) with ESMTP id 8F80E1C984;
 Tue, 17 Nov 2015 08:29:28 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues?
From: Dan Partelly <dan_partelly@rdsor.ro>
In-Reply-To: <18325.1447711377@chaos>
Date: Tue, 17 Nov 2015 08:29:28 +0200
Cc: Adrian Chadd <adrian.chadd@gmail.com>,
 freebsd-current <freebsd-current@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE360CD2-EEC8-460C-B839-144072A88C8E@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> <18325.1447711377@chaos>
To: "Simon J. Gerraty" <sjg@juniper.net>
X-Mailer: Apple Mail (2.3096.5)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 06:29:33 -0000


Management daemon with fine grained permission, extremely useful. Would =
Juniper consider donating to FreeBSD under a BSD license portions of =
this code, the MGD, which could be  reused in FreeBSD ? A fine grained =
permission system on daemon IPC and the scaffoldings of a management =
configuration daemon would help FreeBSD. I am very grateful your company =
helped us with libxo.  Now you could help with the other end of the =
system. =20

So Juniper, thank you for contributing, and please help the OS who makes =
us all tick.

Dan


> On 17 Nov 2015, at 00:02, Simon J. Gerraty <sjg@juniper.net> wrote:
>=20
> Dan Partelly <dan_partelly@rdsor.ro> wrote:
>>>> The ability to get machine parsable output from OS components is a =
big part of the success of Junos CLI, netconf etc.
>>=20
>> 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
> We didn't make any changes to the way tools are run as there was no
> need.
>=20
> 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.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"