From owner-freebsd-stable@freebsd.org Thu Jan 12 05:07:04 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D725CACEE0 for ; Thu, 12 Jan 2017 05:07:04 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wj0-x229.google.com (mail-wj0-x229.google.com [IPv6:2a00:1450:400c:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E40C91D96 for ; Thu, 12 Jan 2017 05:07:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wj0-x229.google.com with SMTP id i20so4547999wjn.2 for ; Wed, 11 Jan 2017 21:07:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mgdyuugAvjtic5G81MzcpavJeVxv7FblzJZzqGeXHCI=; b=Trm181Q00YSAGC0VV1jZks/4IDi1PlWahf5ei5pWMm+EHkw+3XGvGeA0da1hh+7neW An8vy1Oq7AKyz6F/0AyxVwFoOcwCE30r1HrZzfy+wpQoldf6NWGRqGE+9QbfLPC7jvOM aX0i0b/arhb6gVuzKrqfOeCzu2EXLhM6fR+e52a/zuPlhC5BRarzrH+CjtalVCZvqdIy pONQsMh+INl0icCCB137b1JOOC8yW+fVSrDtD6Day3uVPJ912q1zIw75Gj5fKpFnd6eg hY8RC4ZaOzZRscME6DCLltCRGBhnL1NxwuBDDLQ2HT/Mettd3fU37/VawOnkrjCAMOng r5DA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=mgdyuugAvjtic5G81MzcpavJeVxv7FblzJZzqGeXHCI=; b=hH5V9wR84udy9SYck8OeG2kgrCXGzNtSi1lX4ubCypxWvvQgYO/TGTv4NGuhd88q2O IvSJ76UPkqup/xRST4Usd5gSiDfJ73KUOC/H6ipZ+yIvzX5f4WBG6dxlVUZVn3eWFzUL k7wu/Ndqx9z6O8JNw4DwAuLdZ+kSPvqdDReciM/rkFBPuLWE+pwRRP4idpxJ89AfPzoH xT83TLQ3K2vLIIkGjwBZWUZSVBVQ+c/0xVHSQSm2rE/xEGfh40kY9a5BSbilIr+yB5qz c0yHii6Zlfg6JAtaeo7ngcpXEhhUA/zkpl/EX2Jz3cL7PvTjOPzK/JQCNyIleU3FYCBF GB5A== X-Gm-Message-State: AIkVDXKy9Z42bPhWrU2gWwZsJ2fYbW8LYefkiLBnXyqZQ+LQh9IX3KNP29RDuQ5tsjB2/E7PjQBHbb8qf3630g== X-Received: by 10.194.122.231 with SMTP id lv7mr3084419wjb.231.1484197621585; Wed, 11 Jan 2017 21:07:01 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.51.78 with HTTP; Wed, 11 Jan 2017 21:07:01 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Wed, 11 Jan 2017 21:07:01 -0800 X-Google-Sender-Auth: VT9szv4gbvpUf4Lhimlpc7XS9cg Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: George Mitchell Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 05:07:04 -0000 On Wed, Jan 11, 2017 at 8:24 PM, George Mitchell wrote: > On 01/11/17 17:46, George Mitchell wrote: > > On 01/11/17 17:20, Kevin Oberman wrote: > >> [...] > >> > >> While I have no suggestions about the error building libc, your > statement > >> that you can't use freebsd-update due to your use of a custom kernel i= s > >> incorrect. This is a common misconception and, in cases of very limite= d > >> disk space, may be true, it is rare. It is helped by the fact that the > man > >> page makes no mention of how to so this. (You do still need to build a > new > >> kernel if the update does, indeed, touch the kernel.) > >> > >> All you need is a GENERIC kernel in /boot/GENERIC. You can either buil= d > it > >> or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCu= stom > Kernels > >> with FreeBSD 9.X and Later=E2=80=9D > >> handbook/updating-upgrading-freebsdupdate.html#freebsd- > update-custom-kernel-9x> > >> for details on downloading a GENERIC kernel. Before any upgrade, major > or > >> minor, you might wat to re-reas that section. > >> > >> Once the GENERIC kernel is in /boot, you may use freebsd-update and, i= f > the > >> GENERIC kernel is not updated, you're good to go. If it is, you will > need > >> to build and install a new custom kernel and reboot. Since most securi= ty > >> patches don't touch the kernel, this is usually not needed. I believe > that > >> the 10.3 kernel was last touched in p11. > >> -- > >> Kevin Oberman, Part time kid herder and retired Network Engineer > >> E-mail: rkoberman@gmail.com > >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@ > freebsd.org" > >> > > Thanks, I'll try that the next time I have a chance. When I naively > > tried a straight "freebsd-update" a few months ago, of course it > > overwrote my SCHED_4BSD kernel with a SCHED_ULE one. -- George > > > Just to refresh my memory of what happened a few months ago, I tried > the following experiment. I copied my current modified kernel: > > rsync -av /boot/kernel/ /boot/my.kernel/ > > Then with my modified kernel still in place, I said: > > freebsd-update fetch > freebsd-update install > > With not a qualm in the world, freebsd-update installed a fresh > SCHED_ULE kernel in /boot. (Happily, it did save my current kernel > in /boot/kernel.old.) That's what happened last year, too. Why > didn't freebsd-update notice that I had a modified kernel and at > least notify me that something funky was going on? -- George I'm a bit surprised that there was no message about the kernel being non-GENERIC, but I've never tried. The key is the presence of /boot/GENERIC. If it is present, the kernel in /boot/kernel is left untouched and /boot/GENERIC is updated to the new version. If /boot/GENERIC does not exist, then the update is performed on /boot/kernel/kernel. (N.B. Kernel modules are always updated when or if needed!) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683