1.5.24 : "bash: /dev/null: No such file or directory" (Windows Fundamentals for Legacy PCs)

[Andre]

I'm seeing the following error every time I start a cygwin shell,
running on a freshing installed copy of Windows Fundamentals for
Legacy PCs (WinFLP).

bash: /dev/null: No such file or directory

>From the mailing list archives, it seems that the same symptom has
been seen in the past (albeit on other versions of Windows...)

http://www.cygwin.com/ml/cygwin/2006-06/msg00009.html
http://www.cygwin.com/ml/cygwin/2003-10/msg01005.html

Following previous advice given to people trying to debug the
problem, here's an extact of: strace sh -c "ls > /dev/null"

   57 3748990 [main] sh 2372 open: open (/dev/null, 0x601)
  205 3749195 [main] sh 2372 normalize_posix_path: src /dev/null
  142 3749337 [main] sh 2372 normalize_posix_path: /dev/null =
normalize_posix_path (/dev/null)
   85 3749422 [main] sh 2372 mount_info::conv_to_win32_path:
conv_to_win32_path (/dev/null)
   86 3749508 [main] sh 2372 mount_info::conv_to_win32_path: src_path
/dev/null, dst nul, flags 0x2, rc 0
   88 3749596 [main] sh 2372 build_fh_pc: fh 0x61167E40
   61 3749657 [main] sh 2372 fhandler_base::open_9x: (NUL, 0x601)
  192 3749849 [main] sh 2372 seterrno_from_win_error:
/ext/build/netrel/src/cygwin-1.5.24-2/winsup/cygwin/fhandler.cc:535
windows error 2
   97 3749946 [main] sh 2372 geterrno_from_win_error: windows error 2
== errno 2
   69 3750015 [main] sh 2372 __set_errno: void
seterrno_from_win_error(const char*, int, DWORD):310 val 2
   82 3750097 [main] sh 2372 fhandler_base::open_9x: 0xFFFFFFFF =
CreateFile (NUL, 0x40000000, 0x7, 0x22C250, 0x2, 0x80, 0)
   85 3750182 [main] sh 2372 fhandler_base::open_9x: 0 =
fhandler_base::open (NUL, 0x601)
   78 3750260 [main] sh 2372 open: -1 = open (/dev/null, 0x601)

Corinna's comment from the archives:

> However, the above effect is pretty weird. Is it possible (don't
> laugh) that the nul device is broken on your machine? Actually
> there's a driver ${windir}/system32/drivers/null.sys which manages
> that device. Or an even worse scenario: Do you (well, your machine)
> have some bad virus? So far, I have no other idea :-(

${windir}/system32/drivers/null.sys does not seem to be present in
WinFLP. I'm running a fresh install of the OS, sitting behind a
firewall, so the chances of Windows corruption or viruses seems low.
I can only assume that the lack of null.sys is the way Microsoft
intends it... ?!?

Is there an alternative way that cygwin could implement /dev/null in
this situation ??

Andre
--




 
____________________________________________________________________________________
Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck.txt
URL: <http://cygwin.com/pipermail/cygwin/attachments/20070312/f8075f9f/attachment.txt>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/