Re: Upgrade: Unbound constraint let fw_update always fail

Thanks Steve,

Jul 25, 2023 14:41:53 Steve Litt <slitt@troubleshooters.com>:

> chattr -i resolv.conf && echo nameserver 8.8.8.8 >> resolv.conf && chattr +i resolv.conf
>
> I also don't understand why you start unbound manually instead of from
> computer initialization. It sounds like if unbound started before
> fw_update, there would be no problem

I also would like the possibility to rewind my mindset to two years ago to have the proper
technical answer when I need it.. However I try to answer you..

Basically I think while experimenting I found interesting the possibility to have full
control over my dev environment and decide when to take up/down all my needs, including the network..
Indeed I was so happy about my findings that I decided to give to it also a graphical interface
to make it more amousing. :D

If you want to help, in my script to switch the dev environment down I miss the possibility to take down Unbound
that one time launched is very hard to switch off, still my script doesn't do that..

I think the suggestion to implement an ad-hoc network settings for the unattended installation could
be interesting also to cover that few cases of disparate accesses to Internet, indeed. But here you should
have a some more case studies than me.

-- Daniele Bonini

Jul 25, 2023 14:41:53 Steve Litt <slitt@troubleshooters.com>:

> chattr -i resolv.conf && echo nameserver 8.8.8.8 >> resolv.conf && chattr +i resolv.conf
>
> I also don't understand why you start unbound manually instead of from
> computer initialization. It sounds like if unbound started before
> fw_update, there would be no problem.