Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 22 Mar 2003 03:14:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 22 Mar 2003 03:14:20 -0500 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:1796 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id ; Sat, 22 Mar 2003 03:14:19 -0500 From: John Bradford Message-Id: <200303220827.h2M8R4YW000282@81-2-122-30.bradfords.org.uk> Subject: Re: Release of 2.4.21 To: degger@fhm.edu (Daniel Egger) Date: Sat, 22 Mar 2003 08:27:04 +0000 (GMT) Cc: linux-kernel@vger.kernel.org In-Reply-To: <1048283620.15199.22.camel@sonja> from "Daniel Egger" at Mar 21, 2003 10:53:40 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1071 Lines: 26 > > Unless the system has to run 24/7, which a desktop machine usually > > doesn't have to, I don't see why testing 2.5 on it isn't a > > possibility. > > Because desktop systems usually don't feature the notion of a testbed, > read an environment in which dangerous changes can be tested without > severe loss of important data. So why did you trim the part of my quote that said that production systems should always be backed up anyway? > I would never ever boot a 2.5.x kernel on my notebook or on any other=20 > machines without preparing a different harddrive for instance, YMMV > though. It's not exactly much work to put a different disk in a machine. With a notebook, it might be 30-45 minutes work dismantling it, but on a typical desktop, about 2 minutes, and on a rackmount server, probably 60 seconds. John. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/