public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: iana-etc
Date: Mon, 14 Feb 2022 14:33:09 +0000	[thread overview]
Message-ID: <AB38B137-3F4C-49EA-B7F6-AF79FAE3E966@ipfire.org> (raw)
In-Reply-To: <b1991dd5-b096-4fb1-8afc-8d3a11363b63@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

Hello Adolf,

> On 14 Feb 2022, at 13:48, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi all,
> 
> 
> I have noticed that iana-etc on IPFire was last updated in 2011.
> 
> It appears that iana no longer provided a versioned form of their data. However I have found a github location that has setup an automated versioning script to automatically create a versioned source file roughly every week.
> 
> This is https://github.com/Mic92/iana-etc and the source file has the /etc/services and /etc/protocols files ready available to copy to the installation locations.

Yes, it looks like this is the source for LFS as well:

  https://www.linuxfromscratch.org/lfs/view/development/chapter03/packages.html

> Another alternative is Arch Linux who run a process once a month to download the .xml files and then run some gawk scripts to strip all the stuff that is not required for a list of the services and protocols. Arch Linux stores both the text versions and the xml versions of the services and protocols in the OS.

Since the project you linked is releasing tarballs on a regular basis, I would just go with those.

> Looking at the two above options the one from Mic92 seems to be the easier options as that provides both the text and xml versions and so the LFS file would only need to copy the text versions to the correct location.

Agreed.

-Michael

> 
> 
> Feedback on the best approach to use for this?
> 
> 
> Regards,
> 
> Adolf.
> 
> 


      reply	other threads:[~2022-02-14 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 13:48 iana-etc Adolf Belka
2022-02-14 14:33 ` Michael Tremer [this message]

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=AB38B137-3F4C-49EA-B7F6-AF79FAE3E966@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox