br>
&gt;&gt; <br>
&gt;&gt; Anyway, I&#39;m a user, albeit a small user, of RIP and wouldn&#39=
;t object to its<br>
&gt;&gt; removal from FreeBSD if there were a small footprint alternative.=
=C2=A0 I&#39;ve used<br>
&gt;&gt; FRR and VyOS a bit and they are overkill as replacements.<br>
&gt;&gt; <br>
&gt;&gt; Your email doesn&#39;t justify its removal other than to say you a=
re unconvinced<br>
&gt;&gt; of the value of shipping it.=C2=A0 As a user I definitely see the =
value.=C2=A0 I<br>
&gt;&gt; understand that there is always a cost to providing code, but that=
 wasn&#39;t<br>
&gt;&gt; suggested as a reason.=C2=A0 All APIs, modules, utilities, etc. ne=
ed to regularly<br>
&gt;&gt; justify their presence in the OS.<br>
&gt;&gt; <br>
&gt;&gt; If it must be removed, is there any way to fork the FreeBSD routed=
 and<br>
&gt;&gt; route6d to a port?=C2=A0 Or would that defeat the purpose of remov=
ing it in the<br>
&gt;&gt; first place?<br>
&gt; <br>
&gt; Yeah, where did that recent trend came to FreeBSD to remove perfectly<=
br>
&gt; working code??<br>
&gt; <br>
&gt; There are more and more ideas in recent times like this.<br>
&gt; <br>
&gt; Architectures removal, drivers removal, backward compatibility<br>
&gt; removal. While basic functions become unstable and unreliable. Looks<b=
r>
&gt; more like diversion and sabotage than progress.<br>
&gt; <br>
&gt; If anything is about to be moved out from SRC for a really good reason=
<br>
&gt; it should be available in ports and not in /dev/null.<br>
&gt; <br>
<br>
</blockquote></div>

--000000000000d8495206188160b7--