From: richardd@cix.compulink.co.uk (Richard Donkin) Subject: Re: b17 bash problem with /dev/null on Windows 95 system 9 Dec 1996 14:04:19 -0800 Sender: daemon@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: Reply-To: richardd@cix.compulink.co.uk Original-To: jwe@bevo.che.wisc.edu Original-Cc: richardd@cix.compulink.co.uk, gnu-win32@cygnus.com Original-Sender: owner-gnu-win32@cygnus.com In-Reply-To: <199612090054.SAA00438@tillamook-sharp.eaton.net> > Yesterday, I wrote about a problem with b17, bash, and /dev/null on a > Windows 95 system. Some people suggested that it might be caused by > having an old copy of cygwin.dll somewhere but I am quite certain that > I only have files from b17 installed. > > In any case, I still have the problem but have since discovered that > although > > bash$ echo foo > /dev/null > > fails, > > bash$ echo foo > /dev/nul > > works (?!). I had this problem in trying to make RCS 5.7 - 'nul' is another NT/95 device name that is valid in every directory along with aux, lpt1, prn, etc. Suggestion - it might be worth putting in a horrible hack that normally maps at the API level to a file called '_'. This hack would be disabled for any /dev/* names, and 'null' mapped to 'nul' in this directory, enabling /dev/null and /dev/ to work properly. Richard -- richardd@cix.compulink.co.uk http://www.inside-edge.co.uk/ Inside Edge Consultancy Client/Server and Internet Applications PGP key from: pgp-public-keys@keys.pgp.net -or- http://www.four11.com/ - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".