I haven't unpackaged an Evolved distribution yet, but my experience
with WindRiver licensing back in early 2000, it would be pricey.
As for FreeBSD, they could have gone the way of upgrading the
kernel (I saw some evidences about 10.x but no confirmation yet) but
depending of their initial work done during the 4.x days, switching
might have been a better financial choice.
Device support wouldn't be an issue pretty much all the worthy
stuff works on both... and with virtualization its not an really issue
anymore.
-----
Alain Hebert aheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
On 2020-10-13 13:22, Chris Adams wrote:
Once upon a time, Alain Hebert <aheb...@pubnix.net> said:
Since most of the reference implementation from their ASIC
provider with be Linux based ... the path of least resistance wins.
This is on the RE, which is just standard Intel x86 stuff (or IIRC ARM
for smaller stuff?).
And, I think, the "preference" of the majority of their own
devs/mgmt which never knew nothing but Linux =D.
I think with FreeBSD-based Junos, Juniper forked their chosen FreeBSD
release and made a bunch of customizations. That means every time they
need to get to newer FreeBSD (for newer hardware support, newer
features, etc.), it is a major operation. With Junos Evolved, it sounds
like they're going with somebody else's distribution (Wind River) and
adapting to fit it. Then when they need new support, they just get the
latest release and go (somebody else does all the hardware work).
It's my understand that the Linux kernel tends to have broader support
for new hardware than the FreeBSD kernel, but I haven't really looked in
a long time (I run Linux, not FreeBSD, so I could be wrong).
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
