Re: freebsd-update: to a specific patch level - help please? [PATCH]
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 I've already benefited. Please submit this in a PR, and post the PR number here, I'll work to get this in the tree. PR is 226893 FYI - Just awaiting any kind of feedback on the PC. Won't be starting anything until then. Derek ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: freebsd-update: to a specific patch level - help please? [PATCH]
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 happy to flesh it out, and document it properly, but I'm very hesitant to spend the time doing it in detail and submitting a PR if I'm doing this in isolation, and nobody wants it. Please submit this in a PR, and post the PR number here, I'll work to get this in the tree. PR is 226893 Thanks! Derek ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: freebsd-update: to a specific patch level - help please? [PATCH]
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 document it properly, but I'm > very hesitant to spend the time doing it in detail and submitting > a PR if I'm doing this in isolation, and nobody wants it. Please submit this in a PR, and post the PR number here, I'll work to get this in the tree. -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: freebsd-update: to a specific patch level - help please? [PATCH]
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 freebsd-update server“. Mirroring one of the existing ones is AFAIK neither guaranteed to work nor desired by the current „administration“. Thanks for your thoughts. 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 document it properly, but I'm very hesitant to spend the time doing it in detail and submitting a PR if I'm doing this in isolation, and nobody wants it. Perhaps the silence on the thread is already a good indicator of the appetite, although I fear it's my ability to sell it or myself properly.) Structurally, "run your own freebsd-update server" is a wasteful solution for a single (or much larger set of) default install(s). It makes a lot of sense for custom installations. For what should be the default approach: repeatable - version controlled - installations with the support of the FreeBSD project, it would seem that having freebsd-update support patch levels would be a far more efficient net use of people's time than the alternatives. (I was debating both running an update server, or running "behind" a hacked up mirror as well, and in fact, I feel patching freebsd-update was a great investment, for n=1.) It’s also a somewhat transient problem now because - AFAIK - FreeBSD will see packaged base and you can probably mirror those packages and snapshot the directory at any point in time. And/Or it’s just easier to create these base-packages yourselves vs. running your own freebsd-update server. This is a good point, and perhaps why it's not worth putting more time into this. I appreciate your feedback. Thanks! Derek ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: freebsd-update: to a specific patch level - help please?
> 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“. Mirroring one of the existing ones is AFAIK neither guaranteed to work nor desired by the current „administration“. I’ve contemplated doing both, but never had enough heart-ache to do it and never thought the pay-off would be greater than the potential problems. It’s also a somewhat transient problem now because - AFAIK - FreeBSD will see packaged base and you can probably mirror those packages and snapshot the directory at any point in time. And/Or it’s just easier to create these base-packages yourselves vs. running your own freebsd-update server. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
freebsd-update: to a specific patch level - help please?
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. Here's a story for context, please feel free to skip: We are planning to cut our 10.3-RELEASE infrastructure over to 11.1-RELEASE before the end of the month, because it's EoL in April. We updated and cut over our production load balancer March 6th (and patted ourselves on the back for being ahead of schedule), and within less than 12 hours, updated our backup load balancers. Unfortunately, we're now on ever so slightly different versions (-p6/-p7), and we're not affected by the -p7 problems. This makes my eye twitch slightly, especially when -p7 was the first patch of 2018. Now we need to upgrade our application servers, that are running our trusted code, and -p8 comes out. I'm nervous about just applying -p8, but I definitely want to upgrade to 11.1-RELEASE asap. After assessing the impact of -p8 on our infrastructure, I feel the security risk is relatively low in the short term (and we've waited this long anyway), but I feel the probability of introducing unintended side-effects is high, and want some time to test and asses. /story It would seem to me, for repeatable environments, that binary updates from FreeBSD that can be pinned to specific version are highly desireable. I've gone ahead and created a patch for my use here: https://github.com/derekmarcotte/freebsd/commit/009015a7dda5d1f1c46f4706c222614f17fb535c (there's a 10.3-specific one here: https://github.com/derekmarcotte/freebsd/commit/458879f36ae984add0ff525fb6c2765fcf1fba67 ) I'd be happy to open a PR, and to iterate and improve on this PoC, but if there's no support from the project, I'll keep it to myself. I guess what I'm asking is, for these reasons, is anyone willing to work with me (in mentorship+commit bits) to add this feature (maybe not this particular implementation) to freebsd-update? Thanks! Derek ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
