svn commit: r366186 - in head/usr.sbin: bsdconfig/share/media bsdinstall/scripts

[Niclas Zeising]

On 2020-09-27 03:38, Scott Long wrote:
> 
> 
>> On Sep 26, 2020, at 5:24 PM, Rodney W. Grimes <freebsd at gndrsh.dnsmgr.net> wrote:
>>
>> 
>>>
>>>
>>>>> On Sep 26, 2020, at 1:22 PM, Warner Losh <imp at bsdimp.com> wrote:
>>>>
>>>>
>>>>
>>>> I am the wrong person to answer that question.
>>>>
>>>> In this case, things have not become lame.  For instance, the names
>>>> ervers for se.freebsd.org work fine, but ftp3.se and ftp6.se records are
>>>> removed.  Same for ru.freebsd.org and ftp4.ru.
>>>> I'm merely pointing out that changing ftp.CC.freebsd.org usually
>>>> requires contacting the person(s) maintaining the CC.freebsd.org zone,
>>>> which is usually not the project.
>>>>
>>>> It's usually people associated with the project in some way, but who might not be as responsive as cluster admin. These domains have been delegated, so we have to get the delegated admin to make the changes, which can take a bit of time to chase down and doesn't lend itself to easy / automated coping with this situation.
>>>>
>>>
>>> Just a spitball idea here, but maybe we should consider not embedding these lists of mirror URLs into the binaries.  It seems pretty straight-forward that the list evolves over time, and that evolution is not tightly coupled with the updating of the binaries.  It sounds like the pkg and freebsd-update infrastructure use DNS TXT and/or SRV records to point to the metadata needed to construct a mirror URL list dynamically.  Maybe something similar can be done for bsdconfig?  If it?s not a crazy idea, is there anyone who would be interested in helping me write a proposal over at arch@?
>>
>> 100% behind that idea!  Especially since it seems the project has lost
>> (some) control over its DNS space, which IMHO, is still an issue, if
>> the people whom DNS zones have been deligated to are not responsive
>> that should also
> 
> Words of agreement don’t help at the moment, though i appreciate your enthusiasm.  Would you he able to help write a proposal for the arch@ mailing list?
> 

I think this is the wrong approach, and the better approach is to have 
the official installer use download.freebsd.org (which already is 
geo-located).  I also feel like this is probably something that core and 
possibly clusteradm should weigh in on, since it affects how we 
distribute FreeBSD.

My impression was that we were generally trying to move away from 
mirrors hosted by various people and organizations all over the world, 
where we have little control, to our own mirrors behind 
download.freebsd.org.  If this is the case, perhaps we should do so in 
the installer as well.

That said, I'm not opposed to the idea of using DNS SRV/TXT records to 
construct mirror lists, especially if we want to keep on using those 
mirrors.

Regards
-- 
Niclas Zeising