Bug 450408 – sys-apps/file-5.12 - wrongly identifies kernel images

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sergey Popov 2013-01-05 15:56:32 UTC]

From upstream bugreport:

"After upgrading to file 5.12, linux kernel files are misidentified as boot sectors:

with file-5.11:

# file /boot/vmlinuz-linux
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 3.6.6-1-ARCH (tobias@T-POWA-LX) 1 SMP PREEMPT Mon Nov 5 11:57:, RO-rootFS, swap_dev 0x3, Normal VGA


with file-5.12:

# file /boot/vmlinuz-linux
/boot/vmlinuz-linux: x86 boot sector"

Little addition - with '-k' options output are almost the same as for previous versions

[Comment 1 Sergey Fionov 2013-01-08 13:59:30 UTC]

There is also a problem with bootsectors.

file-5.11:
# file -s /dev/sdc
/dev/sdc: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 1953525167 sectors, extended partition table (last)\011, code offset 0x0

file-5.12:
# file -s /dev/sdc 
/dev/sdc: x86 boot sector

[Comment 2 Thomas Capricelli 2013-01-22 19:17:19 UTC]

yeps, same problem here, and it hurts a lot. File bzImage is a very useful way to easily know which version of the kernel it is
before:
/boot/bzImage:          Linux kernel x86 boot executable bzImage, version 3.6.10 (root@xx) #8 SMP Thu Dec 13 19:12:52 CET 2012, RO-rootFS, swap_dev 0x3, Normal VGA

after:
/boot/bzImage:              x86 boot sector

[Comment 3 Sergey Popov 2013-01-23 06:01:52 UTC]

Patch from upstream bugreport does not help, so i filed another report. Will wait for feedback...

[Comment 4 Thomas Capricelli 2013-01-23 16:24:43 UTC]

Shouldn't 5.12 be masked ?
Anyway, I've locally masked on all my computers/servers.

[Comment 5 SpanKY 2013-02-09 06:51:18 UTC]

(In reply to comment #4)

not really grounds for masking

[Comment 6 SpanKY 2013-02-09 06:52:27 UTC]

should be all set now in the tree; thanks for the report!

Commit message: Pull magic updates from latest upstream git
http://sources.gentoo.org/sys-apps/file/file-5.12-r1.ebuild?rev=1.1