From owner-freebsd-ports@FreeBSD.ORG Tue Jan 27 10:51:59 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 00C5F154 for ; Tue, 27 Jan 2015 10:51:58 +0000 (UTC) Received: from mail.mimar.rs (mail.mimar.rs [193.53.106.129]) by mx1.freebsd.org (Postfix) with ESMTP id 9C0B5323 for ; Tue, 27 Jan 2015 10:51:57 +0000 (UTC) Received: from mail.mimar.rs (localhost [127.0.0.1]) by mail.mimar.rs (Postfix) with ESMTP id 099601AF503 for ; Tue, 27 Jan 2015 11:51:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:references:in-reply-to:message-id:subject:subject:from :from:date:date:received:received; s=mimar-0901; t=1422355912; x=1424170313; bh=QNBSNT4YpmpeqQ+o526yPFgy31ya3u65B/hT3f4Y5Hc=; b= JwcZP0NeD6Ez82amTvSDgoXTvJsz/r9Ik//8P08k2SVoM8cVpUcITV6dTzNOFzON dGBlT7tJIVdNpe/J3pLpaim/PMMN3C+voZHbA3/cC1zRqnAaVfb300olQ1RXKQqx AcswWGovxPlm1QWh1799ZvWqdpsUSYKfOB5c/iSnP14= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.0.1]) by mail.mimar.rs (mail.mimar.rs [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zf3nsPlRIWq1 for ; Tue, 27 Jan 2015 11:51:52 +0100 (CET) Received: from efreet (nat.kappastar.com [193.53.106.34]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id 400301AF32C for ; Tue, 27 Jan 2015 11:51:52 +0100 (CET) Date: Tue, 27 Jan 2015 11:51:51 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-ports@freebsd.org Subject: Re: www/squid does not shutdown via rc Message-Id: <20150127115151.afeb1ee969a562e8f42e300c@mimar.rs> In-Reply-To: <54C73A0E.8050501@FreeBSD.org> 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> <54C73A0E.8050501@FreeBSD.org> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 10:51:59 -0000 On Tue, 27 Jan 2015 07:11:10 +0000 Matthew Seaman wrote: > On 2015/01/27 03:52, Kurt Jaeger wrote: > > Doesn't installing a custom kernel break freebsd-update ? >=20 > No. freebsd-update has always supported using a custom kernel. It > helps if you name your kernel something other than GENERIC, which you d= o > by creating a modofoed kernel config file in /usr/src/sys/amd64/conf (o= r > i386 if that's your architecture): eg. >=20 > % cat FOO > include GENERIC >=20 > ident FOO >=20 > and then add: >=20 > KERNCONF=3D FOO >=20 > to /etc/make.conf >=20 > You should also edit /etc/freebsd-update.conf and change the > 'Components' line to remove 'kernel' from the list. >=20 > None of this is absolutely necessary, but it will help you avoid > accidentally ending up with the generic kernel. >=20 > 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. The timing for this is really unfortunate for me, because I have just re-installed my FreeBSD fleet of some 20 virtual servers without sources included, and I just introduced "binary only" policy (ok I do build my own ports on one server in poudriere, but all other servers use packages)= . I guess theoretically it is possible to make "kernel build server" which will build custom kernel for distribution to other servers. I am just not sure how will RELEASE userland tolerate STABLE kernel. Does this sound reasonable? Any tips? Thank you in advance, --=20 Marko Cupa=C4=87 https://www.mimar.rs