X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: From: "Lee Maschmeyer" To: References: <7A40667E3D2C4AE49FC1811BB6945D13 AT cit DOT wayne DOT edu> <20080714203707 DOT GF24644 AT calimero DOT vinschen DOT de> <7CD0FF29D986456EBD660879815BAF24 AT cit DOT wayne DOT edu> <20080715163141 DOT GK24644 AT calimero DOT vinschen DOT de> Subject: Re: A path that's invalid on 1.7 but presumably valid on 1.5 Date: Tue, 15 Jul 2008 14:00:19 -0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00A7_01C8E683.1D9B2430" X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-Junkmail-Status: score=10/50, host=mirapointmr4.wayne.edu X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0206.487CE5B4.005A,ss=1,fgs=0, ip=141.217.4.199, so=2007-10-30 19:00:17, dmn=5.4.3/2008-02-01 X-Junkmail-IWF: false X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com ------=_NextPart_000_00A7_01C8E683.1D9B2430 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit >You could try to remove the /e mount point for testing. It's possible >that the problem I patched yesterday is the cause of the problem. No, that didn't help. I didn't reboot but I did restart Cygwin which I think is enough. For completeness I'm attaching my fstab. Would it help if I change "some_fs" to ntfs? -- Lee Maschmeyer Computing Center Services Computing and Information Technology Wayne State University Detroit, Michigan, USA ------=_NextPart_000_00A7_01C8E683.1D9B2430 Content-Type: application/octet-stream; name="fstab" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="fstab" # The file fstab contains descriptive information about the various file # systems. fstab is only read by programs, and not written; it is the # duty of the system administrator to properly create and maintain this # file. Each filesystem is described on a separate line; fields on each # line are separated by tabs or spaces. Lines starting with '#' are com- # ments. # # The first field, (fs_spec), describes the block special device or # remote filesystem to be mounted. On Cygwin, this is the native Windows # path which the mount point links in. As path separator you MUST use a # slash. Usage of a backslash might lead to unexpected results. UNC # paths (using slashes, not backslashes) are allowed. If the path # contains spaces these can be escaped as '\040'. # # The second field, (fs_file), describes the mount point for the filesys- # tem. If the name of the mount point contains spaces these can be # escaped as '\040'. # # The third field, (fs_vfstype), describes the type of the filesystem. # Cygwin supports any string here, since the file system type is usually # not evaluated. The noticable exception is the file system type # cygdrive. This type is used to set the cygdrive prefix. See the # user's guide for more information about the cygdrive prefix. # # The fourth field, (fs_mntops), describes the mount options associated # with the filesystem. It is formatted as a comma separated list of # options. It contains at least the type of mount (binary or text) plus # any additional options appropriate to the filesystem type. Recognized # options are binary, text, nouser, user, exec, notexec, cygexec, nosuid, # managed. For a description of the options see the user's guide. Note # that nouser mount points are not overridable by a later call to # mount(2). This is only possible for user mount points. Mount points # are by default nouser mount points, unless you specify the option user. # # The fifth (fs_freq) and sixth (fs_passno) field are ignored. They are # so far only specified to keep a Linux-like fstab file layout. # # Note that you don't have to specify an fstab entry for the root dir, # unless you want to have the root dir pointing to somewhere entirely # different (hopefully you know what you're doing), or if you want to # mount the root dir with special options (for instance, as text mount). # # Example entries: # # Just a normal mount point: # # c:/foo /bar fat32 binary 0 0 # # A mount point for a managed, textmode mount: # # C:/foo /bar/baz ntfs text,managed 0 0 # # A mount point for a Windows directory with spaces in it: # # C:/Documents\040and\040Settings /docs ext3 binary 0 0 # # A mount point for a remote directory: # # //server/share/subdir /srv/subdir smbfs binary 0 0 # # This is just a comment: # # # This is just a comment # # Set the cygdrive prefix to /mnt: # # none /mnt cygdrive binary 0 0 # e:/cygwin / some_fs binary 0 0 # a: /a some_fs binary,cygexec 0 0 c: /c some_fs binary,cygexec 0 0 d: /d some_fs binary,cygexec 0 0 e:/braille\040books /data/Braille\040Books some_fs binary,cygexec 0 0 e:/classic\040literature /data/Classic\040Literature some_fs binary,cygexec= 0 0 e:/Jiffy-Braille /data/Jiffy-Braille some_fs binary,cygexec 0 0 e:/New\040Literature /data/New\040Literature some_fs binary,cygexec 0 0 # e: /e some_fs binary,cygexec 0 0 h: /h some_fs binary,cygexec 0 0 j: /j some_fs binary,cygexec 0 0 e:/cygwin/bin /usr/bin some_fs binary 0 0 e:/cygwin/lib /usr/lib some_fs binary 0 0 e:/cygwin/usr/X11R6/lib/X11/fonts /usr/X11R6/lib/X11/fonts some_fs binary 0= 0 y: /y some_fs binary,cygexec 0 0 # This is default anyway: # none /cygdrive cygdrive binary,user 0 0 ------=_NextPart_000_00A7_01C8E683.1D9B2430 Content-Type: text/plain; charset=us-ascii -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ ------=_NextPart_000_00A7_01C8E683.1D9B2430--