* new-features.sgml (ov-new1.7-file): Add new hardlink behaviour on
filesystems not supporting hardlinks. * overview2.sgml (ov-hi-files): Change descripton accordingly.
This commit is contained in:
parent
6cabe044dd
commit
8fd422fe4e
|
@ -1,3 +1,9 @@
|
||||||
|
2009-09-21 Corinna Vinschen <corinna@vinschen.de>
|
||||||
|
|
||||||
|
* new-features.sgml (ov-new1.7-file): Add new hardlink behaviour on
|
||||||
|
filesystems not supporting hardlinks.
|
||||||
|
* overview2.sgml (ov-hi-files): Change descripton accordingly.
|
||||||
|
|
||||||
2009-08-26 Corinna Vinschen <corinna@vinschen.de>
|
2009-08-26 Corinna Vinschen <corinna@vinschen.de>
|
||||||
|
|
||||||
* new-features.sgml (ov-new1.7-posix): Add "KOI8-R" and "KOI8-U"
|
* new-features.sgml (ov-new1.7-posix): Add "KOI8-R" and "KOI8-U"
|
||||||
|
|
|
@ -100,6 +100,10 @@
|
||||||
- Recognize Samba version beginning with Samba 3.0.28a using the new
|
- Recognize Samba version beginning with Samba 3.0.28a using the new
|
||||||
extended version information negotiated with the Samba developers.
|
extended version information negotiated with the Samba developers.
|
||||||
|
|
||||||
|
- Stop faking hardlinks by copying the file on filesystems which don't
|
||||||
|
support hardlinks natively (FAT, FAT32, etc.). Just return an error
|
||||||
|
instead, just like Linux.
|
||||||
|
|
||||||
- List servers of all accessible domains and workgroups in // instead of
|
- List servers of all accessible domains and workgroups in // instead of
|
||||||
just the servers in the own domain/workgroup.
|
just the servers in the own domain/workgroup.
|
||||||
|
|
||||||
|
|
|
@ -225,8 +225,8 @@ new UTF-16 style of symlinks is not compatible with older Cygwin release,
|
||||||
which can't read the target filename correctly.</para>
|
which can't read the target filename correctly.</para>
|
||||||
|
|
||||||
<para>Hard links are fully supported on NTFS and NFS file systems. On FAT
|
<para>Hard links are fully supported on NTFS and NFS file systems. On FAT
|
||||||
and some other file systems, the call falls back to simply copying the file,
|
and other file systems which don't support hardlinks, the call returns with
|
||||||
a strategy that works in many cases.</para>
|
an error, just like on other POSIX systems.</para>
|
||||||
|
|
||||||
<para>On file systems which don't support unique persistent file IDs (FAT,
|
<para>On file systems which don't support unique persistent file IDs (FAT,
|
||||||
older Samba shares) the inode number for a file is calculated by hashing its
|
older Samba shares) the inode number for a file is calculated by hashing its
|
||||||
|
|
Loading…
Reference in New Issue