Thank you for your testing. It make me suspect that the file name do not really contain space, but the string '\x20' instead. This is then interpreted differently by different programs. fsck understand it to mean 'x20', while mount understand it to mean '\x20'. Neither seem to understand it to mean ' ' (space).
Could the problem be with the process creating the symlink in the first place? Is it done by udev? Perhaps it should have created a file 'W-98 SE' instead? Then mount and fsck would just have to handle the space character like they normally do, using '\040'. Anyway, I am quite sure this problem can not be solved in the initscripts package. Not quite sure where to reassign it, though. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
