From owner-freebsd-ports@FreeBSD.ORG Wed Jan 28 14:59:02 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C905C9B for ; Wed, 28 Jan 2015 14:59:02 +0000 (UTC) Received: from mail-in-3.serv.Uni-Osnabrueck.DE (vm299.rz.uni-osnabrueck.de [131.173.16.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1758E2A for ; Wed, 28 Jan 2015 14:59:00 +0000 (UTC) Received: from smtp-auth.serv.Uni-Osnabrueck.DE (vm136.rz.uni-osnabrueck.de [131.173.16.11]) by mail-in-3.serv.Uni-Osnabrueck.DE (8.14.4/8.14.4) with ESMTP id t0SEwqwQ002060; Wed, 28 Jan 2015 15:58:52 +0100 Received: from spock.drpetervoigt.private (p549B5CDC.dip0.t-ipconnect.de [84.155.92.220]) (authenticated bits=0) by smtp-auth.serv.Uni-Osnabrueck.DE (8.13.8/8.13.8) with ESMTP id t0SEwoUm013393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Jan 2015 15:58:51 +0100 Received: from kirk.drpetervoigt.private (kirk.drpetervoigt.private [192.168.1.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pvoigt) by spock.drpetervoigt.private (Postfix) with ESMTPSA id 4DB991D15A8E; Wed, 28 Jan 2015 15:58:50 +0100 (CET) Date: Wed, 28 Jan 2015 15:58:46 +0100 From: "Dr. Peter Voigt" To: Marko =?UTF-8?B?Q3VwYcSH?= Subject: Re: www/squid does not shutdown via rc Message-ID: <20150128155846.76d77a18@kirk.drpetervoigt.private> In-Reply-To: <20150127115151.afeb1ee969a562e8f42e300c@mimar.rs> 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> <20150127115151.afeb1ee969a562e8f42e300c@mimar.rs> Organization: =?UTF-8?B?VW5pdmVyc2l0w6R0IE9zbmFicsO8Y2s=?= X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.23; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.1.28.145119 (Univ. Osnabrueck) X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report= HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_3000_3999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, CT_TEXT_PLAIN_UTF8_CAPS 0, FROM_NAME_PHRASE 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RDNS_POOLED_10 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0 X-PMX-Spam-Level: IIIIIIII Cc: freebsd-ports@freebsd.org 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: Wed, 28 Jan 2015 14:59:02 -0000 On Tue, 27 Jan 2015 11:51:51 +0100 Marko Cupa=C4=87 wrote: > On Tue, 27 Jan 2015 07:11:10 +0000 > Matthew Seaman wrote: >=20 > > 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 do by creating a modofoed kernel config file > > in /usr/src/sys/amd64/conf (or 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. >=20 > 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). >=20 > 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. >=20 > Does this sound reasonable? Any tips? >=20 > Thank you in advance, Thanks to all who contributed to this thread. @Kevin: Your outline of kernel patching procedure is helpful and corresponds in most aspects what I have thought so far. I aggree with you that patching, building and installing a custom kernel can be managed. And I am sure that I can do it. So getting a custom kernel installed is one thing but keeping your system in a manageable way is another. Kurt and Mattew pointed out that you want to keep freebsd-update working in a reliable way and this obviously needs some manual interaction. Information about it is not too easily gathered and answers given here still leave some question open to me. I have had a hard time with freebsd-update when upgrading 10.0-RELEASE -> 10.1-RELEASE: =20 https://forums.freebsd.org/threads/segmentation-fault-while-upgrading-from-= 10-0-release-to-10-1-release.48977/page-2#post-277094 and I do not want to get even more trouble letting freebsd-update confuse my system with a mixture of GENERIC and custom kernels ending in a situation where none of them is able to boot. I have learned that I can advice freebsd-update to not update my kernel but am still confused whether it is the version under /boot/GENERIC or the one under /boot/kernel. And I would like to know how to tell FreeBSD how to boot a certain kernel. All I know so far is that if a kernel fails to boot you have to boot into recovery and move kernel.old to kernel. Is there a boot menu available with the FreeBSD boot loader which would simplify life a lot? Furthermore, installing a custom kernel influcences a subsequent build world process in a way that I do not yet fully understand. If all above is clarified I could go the way of using a custom kernel. But to be honest: I would do it only, because I have just one FreeBSD server to mannage this way. The other FreeBSD based servers have FreeNAS and pfSense and are managed differently. But if I was an administrator with several FreeBSD servers, this would not be a way to go.=20 Regards, Peter