From: "Hua Zhong" <hzhong@gmail.com>
To: "'Vadim Lobanov'" <vlobanov@speakeasy.net>,
"'H. Peter Anvin'" <hpa@zytor.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 12:05:55 -0800 [thread overview]
Message-ID: <000301c64d22$dd94ef70$853d010a@nuitysystems.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0603211154530.31582@shell3.speakeasy.net>
It's more "treating aux.* the same way as aux". It doesn't fail per se. If
you do "echo test >con.h", it will print to the screen.
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Vadim Lobanov
> Sent: Tuesday, March 21, 2006 11:55 AM
> To: H. Peter Anvin
> Cc: Jan Engelhardt; linux-kernel@vger.kernel.org
> Subject: Re: VFAT: Can't create file named 'aux.h'?
>
> On Tue, 21 Mar 2006, H. Peter Anvin wrote:
>
> > Jan Engelhardt wrote:
> > >>>>You're confusing characters which aren't legal *VFAT* names which
> those
> > >>>>which
> > >>>>aren't legal *FAT* (8.3) names.
> > >>>
> > >>>Could you please name an illegal FAT name being legal VFAT name?
> > >>
> > >>"Green Furry Submarine"
> > >>
> > >
> > > Ah well. But aux.h is also forbidden under VFAT, is not it? Or no,
> because
> > > it's "just" an 8.3 name?
> > >
> >
> > It probably depends on how picky you want to be. As far as I know, even
> > NT will recognize a character device name without leaving \DEV\, even
> > though \DEV\ has been the "official" device prefix since DOS 2.0.
> >
> > 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.
>
> Fails silently.
>
> > -hpa
> >
> > -
>
> Vadim Lobanov
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-03-21 20:08 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 [this message]
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
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='000301c64d22$dd94ef70$853d010a@nuitysystems.com' \
--to=hzhong@gmail.com \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vlobanov@speakeasy.net \
/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