Date: Tue, 27 Jan 2015 07:11:10 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: www/squid does not shutdown via rc Message-ID: <54C73A0E.8050501@FreeBSD.org> 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 2015/01/27 03:52, Kurt Jaeger wrote: > Doesn't installing a custom kernel break freebsd-update ? No. freebsd-update has always supported using a custom kernel. It helps if you name your kernel something other than GENERIC, which you do by creating a modofoed kernel config file in /usr/src/sys/amd64/conf (or i386 if that's your architecture): eg. % cat FOO include GENERIC ident FOO and then add: KERNCONF= FOO to /etc/make.conf You should also edit /etc/freebsd-update.conf and change the 'Components' line to remove 'kernel' from the list. None of this is absolutely necessary, but it will help you avoid accidentally ending up with the generic kernel. In any case, what you will need to do is rebuild your kernel and reinstall it any time freebsd-update touches the kernel. You can use freebsd-update to maintain the kernel sources, which will pull in the needed updates to the kernel sources. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54C73A0E.8050501>