From owner-freebsd-arch Sat Dec 22 18: 7:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 2C0A737B405; Sat, 22 Dec 2001 18:07:18 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBN270G33803; Sat, 22 Dec 2001 18:07:00 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: The Anarcat Cc: arch@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: sysctl kern.disks shouldn't have to sort its output In-Reply-To: Message from The Anarcat of "Sat, 22 Dec 2001 19:54:50 EST." <20011223005449.GE530@shall.anarcat.dyndns.org> Date: Sat, 22 Dec 2001 18:07:00 -0800 Message-ID: <33799.1009073220@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Yes, of course. But I wonder how best it would be implemented... By > controlling how entries are added to the list, or by controlling how he > prints those entries? It's only useful if you control how the entries are added to the Disks ** structure. > Because it is a list, sorting it is not very efficient. At the output It's small. You can bubble sort it for all we care. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message