Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756486Ab1FWNOk (ORCPT ); Thu, 23 Jun 2011 09:14:40 -0400 Received: from mail-bw0-f46.google.com ([209.85.214.46]:58766 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754668Ab1FWNOj (ORCPT ); Thu, 23 Jun 2011 09:14:39 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=Jh+QeMJtVsYXRXugKWZ7QQtt0Ipd9YSaW1q2iNUhn/LQqNtrugOliTXbODyNf1a7ew P9kcGcnv5f5XWiFk34Hxkg/b5+N6wVsox3t+VAxqDW8RNSVNaDPdRETnIW9mTc7oCP3M xXPy16tr4DCL5oJIhRaOcqTVs5tXk2bpI3ZD8= MIME-Version: 1.0 From: yuyichao-mit Date: Thu, 23 Jun 2011 09:14:18 -0400 X-Google-Sender-Auth: skFeQ3fIyMxZFDVq1roF4fvj-14 Message-ID: Subject: extra slash in current path To: linux-kernel@vger.kernel.org, linux-c-programming@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 506 Lines: 26 The problem is like this: $ cd / $ pwd / $ cd / $ pwd // $ cd /// $ pwd / Why can there be a extra slash (and exactly one) in current path? Is this designed on purpose? This is not really a big deal but I think it can confuse some program. Thanks. Yichao -- 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/