* [Buildroot] Updating /etc/protocols
@ 2013-10-25 23:50 Peter Sanford
2013-10-26 0:02 ` Gustavo Zacarias
0 siblings, 1 reply; 4+ messages in thread
From: Peter Sanford @ 2013-10-25 23:50 UTC (permalink / raw)
To: buildroot
Today I noticed that /etc/protocols found in skeleton is quite old (2004)
and has a number of common protocols missing from it. It looks like the
current /etc/protocols was pulled from netbsd. Does it make sense to update
it based on the current netbsd file[1]?
-Peter
[1]
http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/etc/protocols?content-type=text/plain&only_with_tag=MAIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131025/7cd90451/attachment.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] Updating /etc/protocols
2013-10-25 23:50 [Buildroot] Updating /etc/protocols Peter Sanford
@ 2013-10-26 0:02 ` Gustavo Zacarias
2013-10-26 0:19 ` Peter Sanford
0 siblings, 1 reply; 4+ messages in thread
From: Gustavo Zacarias @ 2013-10-26 0:02 UTC (permalink / raw)
To: buildroot
On 10/25/2013 08:50 PM, Peter Sanford wrote:
> Today I noticed that /etc/protocols found in skeleton is quite old
> (2004) and has a number of common protocols missing from it. It looks
> like the current /etc/protocols was pulled from netbsd. Does it make
> sense to update it based on the current netbsd file[1]?
The updated NetBSD protocols has a lot of comments/emails addresses that
would take up space [1]. You could just use some linux distribution
/etc/protocols or trim it down and send a patch.
For that matter /etc/services could be updated too.
Regards.
[1] - Not that much, but still.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] Updating /etc/protocols
2013-10-26 0:02 ` Gustavo Zacarias
@ 2013-10-26 0:19 ` Peter Sanford
2013-10-26 6:55 ` Peter Korsgaard
0 siblings, 1 reply; 4+ messages in thread
From: Peter Sanford @ 2013-10-26 0:19 UTC (permalink / raw)
To: buildroot
On Fri, Oct 25, 2013 at 5:02 PM, Gustavo Zacarias
<gustavo@zacarias.com.ar>wrote:
>
> The updated NetBSD protocols has a lot of comments/emails addresses that
> would take up space [1]. You could just use some linux distribution
> /etc/protocols or trim it down and send a patch.
> For that matter /etc/services could be updated too.
Yeah that was basically why I was asking. I also wanted to verify that
there wasn't any licencing reasons for using a BSD source originally. If
that's the case I will probably just grab the Debian version[1] which is
quite a bit more concise than the NetBSD one.
[1] -
http://bazaar.launchpad.net/~ubuntu-branches/debian/jessie/netbase/jessie/view/head:/etc-protocols
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131025/b16c3ea1/attachment.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] Updating /etc/protocols
2013-10-26 0:19 ` Peter Sanford
@ 2013-10-26 6:55 ` Peter Korsgaard
0 siblings, 0 replies; 4+ messages in thread
From: Peter Korsgaard @ 2013-10-26 6:55 UTC (permalink / raw)
To: buildroot
>>>>> "Peter" == Peter Sanford <psanford@nearbuysystems.com> writes:
> Yeah that was basically why I was asking. I also wanted to verify
> that there wasn't any licencing reasons for using a BSD source
> originally. ?If that's the case I will probably just grab the Debian
> version[1] which is quite a bit more concise than the NetBSD one.
Sounds good, please do.
Thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-10-26 6:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-25 23:50 [Buildroot] Updating /etc/protocols Peter Sanford
2013-10-26 0:02 ` Gustavo Zacarias
2013-10-26 0:19 ` Peter Sanford
2013-10-26 6:55 ` Peter Korsgaard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox