www/squid does not shutdown via rc
rkoberman at gmail.com
Tue Jan 27 05:03:50 UTC 2015
On Mon, Jan 26, 2015 at 7:52 PM, Kurt Jaeger <lists at opsec.eu> wrote:
> > As far as patching, it is really pretty easy and requires no special
> > or knowledge.
> > 1. Download the two patches as ~/A.patch and ~/B.patch
> Doesn't installing a custom kernel break freebsd-update ?
> pi at opsec.eu +49 171 3101372 5 years to
> go !
Seriously? Yes. That is why I offered exact commands to enter. And I am not
a developer. My C skills are poor and I last wrote kernel code for VMS. I
am a system admin, either full or part time for at least 35 years, though,
so I am more comfortable than the average user. But the average user is not
installing and configuring squid, either.
It's a simple process and, as always when a new kernel is installed, the
old one is saved, so recovery is pretty easy. If someone looks at those
step and feels they are beyond, they won't so them, but right now they are
stuck. I have no influence with those who can decide when an update should
be made but I've been around FreeBSD long enough to know how unlikely it is
that an update to fix this is, so I am offering another option.
No. That is the purpose of copying the standard kernel to /boot/GENERIC is
for that purpose. It's not in the man pages but is in the Handbook. If you
have /boot/GENERIC, freebsd-update will use that kernel instead of
/boot/kernel/kernel. If you are making changes to the kernel of a release,
just be sure that you have copied the running kernel to /boot/GENERIC and
you are safe. (Of course, any changes to the kernel will be lost when
freebsd-update is run in the future, but in this case STABLE already has
the patches, so they (or something similar) will be in 10.2.
The only problem is a security patch that updates the kernel. After that,
the patches would have to be re-applied, the new kernel copied to
/boot/GENERIC and so on.
Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com
More information about the freebsd-ports