Mail Archives: cygwin/2006/12/06/14:34:48
Tom Rodman wrote:
> On Mon 12/4/06 14:47 CST cygwin AT cygwin DOT com wrote:
> --snip
>> ~ $ date;uname -a
>> Mon Dec 4 14:31:38 CST 2006
>> CYGWIN_NT-5.0 OurServer121 1.5.22(0.156/4/2) 2006-11-13 17:01 i686 Cygwin
>> ~ $ printf '\377\376h\000\r\000\n\000'|file -
>> /dev/stdin: MPEG ADTS, layer I, v1, 192 kBits, 32 kHz, Stereo
>> --snip
>> ~ $ date;uname -a
>> Mon Dec 4 14:34:15 CST 2006
>> Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux
>> ~ $ printf '\377\376h\000\r\000\n\000'|file -
>> standard input: Little-endian UTF-16 Unicode character data, with CR line terminators
>> ~ $
>>
>> From above you can see linux and cygwin "file" output differs. The printf
>> above was inspired recently when "file" mis-identified a unicode file.
>>
>> I don't think this is a new problem.
>
> Maybe not a new problem, but this older (flame me) cygwin version works better:
>
> ~ $ date;uname -a #box in Bangalore
> Thu Dec 7 00:51:35 IST 2006
> CYGWIN_NT-5.0 XXXblr001 1.3.20(0.73/3/2) 2003-02-08 12:10 i686 unknown unknown Cygwin
> ~ $ cygcheck -c file
> Cygwin Package Information
> Package Version
> file 3.39-1
>
> Use -h to see help about each section
> ~ $ printf '\377\376h\000\r\000\n\000'|file -
> standard input: Little-endian UTF-16 Unicode character data, with CR line terminators
> ~ $
>
> I understand this is low priority.. Thanks as always for cygwin!
This is a change (or bug) in 'file', not Cygwin. I get the same thing as you
do with Cygwin's version on FC4. If you think there is an issue here, you
should take it upstream.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -