All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Updating /etc/protocols
Date: Fri, 25 Oct 2013 21:02:32 -0300	[thread overview]
Message-ID: <526B0698.4010400@zacarias.com.ar> (raw)
In-Reply-To: <CANGB_5aEjRq1=5mwPdJ8R9Q20aRdZ2JGpy2giGvz9QhMUoAfdQ@mail.gmail.com>

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.

  reply	other threads:[~2013-10-26  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 23:50 [Buildroot] Updating /etc/protocols Peter Sanford
2013-10-26  0:02 ` Gustavo Zacarias [this message]
2013-10-26  0:19   ` Peter Sanford
2013-10-26  6:55     ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=526B0698.4010400@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.