From owner-freebsd-current Wed Jan 5 10:18:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id C7C7015492 for ; Wed, 5 Jan 2000 10:18:29 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DCF741CA0; Tue, 5 Jan 1999 15:22:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: David Scheidt Cc: Michael Lucas , Dmitry Valdov , current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: Message from David Scheidt of "Wed, 05 Jan 2000 09:52:43 CST." Date: Tue, 05 Jan 1999 15:22:10 +0800 From: Peter Wemm Message-Id: <19990105072210.DCF741CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > On Wed, 5 Jan 2000, Michael Lucas wrote: > > > Hello, > > > > Not that this is an actual fix to the problem, but: > > > > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > > least, when I wrote an article on this, it wasn't.) You can probably > > remove COMPAT_LINUX entirely. > > I use COMPAT_LINUX because I make kernels more frequently then I make world > or modules. I get fewer panics that way. > > David Scheidt You should definately use a static kernel without modules if you are tracking -current and rebuilding regularly. It is too easy to shoot yourself in the foot by getting /modules and the kernel out of sync while the internal interfaces are still changing. Using kld's to develop drivers is different. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message