From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3465 invoked by alias); 29 Jul 2011 07:46:01 -0000 Received: (qmail 3452 invoked by uid 22791); 29 Jul 2011 07:46:00 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: sourceware.org Received: from thoth.sbs.de (HELO thoth.sbs.de) (192.35.17.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 Jul 2011 07:45:45 +0000 Received: from mail2.siemens.de (localhost [127.0.0.1]) by thoth.sbs.de (8.13.6/8.13.6) with ESMTP id p6T7jhxW030654 for ; Fri, 29 Jul 2011 09:45:43 +0200 Received: from DEMCHP99ET2MSX.ww902.siemens.net (demchp99et2msx.ww902.siemens.net [139.25.131.241]) by mail2.siemens.de (8.13.6/8.13.6) with ESMTP id p6T7jhHD008248 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 29 Jul 2011 09:45:43 +0200 Received: from DEMCHP99E84MSX.ww902.siemens.net ([169.254.1.172]) by DEMCHP99ET2MSX.ww902.siemens.net ([139.25.131.241]) with mapi; Fri, 29 Jul 2011 09:46:09 +0200 From: "Schwarz, Konrad" To: "cygwin@cygwin.com" Date: Fri, 29 Jul 2011 07:46:00 -0000 Subject: RE: Device names in /proc/mounts Message-ID: <9B10FEAACF062F48A095880A451FF05903819B318E@DEMCHP99E84MSX.ww902.siemens.net> References: <20110728112154.GB16913@ednor.casa.cgf.cx> In-Reply-To: <20110728112154.GB16913@ednor.casa.cgf.cx> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-07/txt/msg00365.txt.bz2 > -----Original Message----- > From: Christopher Faylor=20 > Subject: Re: Device names in /proc/mounts > The "drive letters" above could be anything that=20 > Windows maps to a drive letter. A drive does not necessarily=20 > directly map to a physical device. That's why the proposal suggests using /dev/sdXY names only when a driver letter does indeed map to a hard disk. =20 > /cygdrive is a user-settable value. So use whatever /cygdrive is actually set to. > Some users use other=20 > values like "/dev" instead of /cygdrive. How does /dev/ttyS0 resolve in this case? Those users have already shot themselves in the foot. > Some people get rid=20 > of the /cygdrive entirely and just map to /a. Which would be a rebind. /cygdrive (or the user's selected replacement) still exists, right? > We're not=20 > going to introduce this level of recursive confusion to the=20 > mount table handling. The proposal is sound. It works on Linux, after all. > Please give it a rest. We're not changing the mount table for you. Ok. Can you answer the following question: Given a volume label, how does one figure out where the corresponding volume has been mounted into the Cygwin namespace? Thanks, Konrad Schwarz -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple