From: Vincent R. <fo...@sm...> - 2010-03-04 14:02:07
|
On Thu, 04 Mar 2010 08:00:00 -0500, Earnie <ea...@us...> wrote: > Vincent Richomme wrote: >> On Thu, 04 Mar 2010 11:59:51 +0100, Vincent Richomme >> <fo...@sm...> wrote: >> >>> Hi, >>> >>> I am trying to understand how mount points work and I need some help. >>> On some tutorial we can see that in fstab they recommend to add a mount >>> point >>> for mingw : >>> >>> c:/mingw /mingw >>> >>> but by default when I run mount command I get the following lines : >>> >>> $ mount >>> C:\DOCUME~1\Vincent\LOCALS~1\Temp on /tmp type user (binmode,noumount) >>> C:\Developer\EasyMingw-devel on / type user (binmode,noumount) >>> C:\Developer\EasyMingw-devel on /usr type user (binmode,noumount) >>> a: on /a type user (binmode,noumount) >>> c: on /c type user (binmode,noumount) >>> d: on /d type user (binmode,noumount) >>> e: on /e type user (binmode,noumount) >>> h: on /h type user (binmode,noumount) >>> >>> so install dir is mapped to / it means that if I enter something like >>> $>display_arg /mingw I get : C:/Developer/EasyMingw-devel/mingw >>> >>> So I would like to know why it would be necessary to add an entry in >>> fstab? >>> >>> > If you install MinGW under the MSYS root then there isn't one. But if > you do as you allude to above and install MinGW into c:\mingw and MSYS > into c:\msys then you need to tell MSYS where to look for /mingw by > mapping it in /etc/fstab. >>> Another question, when displaying mount points wouldn't be more logical >>> >> to >> >>> display them with / instead of \ since this is how they are really >>> >> mapped >> >>> ? >>> >> > That is a good point but probably historically came from Cygwin. One > could argue that displaying Windows paths should always show the \ > instead of / since that is what is native to Windows. >> >> Hey before I stop bothering you another remark about that, look at the >> following cases >> >> $ ./display_arg.exe /mingw32/include >> C:/Developer/EasyMingw-devel/mingw32/include >> >> $ ./display_arg.exe /mingw32/include:/mingw32/include >> C:\Developer\EasyMingw-devel\mingw32\include;C:\Developer\EasyMingw-devel\mingw32\include >> >> When I pass only one path(first example), result is mapped with / but if >> I >> pass more >> it's \ that is used. >> is there any good reason to do that ? >> > > I doubt that it was reasoned, more coincidence but check the source > code. I know you're asking about UX issues due to inconsistency of > text. If it is a really big deal, open an issue to be tracked. > Ok let's say you buy a car and half the seats are made with leather and the other ones are made in cheap plastic... Either you choose one convention or the other one but mixing both is stupid (I know this is always the same thing : historical reason but I dont' live in past) So finally I solved my issue with clang by creating a msyspath.exe that replace \ by / when called with a path. |