Hi folks,
I just uploaded a new Cygwin 1.7 test release, 1.7.0-38.
As already announced last year, just download
http://cygwin.com/setup-1.7.exe and use that setup tool to install
Cygwin 1.7. As usual, please report bugs and problems to the mailing
list cygwin AT
THIS IS STILL A TEST RELEASE. DON'T USE IN PRODUCTION ENVIRONMENTS.
What's new in contrast to 1.7.0-37:
===
- New header bits/wordsize.h.
- New function: glob_pattern_p.
- unlink(2) now tries even harder to remove files in use.
- fts(3) functions use d_type now.
- New ldd(1) tool.
- cygcheck recognizes Windows 7 and Windows 2008 R2.
- Drop the Cygwin-only ENOSHARE error in favor of ENOENT.
- On systems supporting WSARecvMsg (=XP) and WSASendMsg (=Vista) use
these functions if a non-empty msg_control buffer is given in calls to
recvmsg and sendmsg. Please note that the functionality of these
functions is extremly limited in Windows! For instance, calling
these function only works with SOCK_DGRAM and SOCK_RAW sockets.
Bugfixes:
=
- Fix handle leak in symlink code.
- Fix a path quoting problem in cygcheck.
- Fix link(2) to append .exe suffix to target only if source has a .exe
suffix as well.
- Handle a Samba 3.2.x problem in path resolution code.
- Fix an endless recursion in cygcheck when scanning the registry on
64 bit OSes.
- Fix a wrongly reported option ambiguity in getopt_long(3).
- getrlimit now returns correct upper hard limit for RLIMIT_NOFILE.
- Fix alignment problem in mmap(2) when mapping files.
- Allow multiple concurrent pthread_rwlock read locks per thread as
required by SUSv4.
Known problems:
===
- Broken pipe when trying to copy large files over scp.
FAQ:
- Q: How do I know that I'm running Cygwin 1.7.0-38?
A: The `uname -v' command prints 2009-01-21 12:03
Have fun,
Corinna
Just for completeness, here's once more the list of Changes in 1.7.0
related to 1.5.25:
OS releated changes:
- Windows 95, 98 and Me are not supported anymore. The new DLL will
not run on any of these systems.
File Access related changes:
- Mount points are no longer stored in the registry. Use /etc/fstab
and /etc/fstab.d/$USER instead. Mount points created with mount(1)
are only local to the current session and disappear when the last
Cygwin process in the session exits.
- PATH_MAX is now 4096. Internally, path names can be as long as the
underlying OS can handle (32K).
- UTF-8 filenames are supported now. So far, this requires to set
the environment variable CYGWIN to contain codepage:utf8. but this
will likely disappear at one point. The setting of $LANG or $LC_CTYPE
will be used instead.
- struct dirent now supports d_type, filled out with DT_REG or DT_DIR.
All other file types return as DT_UNKNOWN for performance reasons.
- The CYGWIN environment variable options ntsec and smbntsec have
been replaced by the per-mount option acl/noacl.
- The CYGWIN environment variable option ntea has been removed without
substitute.
- The CYGWIN environment variable option check_case has been removed
in favor of real case-sensitivity on file systems supporting it.
- Creating filenames with special DOS characters '', '*', ':', '',
'', '|' is supported.
- Creating files with special DOS device filename components (aux,
nul, prn) is supported.
- File name are case sensitive if the OS and the underlying file system
supports it. Works on NTFS and NFS. Does not work on FAT and Samba
shares. Requires to change a registry key (see the user's guide).
Can be switched off on a per-mount base.
- Due to the above changes, managed mounts have been removed.
- Incoming DOS paths are always handled case-insensitive and get no POSIX
permission, as if they are mounted with noacl,posix=0 mount flags.
- unlink(2) and rmdir(2) try very hard to remove files/directories even
if they are currently accessed or locked. This is done by utilizing
the hidden recycle bin directories and marking the files for deletion.
- rename(2) rewritten to be more POSIX conformant.
- Add st_birthtim member to struct stat.
- File locking is now advisory, not mandatory anymore. The fcntl(2) and
the new lockf(2) APIs create and maintain locks with POSIX semantics,
the flock(2) API creates and maintains locks with BSD semantics.
POSIX and BSD locks are independent of each other.
- Implement atomic O_APPEND mode.
- Handle NTFS native symlinks available since Vista/2008 as symlinks
(but don't create Vista/2008 symlinks due to unfortunate OS restrictions).
- Recognize NFS shares and handle them using native mechanisms.
Recognize and create real symlinks on NFS shares. Get correct
