Date: Mon, 26 Jan 2015 21:03:47 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Kurt Jaeger <lists@opsec.eu> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org>, "Dr. Peter Voigt" <pvoigt@uos.de> Subject: Re: www/squid does not shutdown via rc Message-ID: <CAN6yY1tbxP1gbuBHjPDXbpEv1U7cH0o50NTfNyjdEa4y61=5zw@mail.gmail.com> In-Reply-To: <20150127035200.GF44537@home.opsec.eu> References: <20150126152433.52f07277f377f9396b65c9a8@mimar.rs> <20150127.002919.335530336.yasu@utahime.org> <20150126163934.32f199d43d86a70b00dd7e4a@mimar.rs> <20150127.010539.230444205.yasu@utahime.org> <54C6695E.6010704@freebsd.org> <20150126212514.56c8f0866f1d63bb98089dd0@mimar.rs> <20150126235655.5d371915@kirk.drpetervoigt.private> <CAN6yY1uciVB-83=ECbrtdnNOFDs3VCX9UA97thK8mQ08aavHtw@mail.gmail.com> <20150127035200.GF44537@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 26, 2015 at 7:52 PM, Kurt Jaeger <lists@opsec.eu> wrote: > Hi! > > > As far as patching, it is really pretty easy and requires no special > skills > > or knowledge. > > > > 1. Download the two patches as ~/A.patch and ~/B.patch > [...] > > Doesn't installing a custom kernel break freebsd-update ? > > -- > pi@opsec.eu +49 171 3101372 5 years to > go ! > Michelle, 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. Kurt, 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@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tbxP1gbuBHjPDXbpEv1U7cH0o50NTfNyjdEa4y61=5zw>