GNU bug report logs - #23273
Error using windows 10 bash error 0x53464846 doing a tail -f

Previous Next

Package: coreutils;

Reported by: Dennis J <upumop <at> msn.com>

Date: Mon, 11 Apr 2016 23:02:02 UTC

Severity: normal

Merged with 24078, 24388, 24437, 24792, 24847, 24859, 25161, 25323, 25369, 25417, 25510, 25516, 25567, 25806, 25837, 25982, 26206, 26377, 26689, 26992, 27001, 27478, 27680, 30392

Done: Pádraig Brady <P <at> draigBrady.com>

Bug is archived. No further changes may be made.

Full log

Message #8 received at 23273 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Dennis J <upumop <at> msn.com>, 23273 <at> debbugs.gnu.org
Subject: Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a
 tail -f
Date: Tue, 12 Apr 2016 00:54:38 +0100

On 11/04/16 23:37, Dennis J wrote:
> I'm getting this error when doing a tail -f on a simple text file.
> tail: unrecognized file system type 0x53464846 for ‘kn.txt’. please report this to bug-coreutils <at> gnu.org. reverting to polling

Interesting. What do we call this win_bashfs or something?

Since there is just a single kernel involved, I'm guessing
that we don't need to tag this as a "remote" file system,
and that inotify calls will fail/succeed as appropriate.
That could be confirmed using the inotifywait command as detailed at:
http://bugs.gnu.org/23143#11

thanks
Pádraig
This bug report was last modified 6 years and 204 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.