public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Jan Engelhardt <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:20:28 -0800	[thread overview]
Message-ID: <44206E1C.6090808@zytor.com> (raw)
In-Reply-To: <44205BC5.9040200@cfl.rr.com>

Phillip Susi wrote:
> H. Peter Anvin 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.
> 
> 
> kernel32.dll's CreateFile() and other apis normally perform translation 
> which includes special handling for dos device names including AUX.  You 
> can bypass this by prefixing the absolute file name with the string 
> "\\?\" and this will allow you to create a file named AUX.  It also 
> allows you to reference file names with absolute paths greater than 255 
> characters.
> 

So, in other words, Windows will let you create these files; it will 
just make you just through hoops to access them.

Sounds like they should be able to be legitimately created.  If the 
shortnames are mangled, even DOS or Win9x could access them using the 
shortname.

	-hpa


  reply	other threads:[~2006-03-21 21:20 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 [this message]
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
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=44206E1C.6090808@zytor.com \
    --to=hpa@zytor.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    /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