From 83029bb69e2ccb47ab5546551210b59c4d483198 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Fri, 18 Mar 2016 22:52:04 +0100 Subject: Remove references to older Cygwin releases from documentation Signed-off-by: Corinna Vinschen --- winsup/doc/specialnames.xml | 36 +++++++++++++++--------------------- 1 file changed, 15 insertions(+), 21 deletions(-) (limited to 'winsup/doc/specialnames.xml') diff --git a/winsup/doc/specialnames.xml b/winsup/doc/specialnames.xml index 543a4f127..d67d484c7 100644 --- a/winsup/doc/specialnames.xml +++ b/winsup/doc/specialnames.xml @@ -50,10 +50,9 @@ to be readable by the $USER user account itself. Invalid filenames -Filenames invalid under Win32 are not necessarily invalid -under Cygwin since release 1.7.0. There are a few rules which -apply to Windows filenames. Most notably, DOS device names like -AUX, COM1, +Filenames invalid under Win32 are not necessarily invalid under Cygwin. +There are a few rules which apply to Windows filenames. Most notably, DOS +device names like AUX, COM1, LPT1 or PRN (to name a few) cannot be used as filename or extension in a native Win32 application. So filenames like prn.txt or foo.aux @@ -95,12 +94,12 @@ can create and access files with trailing dots and spaces without problems. An exception from this rule are some network filesystems (NetApp, NWFS) which choke on these filenames. They return with an error like -"No such file or directory" when trying to create such files. Starting -with Cygwin 1.7.6, Cygwin recognizes these filesystems and works around -this problem by applying the same rule as for the other forbidden characters. -Leading spaces and trailing dots and spaces will be converted to UNICODE -characters in the private use area. This behaviour can be switched on -explicitely for a filesystem or a directory tree by using the mount option +"No such file or directory" when trying to create such files. Cygwin +recognizes these filesystems and works around this problem by applying +the same rule as for the other forbidden characters. Leading spaces and +trailing dots and spaces will be converted to UNICODE characters in the +private use area. This behaviour can be switched on explicitely for a +filesystem or a directory tree by using the mount option dos. @@ -227,11 +226,8 @@ semaphores, shared memory, and message queues, so a system without a real Apart from that, Cygwin automatically simulates POSIX devices -internally. Up to Cygwin 1.7.11, these devices couldn't be seen with the -command ls /dev/ although commands such as -ls /dev/tty worked fine. Starting with Cygwin 1.7.12, -the /dev directory is automagically populated with -existing POSIX devices by Cygwin in a way comparable with a +internally. The /dev directory is automagically +populated with existing POSIX devices by Cygwin in a way comparable with a udev based virtual /dev directory under Linux. @@ -245,15 +241,13 @@ Cygwin supports the following character devices commonly found on POSIX systems: /dev/full /dev/console Pseudo device name for the current console window of a session. - Up to Cygwin 1.7.9, this was the only name for a console. - Different consoles were indistinguishable. Cygwin's /dev/console is not quite comparable with the console device on UNIX machines. -/dev/cons0 Starting with Cygwin 1.7.10, Console sessions are numbered from -/dev/cons1 /dev/cons0 upwards. Console device names are pseudo device -... names, only accessible from processes within this very console - session. This is due to a restriction in Windows. +/dev/cons0 Console sessions are numbered from /dev/cons0 upwards. +/dev/cons1 Console device names are pseudo device names, only accessible +... from processes within this very console session. This is due + to a restriction in Windows. /dev/tty The current controlling tty of a session. -- cgit v1.2.3