From owner-freebsd-ports@FreeBSD.ORG Tue Jan 27 05:03:50 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 303143EC for ; Tue, 27 Jan 2015 05:03:50 +0000 (UTC) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB92EC52 for ; Tue, 27 Jan 2015 05:03:49 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id w62so12764053wes.7 for ; Mon, 26 Jan 2015 21:03:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zEl6jF7VBSJfxBsPHBcvQJATT8noLJ8Pug/iXeF0+XY=; b=Nwop5ETLBcKTE+uXYMGxGfSTC7fLIxop2UXDVGJooUcJ1EkXSKkFLalhJLt/C4eyPE /RSXMUAbD4PmkaYT1g6n6/8e+A+7OAZImC7PJkOPJdrpMu2GGprlyHMT/FGjLWa0RiJI fVpYP4FnxbHAQAEZnra2N+8Y6sQjmpD0EzsMRpffHXLyrfizdph5BlKSjLsTf+Vw3XMt sYPs5f92DSxvRZozrPlPC5vgOj7vzyulxpxw7vcb0gHxQkztuzJVTXtWEpLw4FVV7YWQ isX09LM+6eC3DeZcALuARncqqoR4fvRuzIqXrrJAiOUXUORu9Dky0JUMsf7VU2dsPrT6 osaQ== MIME-Version: 1.0 X-Received: by 10.180.73.4 with SMTP id h4mr29805696wiv.72.1422335028003; Mon, 26 Jan 2015 21:03:48 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.27.62.20 with HTTP; Mon, 26 Jan 2015 21:03:47 -0800 (PST) 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> <20150127035200.GF44537@home.opsec.eu> Date: Mon, 26 Jan 2015 21:03:47 -0800 X-Google-Sender-Auth: ypZnyVtXHunfh_Xjnvxbfn2shGw Message-ID: Subject: Re: www/squid does not shutdown via rc From: Kevin Oberman To: Kurt Jaeger Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Ports ML , "Dr. Peter Voigt" 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 05:03:50 -0000 On Mon, Jan 26, 2015 at 7:52 PM, Kurt Jaeger wrote: > Hi! > > > As far as patching, it is really pretty easy and requires no special > skills > > or knowledge. > > > > 1. Download the two patches as ~/A.patch and ~/B.patch > [...] > > Doesn't installing a custom kernel break freebsd-update ? > > -- > pi@opsec.eu +49 171 3101372 5 years to > go ! > Michelle, Seriously? Yes. That is why I offered exact commands to enter. And I am not a developer. My C skills are poor and I last wrote kernel code for VMS. I am a system admin, either full or part time for at least 35 years, though, so I am more comfortable than the average user. But the average user is not installing and configuring squid, either. It's a simple process and, as always when a new kernel is installed, the old one is saved, so recovery is pretty easy. If someone looks at those step and feels they are beyond, they won't so them, but right now they are stuck. I have no influence with those who can decide when an update should be made but I've been around FreeBSD long enough to know how unlikely it is that an update to fix this is, so I am offering another option. Kurt, No. That is the purpose of copying the standard kernel to /boot/GENERIC is for that purpose. It's not in the man pages but is in the Handbook. If you have /boot/GENERIC, freebsd-update will use that kernel instead of /boot/kernel/kernel. If you are making changes to the kernel of a release, just be sure that you have copied the running kernel to /boot/GENERIC and you are safe. (Of course, any changes to the kernel will be lost when freebsd-update is run in the future, but in this case STABLE already has the patches, so they (or something similar) will be in 10.2. The only problem is a security patch that updates the kernel. After that, the patches would have to be re-applied, the new kernel copied to /boot/GENERIC and so on. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com