From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 21 08:11:00 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DE2716A4CE; Mon, 21 Jun 2004 08:11:00 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 72AAC43D2F; Mon, 21 Jun 2004 08:10:59 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Jun 2004 09:10:47 +0100 (BST) To: David Schultz In-reply-to: Your message of "Sun, 20 Jun 2004 22:44:06 PDT." <20040621054406.GA927@VARK.homeunix.com> X-Request-Do: Date: Mon, 21 Jun 2004 09:10:47 +0100 From: David Malone Message-ID: <200406210910.aa18808@salmon.maths.tcd.ie> cc: freebsd-hackers@FreeBSD.ORG cc: Dimitry Andric cc: Scott Mitchell Subject: Re: /bin/ls sorting bug? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 08:11:00 -0000 > Sorting on nanoseconds too is likely to be more confusing than > useful. Even if we use one of the precious few option letters ls > doesn't use already to add a nanosecond display, most people won't > know about it because they don't care about nanoseconds. They > might care when they notice---as you did---that the sort order > isn't what they expected. At the moment in FreeBSD the nanoseconds field is always zero, unless you twiddle vfs.timestamp_precision, so it would make no difference to joe user. For people that do set vfs.timestamp_precision, it would be nice if ls did the right thing (for example, test already compares the nanoseconds field, after someone submitted a PR because it didn't). > Is the point of sorting on nanoseconds to totally order the files > based on modification time? Depending on the clock resolution (which is partially determined by vfs.timestamp_precision and partially determined by the actual clock resolution), it may not be enough to totally order the files. David.