Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754696Ab2H2XnA (ORCPT ); Wed, 29 Aug 2012 19:43:00 -0400 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:62709 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754663Ab2H2Xm6 (ORCPT ); Wed, 29 Aug 2012 19:42:58 -0400 MIME-Version: 1.0 In-Reply-To: <503E9FC5.1010707@teksavvy.com> References: <201208231814.21168.tweek@tweek.dk> <201208231951.28606.linux@rainbow-software.org> <1345812057.28613.20.camel@thorin> <1345823281.28613.34.camel@thorin> <20120824173626.0194625c@pyramind.ukuu.org.uk> <20120824174712.16c75f31@pyramind.ukuu.org.uk> <503A2B04.7080703@teksavvy.com> <503E9FC5.1010707@teksavvy.com> Date: Wed, 29 Aug 2012 19:42:56 -0400 X-Google-Sender-Auth: TysXWDrQnyo3ChqNLEvZfbMHYW0 Message-ID: Subject: Re: Drop support for x86-32 From: Jeff Garzik To: Mark Lord Cc: wbrana , linux-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1037 Lines: 24 On Wed, Aug 29, 2012 at 7:03 PM, Mark Lord wrote: > On 12-08-26 10:15 AM, wbrana wrote: >> On 8/26/12, Mark Lord wrote: >>> Here are a couple of real scenarios you don't seem to have thought about. >>> A 32-bit kernel on a legacy (or even new) system in 2017 will still need >>> regular kernel updates (not "long term" un0maintained kernels) >>> in order to work with new USB devices, new 4KB+ sector hard drives, >>> newer generations of SSDs, etc.. >> 12-years-old machine is trash. > > There you go making assumptions again. > Who said anything about a 12-year old machine? > > Much more likely is a 5-year old software installation > that gets moved to a new box. Or a brand new software installation into a 32-bit virtual machine. Jeff -- 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/