Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Dec 2002 22:35:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Dec 2002 22:35:56 -0500 Received: from saturn.cs.uml.edu ([129.63.8.2]:49682 "EHLO saturn.cs.uml.edu") by vger.kernel.org with ESMTP id ; Wed, 11 Dec 2002 22:35:55 -0500 Date: Wed, 11 Dec 2002 22:43:38 -0500 (EST) Message-Id: <200212120343.gBC3hcO11146@saturn.cs.uml.edu> From: "Albert D. Cahalan" To: davej@codemonkey.org.uk Cc: linux-kernel@vger.kernel.org Subject: Re: 2.5 Changes doc update. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1073 Lines: 29 Dave Jones writes: > - Alternatively, the procps by Albert Cahalan now supports the > altered formats since v3.0.5, but lags behind the bleeding edge > version maintained by Rik and Robert. -- http://procps.sf.net/ Currently I'd say it's mostly the other way around. Differences between procps-2.1.11 and procps-3.1.2 that relate to Linux 2.5.xx support are: 1. Robert has /proc/*/wchan support (for WCHAN w/o System.map) 2. My vmstat has a fast O(1) algorithm for 2.5.xx kernels 3. My vmstat reports IO-wait time 4. My sysctl handles the 2.5.xx VLAN interfaces So that's 1-to-3 in my favor, based strictly on support of the 2.5.xx kernels. I find this odd actually, seeing as the procps-2 developers made #2 and #3 possible. The only time I fell behind was when Rik patched procps _before_ Linus accepted a change. - 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/