Message-Id:	<199808011611.MAA16291@delorie.com>
From:	michael DOT mauch AT gmx DOT de (Michael Mauch)
To:	djgpp-workers AT delorie DOT com
Subject:	/dev/null and /dev/tty patch for libc.info
Date:	Sat, 01 Aug 1998 18:11:08 +0200
References:	<6psh15$iop$2 AT news-hrz DOT uni-duisburg DOT de> <xn7m0u2ja1 DOT fsf AT delorie DOT com>
In-Reply-To:	<xn7m0u2ja1.fsf@delorie.com>
MIME-Version:	1.0

Hi,

as suggested by DJ Delorie, here's a patch for the file
djgpp/src/libc/fsext/fsext.txh, so that it clarifies (I hope) that
`/dev/null´ and `/dev/tty´ are handled by libc itsself and need no
user-made File System Extensions. It's for DJGPP 2.01, I don't have the
2.02 alpha yet.

Regards...
		Michael

>>> start of patch
*** fsext.txh.orig	Fri Sep 20 04:37:20 1996
--- fsext.txh	Sat Aug  1 09:49:58 1998
***************
*** 91,97 ****
  
  Some function to create a connection to the extension.  This may be a
  custom function (such as @code{socket} for networking) or an extension
! to open (such as for @code{/dev/null} emulation).
  
  @item
  
--- 91,97 ----
  
  Some function to create a connection to the extension.  This may be a
  custom function (such as @code{socket} for networking) or an extension
! to open (such as @code{/dev/ttyS0} to access the serial port).
  
  @item
  
***************
*** 108,113 ****
--- 108,118 ----
  The core functionality of the extension, if any.
  
  @end itemize
+ 
+ Please note that the special Unix filenames @code{/dev/null} and
+ @code{/dev/tty} are already mapped to the appropriate DOS names
+ @code{NUL} and @code{CON}, respectively, so you don't need to write
+ extensions for these.
  
  @c
----------------------------------------------------------------------
  @node __FSEXT_alloc_fd, file system
<<< end of patch

- Raw text -