[lfs-dev] Concerning iana-etc

DJ Lucas blfs-dev at lucasit.com
Fri Jul 19 16:30:17 PDT 2019

On 7/18/2019 10:12 PM, Bruce Dubbs via lfs-dev wrote:
> On 7/18/19 9:36 PM, DJ Lucas via lfs-dev wrote:
>> On 7/7/2019 5:28 PM, Bruce Dubbs via lfs-dev wrote:
>>> On 7/7/19 5:23 PM, DJ Lucas via lfs-dev wrote:
>>>> On 7/3/2019 10:06 AM, Bruce Dubbs via lfs-dev wrote:
>>>>> On 7/3/19 1:17 AM, DJ Lucas via lfs-dev wrote:
>>> [snip]
>>>>>> Just a quick (but functional) mock-up using 
>>>>>> update-ca-certificates as an example. Can clean it up if this 
>>>>>> would be good for the book. Would need to move to chapter 7, 
>>>>>> after networking configuration (won't work without 
>>>>>> /etc/resolv.conf).
>>>>> This is an interesting idea, but I think for LFS it would be 
>>>>> better to host the files on anduin for download.  The update is 
>>>>> really not very critical.  After all we have been working with the 
>>>>> current version since 2008 without issue.
>>>>> (Looking at the current XML files, protocols was last updated 
>>>>> 2017-10-13 but services was updated 2019-07-02 (yesterday). )
>>>>> Right now we create a tarball with all packages that is available 
>>>>> for download.  After that, for LFS, an internet connection is not 
>>>>> needed. I'd like to keep it that way.
>>>>> We could but the script on anduin to keep the files updated like 
>>>>> we do with firmware.  We could also put the update script into 
>>>>> BLFS similar to make-ca.
>>>>> Another thought for BLFS is to just download the xml files with 
>>>>> wget and use xsltproc and a custom .xsl file to parse the xml.
>>>> https://github.com/djlucas/iana-etc <-- In the interim. I emailed 
>>>> Seth, haven't heard from him in several years.
>>> Are you going to update the book?
>> Okay, I've heard back from Seth, and he is cool with me taking over 
>> maintenance (he hasn't used it in some time) if we'd even like to 
>> keep it in the book. I've created a 4.0 release (per his suggestion, 
>> since somebody else has long ago done an unrelated 3.0 release and 
>> forgotten it). Whether we continue to use it is up to y'all. I'm fine 
>> with just downloading a static copy for LFS and making mention of the 
>> two awk scripts at some point as well, or putting a script in BLFS to 
>> update them occasionally.
> My preference would be for the last suggestion.
End of Glibc?


More information about the lfs-dev mailing list