Hit an interoperatibility issue today:
fat32 stack on OBSD would allow to create illegal file entries for
Micro$oft machines, like:
CON
PRN
AUX
CLOCK$
NUL
COM1
COM2
COM3
COM4
COM5
COM6
COM7
COM8
COM9
LPT1
LPT2
LPT3
LPT4
LPT5
LPT6
LPT7
LPT8
LPT9
and with illegal chars like '?'.
Is this on
Seems similar to this (very old) explanation
http://heirloom.sourceforge.net/mailx_aux_c.html
On Mon, Aug 1, 2011 at 1:09 PM, Daniel Gracia
lists.d...@electronicagracia.com wrote:
Hit an interoperatibility issue today:
fat32 stack on OBSD would allow to create illegal file entries for
Yep! That's it, and I totally agree with the discusion there but, as far
as msdosfs is in OpenBSD for the very reason of portability -and now I'm
supposing-, I wonder if this would be an any welcomed patch.
Anyway, I'm not dying for it... It's working as is for me :D
El 01/08/2011 14:08,
Le Mon, 01 Aug 2011 16:04:08 +0200,
Daniel Gracia lists.d...@electronicagracia.com a icrit :
Yep! That's it, and I totally agree with the discusion there but, as
far as msdosfs is in OpenBSD for the very reason of portability -and
now I'm supposing-, I wonder if this would be an any welcomed
Daniel Gracia lists.dani () electronicagracia ! com wrote:
This is more accurate than the thread title:
fat32 stack on OBSD would allow to create illegal file entries for
Micro$oft machines, like:
The naming of special devices is abstracted a little higher in the food chain:
On Mon, Aug 01, 2011, Daniel Gracia wrote:
Hit an interoperatibility issue today:
fat32 stack on OBSD would allow to create illegal file entries for
Micro$oft machines, like:
CON
Is this on purpose, or do you feel like applying a patch to throw an
error on these cases?
The special
6 matches
Mail list logo
