From owner-freebsd-current@FreeBSD.ORG Fri Jul 9 21:15:13 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 8C56816A4CE; Fri, 9 Jul 2004 21:15:13 +0000 (GMT) Received: from mail.llorien.org (mail.llorien.org [212.88.225.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B5B43D41; Fri, 9 Jul 2004 21:15:13 +0000 (GMT) (envelope-from h@llorien.org) Received: from localhost ([127.0.0.1] helo=mail.llorien.org ident=mail) by mail.llorien.org with esmtp (TLS-1.0:RSA_ARCFOUR_SHA:16) (Exim 4.34) id 1Bj2i5-0003PW-6j; Fri, 09 Jul 2004 23:15:12 +0200 Received: from [213.118.64.6] (helo=d5764006.kabel.telenet.be) by mail.llorien.org with asmtp (SSL 3.0:RSA_ARCFOUR_MD5:16) (Exim 4.34) id 1Bj2i4-0003PT-UH; Fri, 09 Jul 2004 23:15:09 +0200 From: h To: freebsd-current@freebsd.org Date: Fri, 9 Jul 2004 23:16:20 +0200 User-Agent: KMail/1.6.2 References: <200407091513.48539.h@llorien.org> <40EEFBC5.9010605@fer.hr> <20040709202047.GA27694@Odin.AC.HMC.Edu> In-Reply-To: <20040709202047.GA27694@Odin.AC.HMC.Edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407092316.20087.h@llorien.org> X-Spam-Score: 2.6 cc: current@freebsd.org cc: Ivan Voras 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: Fri, 09 Jul 2004 21:15:13 -0000 HEY, you just hurt my blunt scripts' feelings. On Friday 09 July 2004 22:20, 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. > > --- Brooks