Hi Bill,
Thanks for the reply and the fix. I didn't realized that commit would fix this
issue.
Cheers,
Aaron
On Sat, 16 Feb 2019 13:31:39 +0800
Bill Yuan wrote:
> Thanks for reporting the issue and below is the fix.
> https://gitweb.dragonflybsd.org/dragonfly.git/commit/72ce8e08d0708ac9f09d
Thanks for reporting the issue and below is the fix.
https://gitweb.dragonflybsd.org/dragonfly.git/commit/72ce8e08d0708ac9f09d9cda56e3308ad8dcec48
On Fri, 15 Feb 2019 at 09:34, Aaron LI wrote:
> Hi Nima,
>
> I can confirm this issue. I believe this is a bug in IPFW3.
>
> Hi Bill, would you pl
Heh, just read the subject properly. Sorry bro.
/Max
On Sat, Feb 16, 2019 at 1:06 AM Max Herrgard wrote:
> Have you tried to play with the mount options -L and -D described in
> mount_msdos(8)? I haven't tried myself, but could be worth a shot.
>
> Cheers,
> Max
>
> On Fri, Feb 15, 2019 at 10:
Have you tried to play with the mount options -L and -D described in
mount_msdos(8)? I haven't tried myself, but could be worth a shot.
Cheers,
Max
On Fri, Feb 15, 2019 at 10:43 PM Mike Zhang
wrote:
> I have a bunch of files with unicode filenames that I'm trying to copy onto
> an MSDOS mount
I have a bunch of files with unicode filenames that I'm trying to copy onto
an MSDOS mount and what ends up happening is I get a bunch of invalid nodes
that cannot be accessed in any way, including rm -rf /mymountpt/dir. This
seems to be because mount_msdos is trying to be too smart for its own go
