> On Oct 19, 2023, at 16:16, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 19/10/2023 21:26, Tomoaki AOKI wrote:
>> On Thu, 19 Oct 2023 19:53:08 +
>> Miroslav Lachman <000.f...@quip.cz> wrote:
>
> [..]
>
>>> It is hackery workaround. freebsd-update must not overwrite user
>>> modified fi
On 19/10/2023 21:26, Tomoaki AOKI wrote:
On Thu, 19 Oct 2023 19:53:08 +
Miroslav Lachman <000.f...@quip.cz> wrote:
[..]
It is hackery workaround. freebsd-update must not overwrite user
modified files without safe merge of conflicts. yet it did it in the
past, for example pf.conf and some
On Thu, 19 Oct 2023 19:53:08 +
Miroslav Lachman <000.f...@quip.cz> wrote:
> On 19/10/2023 16:19, Robert Blayzor wrote:
> > On 10/4/23 00:45, Peter Libassi wrote:
> >> Me too! My sshd_config is also customized and everytime there is a new
> >> patch I need to run freebsd-update manually and ge
On 19/10/2023 16:19, Robert Blayzor wrote:
On 10/4/23 00:45, Peter Libassi wrote:
Me too! My sshd_config is also customized and everytime there is a new
patch I need to run freebsd-update manually and get rid of the attempt
to trash the sshd config that could make my server unreachable over
th
On 10/4/23 00:45, Peter Libassi wrote:
Me too! My sshd_config is also customized and everytime there is a new
patch I need to run freebsd-update manually and get rid of the attempt
to trash the sshd config that could make my server unreachable over the
network.
Why does the freebsd-update nee
