Date: Wed, 28 Jan 2015 15:58:46 +0100 From: "Dr. Peter Voigt" <pvoigt@uos.de> To: Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs> Cc: freebsd-ports@freebsd.org 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> <CAN6yY1uciVB-83=ECbrtdnNOFDs3VCX9UA97thK8mQ08aavHtw@mail.gmail.com> <20150127035200.GF44537@home.opsec.eu> <54C73A0E.8050501@FreeBSD.org> <20150127115151.afeb1ee969a562e8f42e300c@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Jan 2015 11:51:51 +0100 Marko Cupa=C4=87 <marko.cupac@mimar.rs> wrote: > On Tue, 27 Jan 2015 07:11:10 +0000 > Matthew Seaman <matthew@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150128155846.76d77a18>