| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| 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 |
| From: | "Schwarz, Konrad" <konrad DOT schwarz AT siemens DOT com> |
| To: | "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com> |
| Date: | Fri, 29 Jul 2011 09:45:41 +0200 |
| Subject: | RE: Device names in /proc/mounts |
| Message-ID: | <9B10FEAACF062F48A095880A451FF05903819B318E@DEMCHP99E84MSX.ww902.siemens.net> |
| References: | <20110728112154 DOT GB16913 AT ednor DOT casa DOT cgf DOT cx> |
| In-Reply-To: | <20110728112154.GB16913@ednor.casa.cgf.cx> |
| MIME-Version: | 1.0 |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
| X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id p6T7k7Yk002972 |
> -----Original Message----- > From: Christopher Faylor > Subject: Re: Device names in /proc/mounts > The "drive letters" above could be anything that > Windows maps to a drive letter. A drive does not necessarily > 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. > /cygdrive is a user-settable value. So use whatever /cygdrive is actually set to. > Some users use other > 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 > 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 > going to introduce this level of recursive confusion to the > 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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |