From owner-freebsd-current Sun Dec 21 01:22:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19325 for current-outgoing; Sun, 21 Dec 1997 01:22:28 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19316 for ; Sun, 21 Dec 1997 01:22:23 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id EAA00967; Sun, 21 Dec 1997 04:22:17 -0500 (EST) (envelope-from toor) Message-Id: <199712210922.EAA00967@dyson.iquest.net> Subject: Re: Strange behaviour with -current kernel... In-Reply-To: from The Hermit Hacker at "Dec 21, 97 00:58:51 am" To: scrappy@thelab.hub.org (The Hermit Hacker) Date: Sun, 21 Dec 1997 04:22:17 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The Hermit Hacker said: > > I've just upgraded to the most current kernel, and am having some very, > very strange problems with my system. I use pine for email, and each time > I restart pine, it tells me that its a new version (haven't upgraded pine > in months) and regenerates my .pinerc. Looking at the .pinerc itself > seems to show some "weird" stuff: > Probably my fault. Try setting either (depending what is in -current): sysctl -w debug.ioopt=0 or sysctl -w vfs.ioopt=0 If this fixes it, I'll disable the code by default. Sorry... :-(. John -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.