Date: Wed, 15 Jan 1997 23:24:10 +0000 From: Brian Somers <brian@awfulhak.demon.co.uk> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: wilko@yedi.iaf.nl (Wilko Bulte), FreeBSD-hackers@freebsd.org Subject: Re: msdosfs creates illegal dir names? Message-ID: <199701152324.XAA15009@awfulhak.demon.co.uk> In-Reply-To: Your message of "Wed, 15 Jan 1997 14:10:37 %2B1030." <199701150340.OAA04206@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> You can't say "mkdir .foo", no, but the standards for what is and
> isn't a "valid" filename are pretty grey, and " .foo" is well
> within them.
Ah, but if DOS doesn't let you "mkdir" or "open()" .foo, that implies its invalidity. Other routines may support ' .foo', but correctly so, as they should "assume" that the filesystem is intact.
If DOS was a bit more solid, I would say that running "scandisk" should be the decider. It it allows it, it's valid and anything that doesn't is wrong.
--
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk/>;
Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701152324.XAA15009>