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


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pádraig Brady <P <at> draigBrady.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#23273: closed (Error using windows 10 bash error 0x53464846
 doing a tail -f)
Date: Thu, 21 Apr 2016 20:58:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Thu, 21 Apr 2016 21:57:40 +0100
with message-id <57193EC4.7030000 <at> draigBrady.com>
and subject line Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a tail -f
has caused the debbugs.gnu.org bug report #23273,
regarding Error using windows 10 bash error 0x53464846 doing a tail -f
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
23273: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23273
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Dennis J <upumop <at> msn.com>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: Error using windows 10 bash error 0x53464846 doing a tail -f
Date: Mon, 11 Apr 2016 17:37:59 -0500
[Message part 3 (text/plain, inline)]
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

 		 	   		  
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Pádraig Brady <P <at> draigBrady.com>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, Dennis J <upumop <at> msn.com>,
 23273-done <at> debbugs.gnu.org
Subject: Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a
 tail -f
Date: Thu, 21 Apr 2016 21:57:40 +0100
[Message part 6 (text/plain, inline)]
On 12/04/16 09:11, Bernhard Voelker wrote:
> On 04/12/2016 01:54 AM, Pádraig Brady wrote:
>> 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?
>
> There's not much technical information available, but shouldn't
> that "Windows Subsystem for Linux" (WSL) just pass on some NTFS?
> It's not clear to me whether the entry point is a modified bash,
> library or whatever, so bash may not always be involved here.
> Therefore, I'd say "wsl_fs" or "wsl_ntfs" may be a valid name.
>
>> 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
>
> WSL is in early beta, so I wouldn't expect inotify to work.

Should be no harm trying though I expect.
I went with "wslfs" as underscores are the exception in names.

I'll push the attached later.

cheers,
Pádraig
[coreutils-wslfs.patch (text/x-patch, attachment)]

This bug report was last modified 6 years and 298 days ago.

Previous Next


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