Odd msdos fs behaviour [was: Re: Odd FFS behavior]

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Edd Barrett <vext01@...>
Cc: OpenBSD <misc@...>
Date: Thursday, October 25, 2007 - 4:57 am

On Thu, 25 Oct 2007, Edd Barrett wrote:

> The directory made has been truncated msdos style. "a_frag~1".

While this is a workaround, mounting it with "-l" parameter (mount_msdos
-l) should be the proper solution. Of course, unless you need to keep the
filenames short.

On the other hand, one would expect the filesystem code to truncate the
filename before actually trying to open a file on such a filesystem. I
think that Msoft designed it that way. Currently, you create a file and
cannot stat it immediately afterwards. Oh, and a different new file has
appeared there in the meantime! I think it shouldn't work this way. Is it
a valid assumption?

Regards,
David

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Odd FFS behavior, Edd Barrett, (Mon Oct 22, 3:45 am)
Re: Odd FFS behavior, Edd Barrett, (Thu Oct 25, 3:52 am)
Re: Odd FFS behavior, Lars Hansson, (Thu Oct 25, 6:30 am)
Re: Odd FFS behavior, Edd Barrett, (Thu Oct 25, 8:06 am)
Odd msdos fs behaviour [was: Re: Odd FFS behavior], David Vasek, (Thu Oct 25, 4:57 am)
Re: Odd FFS behavior , Aaron W. Hsu, (Mon Oct 22, 12:49 pm)
Re: Odd FFS behavior, Otto Moerbeek, (Mon Oct 22, 4:14 am)
Re: Odd FFS behavior, Edd Barrett, (Mon Oct 22, 5:14 am)
Re: Odd FFS behavior, Otto Moerbeek, (Mon Oct 22, 5:46 am)
Re: Odd FFS behavior, David Vasek, (Mon Oct 22, 6:26 am)
Re: Odd FFS behavior, Denise H. G., (Mon Oct 22, 6:47 am)