On 18-03-24 10:26 AM, Derek wrote:
On 18-03-23 06:44 AM, Kurt Jaeger wrote:
To be clear, *I've included a link to a patch to freebsd-update
in my initial post, and the help I'm looking for: is to get this
functionality added as a feature so others can benefit.* It
works for me already, and
On 18-03-23 06:44 AM, Kurt Jaeger wrote:
Hi!
To be clear, *I've included a link to a patch to freebsd-update
in my initial post, and the help I'm looking for: is to get this
functionality added as a feature so others can benefit.* It
works for me already, and I've already benefited.
(I'm
Hi!
> To be clear, *I've included a link to a patch to freebsd-update
> in my initial post, and the help I'm looking for: is to get this
> functionality added as a feature so others can benefit.* It
> works for me already, and I've already benefited.
>
> (I'm happy to flesh it out, and
On 18-03-21 05:24 PM, Rainer Duffner wrote:
Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists) <48225...@razorfever.net>:
Hi!
I was surprised when using freebsd-update, that there was no way to specify a
patch level.
AFAIK, the usual answer to these kinds of requests is: „Run your own
> Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists)
> <48225...@razorfever.net>:
>
> Hi!
>
> I was surprised when using freebsd-update, that there was no way to specify a
> patch level.
AFAIK, the usual answer to these kinds of requests is: „Run your own
freebsd-update server“.
Hi!
I was surprised when using freebsd-update, that there was no way
to specify a patch level.
In my day to day, I need to ensure security patches are applied.
I also need to assess the impact of patches, and ensure
consistency (ie. versions) in my environments. This can take time.
