public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: jengelh@linux01.gwdg.de, linux-kernel@vger.kernel.org
Subject: Re: VFAT: Can't create file named 'aux.h'?
Date: Tue, 21 Mar 2006 13:04:28 -0800	[thread overview]
Message-ID: <20060321130428.a221ed24.pj@sgi.com> (raw)
In-Reply-To: <442050C8.1020200@zytor.com>

hpa wrote:
> Probably it would be worth trying to create "aux.h" under XP and see 
> what happens.  Unfortunately I don't have a 'doze system handy at the 
> moment.

On my windows xp box, I just ran the following three experiments,
all inside a window brought up by running Start->Run "cmd":
 
 C:\ copy con foo
 blah blah blah
 ^Z

 C:\ copy con aux
 blah blah blah

 C:\ copy con aux.h
 blah blah blah

The first experiment above created a file named 'foo',
containing 'blah blah blah'

The second and third experiments both returned to the
command prompt when I pressed "Enter" at the end of the
"blah blah blah", after first complaining:

   The system cannot find the file specified.
           0 file(s) copied.

This is on a fairly vanilla and uptodate Windows XP SP2.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2006-03-21 21:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 21:40 VFAT: Can't create file named 'aux.h'? Dirk Reiners
2006-03-20 21:45 ` Randy.Dunlap
2006-03-20 21:50   ` H. Peter Anvin
2006-03-21  7:57     ` Jan-Benedict Glaw
2006-03-21 17:41     ` Jan Engelhardt
2006-03-21 17:44       ` H. Peter Anvin
2006-03-21 17:58         ` Jan Engelhardt
2006-03-21 18:07           ` H. Peter Anvin
2006-03-21 18:11             ` Jan Engelhardt
2006-03-21 18:54               ` H. Peter Anvin
2006-03-21 19:06                 ` Jan Engelhardt
2006-03-21 19:15                   ` H. Peter Anvin
2006-03-21 19:55                     ` Vadim Lobanov
2006-03-21 20:05                       ` Hua Zhong
2006-03-21 19:57                     ` John Stoffel
2006-03-21 20:02                     ` Phillip Susi
2006-03-21 21:20                       ` H. Peter Anvin
2006-03-22 19:39                         ` OGAWA Hirofumi
2006-03-22 21:59                           ` Phillip Susi
2006-03-22 22:22                             ` linux-os (Dick Johnson)
2006-03-23  1:15                               ` Phillip Susi
     [not found]                           ` <442286CD.6070200@lsrfire.ath.cx>
2006-03-23 14:56                             ` OGAWA Hirofumi
2006-03-22 21:57                         ` Ulrich Mueller
2006-03-21 21:04                     ` Paul Jackson [this message]
2006-03-21  4:28   ` Phillip Susi
2006-03-21  5:24     ` Randy.Dunlap
2006-03-20 21:46 ` Jan Engelhardt
2006-03-21  5:49   ` Yaroslav Rastrigin
2006-03-21 11:46     ` linux-os (Dick Johnson)
2006-03-21 15:06       ` Phillip Susi
2006-03-21 15:18     ` Phillip Susi
2006-03-21 17:43     ` Jan Engelhardt
2006-03-20 22:07 ` linux-os (Dick Johnson)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060321130428.a221ed24.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=hpa@zytor.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox