linux-kernel - Re: RaspberryPi "is this a real kernel?"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55647AC3.7010803@gmail.com>
Date:	Tue, 26 May 2015 09:53:07 -0400
From:	Austin S Hemmelgarn <ahferroin7@...il.com>
To:	John Whitmore <arigead@...il.com>, Valdis.Kletnieks@...edu
CC:	linux-kernel@...r.kernel.org
Subject: Re: RaspberryPi "is this a real kernel?"

On 2015-05-25 05:24, John Whitmore wrote:
> On Sun, May 24, 2015 at 09:11:56PM -0400, Valdis.Kletnieks@...edu wrote:
>> On Sun, 24 May 2015 11:32:36 +0100, John Whitmore said:
>>
>>> $ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
>>> tail: +: invalid number of bytes
>>> * Is this a valid kernel? In pass-through mode.
>>
>> Looks like they try to use 'tail' to skip over something, but the + sign
>> in your uname -r gives it indigestion.  Try building with a version name
>> that doesn't include a + sign, and complain to the maintainers of mkknlimg
>> that they've probably got a parameter quoting problem (most likely, there's
>> someplace a
>>
>> tail -this -that $foo
>>
>> needs to be
>>
>> tail -this -that "$foo"
>
> Thanks a million for that help. I'll do a bit of looking into the scripts.
>
Actually, unless you are using ancient firmware (from prior to the first 
production revisions of the Model B), you should be able to boot the 
zImage directly, just drop it in /boot and edit config.txt to point to it.



Download attachment "smime.p7s" of type "application/pkcs7-signature" (2967 bytes)