public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: VFAT: Can't create file named 'aux.h'?
Date: Mon, 20 Mar 2006 13:50:29 -0800 (PST)	[thread overview]
Message-ID: <dvn835$lvo$1@terminus.zytor.com> (raw)
In-Reply-To: 20060320134533.febb0155.rdunlap@xenotime.net

Followup to:  <20060320134533.febb0155.rdunlap@xenotime.net>
By author:    "Randy.Dunlap" <rdunlap@xenotime.net>
In newsgroup: linux.dev.kernel
> 
> "AUX" is (was) a reserved "filename" in DOS.  The Linux MS-DOS
> filesystem preserves (protects) that.  The extension part does not
> matter; it only checks the first 8 characters of the filename.
> You'll need to use a different filesystem or filename...
> 

But this is VFAT, not FAT.  It should probably take the reserved name
and mangle it.

> 
> /* MS-DOS "device special files" */
> static const unsigned char *reserved_names[] = {
> 	"CON     ", "PRN     ", "NUL     ", "AUX     ",
> 	"LPT1    ", "LPT2    ", "LPT3    ", "LPT4    ",
> 	"COM1    ", "COM2    ", "COM3    ", "COM4    ",
> 	NULL
> };
> 

There should be more than that.  At the very least there is "CLOCK$"
(arguably anything with $), "MSCD001" (and probably more than 001), as
well as "COM5".."COM8".

	-hpa

  reply	other threads:[~2006-03-20 21:50 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 [this message]
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
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='dvn835$lvo$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --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