X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 7 Jan 2010 18:53:00 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 2nd Try: nwfs problem Message-ID: <20100107175300.GO23972@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jan 7 11:13, Thorsten Kampe wrote: > * Avi Schwartz (Wed, 6 Jan 2010 11:01:03 -0600) > > > > I upgraded to the latest cygwin version yesterday and since then I have a > > problem I never encountered before. It may have to do with the Netware file > > system. > > > > Here is what mount shows: > > > > C:/cygwin/bin on /usr/bin type ntfs (binary,auto) > > C:/cygwin/lib on /usr/lib type ntfs (binary,auto) > > C:/cygwin on / type ntfs (binary,auto) > > C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto) > > F: on /cygdrive/f type nwfs (binary,posix=0,user,noumount,auto) > > G: on /cygdrive/g type nwfs (binary,posix=0,user,noumount,auto) > > M: on /cygdrive/m type ntfs (binary,posix=0,user,noumount,auto) > > P: on /cygdrive/p type nwfs (binary,posix=0,user,noumount,auto) > > Y: on /cygdrive/y type nwfs (binary,posix=0,user,noumount,auto) > > Z: on /cygdrive/z type nwfs (binary,posix=0,user,noumount,auto) > > > > The problem I am having is with the F, G, P, Y, and Z drives which are all > > of the nwfs type. C and M which are ntfs are fine. > > I can't reproduce the issue. Neither with NWFS nor NcFsd. Neither with > the current 1.7 nor with the latest snapshot > > admin AT windowsxp% /usr/lib/csih/getVolInfo /cygdrive/f > Device Type : 7 > Characteristics : 30 > Volume Name : > Serial Number : 3232235521 > Max Filenamelength : 255 > Filesystemname : > Flags : 12 > FILE_CASE_SENSITIVE_SEARCH : FALSE > FILE_CASE_PRESERVED_NAMES : TRUE > FILE_UNICODE_ON_DISK : FALSE > FILE_PERSISTENT_ACLS : FALSE > FILE_FILE_COMPRESSION : TRUE > FILE_VOLUME_QUOTAS : FALSE > FILE_SUPPORTS_SPARSE_FILES : FALSE > FILE_SUPPORTS_REPARSE_POINTS: FALSE > FILE_SUPPORTS_REMOTE_STORAGE: FALSE > FILE_VOLUME_IS_COMPRESSED : FALSE > FILE_SUPPORTS_OBJECT_IDS : FALSE > FILE_SUPPORTS_ENCRYPTION : FALSE > FILE_NAMED_STREAMS : FALSE > FILE_READ_ONLY_VOLUME : FALSE > FILE_SEQUENTIAL_WRITE_ONCE : FALSE > FILE_SUPPORTS_TRANSACTIONS : FALSE I don't understand that problem at all. Given the above getVolInfo output, the filesystem should be treated basically like any FAT or FAT32 filesystem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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