From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 00:30:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F57E16A4CE for ; Sat, 10 Jul 2004 00:30:55 +0000 (GMT) Received: from mx.sharanet.org (alfonso.cc.fer.hr [161.53.72.118]) by mx1.FreeBSD.org (Postfix) with SMTP id F161543D3F for ; Sat, 10 Jul 2004 00:30:53 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: (qmail 82149 invoked from network); 10 Jul 2004 02:30:52 +0200 Received: from unknown (HELO ?127.0.0.1?) (@127.0.0.1) by 0 with SMTP; 10 Jul 2004 02:30:52 +0200 Message-ID: <40EF38B6.7000307@fer.hr> Date: Sat, 10 Jul 2004 02:30:46 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis , current@freebsd.org References: <200407091513.48539.h@llorien.org> <20040709202047.GA27694@Odin.AC.HMC.Edu> In-Reply-To: <20040709202047.GA27694@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: i need my floppy disk drive. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 00:30:55 -0000 Brooks Davis wrote: > On Fri, Jul 09, 2004 at 10:10:45PM +0200, Ivan Voras wrote: > >>h wrote: >> >>>is it safe to upgrade to current when i'm used to -release ? >> >>I'd say *definetely NO!*. I made the similar mistake a week or so ago, >>and now the -current kernel mis-recognizes my root ATA drive (can't >>boot; I'm stuck in running 5.2-R kernel on a 5-current world; sigh). > > > This situation is caused by failure to follow the step by step > instructions in UPDATING. They very clearly state you should try your > new kernel before updating your world. If you do that, the risk should > be fairly minimal. I'm not complaining - it's on my home machine (I wouldn't even run -current on something important). I'm just puzzled because the error is weird (in short: disabling WITNESS causes my drive to be mis-recognized; I *can* run the same kernel with WITNESS enabled without problems, but I dont want to :) ), and there were no responses or similar errors reported from other people. Just my luck I guess :(