To: linux-kernel@vger.kernel.org
From: hpa@zytor.com (H. Peter Anvin)
Subject: Re: Squashfs without ./..
Date: Thu, 24 Mar 2005 19:59:49 +0000 (UTC)
Organization: Mostly alphabetical, except Q, which We do not fancy
Message-ID: <d1v67l$4dv$1@terminus.zytor.com>
References: <Pine.LNX.4.61.0503221645560.25571@yvahk01.tjqt.qr> <20050323174925.GA3272@zero> <Pine.LNX.4.62.0503241855350.18295@numbat.sonytel.be> <20050324133628.196a4c41.Tommy.Reynolds@MegaCoder.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
NNTP-Posting-Date: Thu, 24 Mar 2005 19:59:49 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1146
Lines: 29

Followup to:  <20050324133628.196a4c41.Tommy.Reynolds@MegaCoder.com>
By author:    Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
In newsgroup: linux.dev.kernel
> 
> Then it is broken in several ways.  
> 
> First, file systems are not required to implement ".." (only "." is
> magical, ".." is a courtesy).  
> 

Sez who?  Realistically, most programs that display a list of
filenames and has "up one level" as part of the list (not all of them
do it that way) probably expect to get ".." in there to display this.

> Second, skipping the first two entries carries an implied assumtion
> about the file name sorting order that is not portable in a
> non-US-ASCII world.

Doesn't have anything to do with sorting order or US-ASCII, it has to
do with readdir order.  If nothing else, it would be highly surprising
if "." and ".." weren't first; it's certainly a de facto standard, if
not de jure.

	-hpa
-
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/