From owner-freebsd-ports@FreeBSD.ORG Tue Jan 27 07:11:34 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D992A100 for ; Tue, 27 Jan 2015 07:11:34 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "ca.infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C4A5AFC for ; Tue, 27 Jan 2015 07:11:34 +0000 (UTC) Received: from worm.infracaninophle.co.uk (worm.infracaninophle.co.uk [81.2.117.101] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.1/8.15.1) with ESMTPSA id t0R7B9g1058720 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 27 Jan 2015 07:11:13 GMT (envelope-from matthew@FreeBSD.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t0R7B9g1058720 Authentication-Results: smtp.infracaninophile.co.uk/t0R7B9g1058720; dkim=none reason="no signature"; dkim-adsp=none; dkim-atps=neutral Message-ID: <54C73A0E.8050501@FreeBSD.org> Date: Tue, 27 Jan 2015 07:11:10 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: www/squid does not shutdown via rc 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> <20150127035200.GF44537@home.opsec.eu> In-Reply-To: <20150127035200.GF44537@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2015 07:11:34 -0000 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