From owner-freebsd-questions Fri Jan 19 6:39:42 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 2393837B402 for ; Fri, 19 Jan 2001 06:39:25 -0800 (PST) Received: (qmail 49762 invoked by uid 100); 19 Jan 2001 14:39:14 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14952.20882.399235.381674@guru.mired.org> Date: Fri, 19 Jan 2001 08:39:14 -0600 (CST) To: "DINKEY,GENE (HP-Loveland,ex1)" Cc: questions@freebsd.org Subject: Kernel & Userland in sync (Was: too much confusion over kernel building) In-Reply-To: <24755071@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DINKEY,GENE (HP-Loveland,ex1) types: > Although I do remember a discussion I had earlier last year about keeping > userland and kernel source stuff in sync with the release. I think the gist > of what I got was that it may not be a good idea to update kernel sources > without updating userland sources as well. Since no one else confirmed this, I will. Yes, having userland and the kernel out of sync is doesn't always work, and hence not supported, a bad idea and something you shouldn't do.(*) Things in userland depend on things in the kernel, and if the two get out of sync, you can get problems. It doesn't even have to be userland source. I was getting screwy console behavior because the console device in the kernel was out of sync with the userland termcap entry for the console. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message