From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Phillip Susi <psusi@cfl.rr.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org
Subject: Re: VFAT: Can't create file named 'aux.h'?
Date: Thu, 23 Mar 2006 23:56:20 +0900 [thread overview]
Message-ID: <87d5gdky5n.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <442286CD.6070200@lsrfire.ath.cx> (=?iso-8859-1?Q?Ren=E9?= Scharfe's message of "Thu, 23 Mar 2006 12:30:21 +0100")
René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> OGAWA Hirofumi schrieb:
>> Looks like we get a good reason to kill strange reserved names in vfat
>> (and msdos too?).
>>
>> Could you/anyone check what shortname is used for "AUX" if it is created
>> in cmd.exe?
>
> on Windows XP Home SP2 I did:
>
> mkdir d:\test
> cd /d d:\test
> echo 1 > \\?\d:\test\aux
> echo 2 > \\?\d:\test\nul
> echo 3 > \\?\d:\test\nul.x
> echo 4 > \\?\d:\test\nul.longext
> echo 5 > \\?\d:\test\...
> echo 6 > "\\?\d:\test\[];,+="
> echo 7 > "\\?\d:\test\ "
> dir /x > a.txt
>
> And here's the contents of a.txt:
>
> --- snip! ---
> Datenträger in Laufwerk D: ist 53_00_00
> Volumeseriennummer: 1002-884F
>
> Verzeichnis von D:\test
>
> 23.03.2006 12:21 <DIR> .
> 23.03.2006 12:21 <DIR> ..
> 23.03.2006 12:21 4 0103~1
> 23.03.2006 12:21 4 7154~1 ...
> 23.03.2006 12:21 0 a.txt
> 23.03.2006 12:21 4 aux
> 23.03.2006 12:21 4 nul
> 23.03.2006 12:21 4 NUL~1.LON nul.longext
> 23.03.2006 12:21 4 nul.x
> 23.03.2006 12:21 4 ______~1 [];,+=
> 8 Datei(en) 28 Bytes
> 2 Verzeichnis(se), 31.506.370.560 Bytes frei
> --- snip! ---
>
> So, no shortname is created for aux on my machine.
Thanks, Phillip and Rene.
It seems the shortname. Because "a.txt" is using same form, and
"no shortname" is meaning a "broken directory entry" in fat spec.
> Of course that doesn't prevent us from creating one in vfat, right?
Yes. We would not need special case for devices.
I'll remove reserved names from vfat/msdos, because many OSes/commands
(even Windows) creates it.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2006-03-23 14:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 21:40 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 [this message]
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=87d5gdky5n.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/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
all inboxes | Powered by JetHome®