Re: [PATCH] Add the '-p4' options when exemplifying the module compilation

[Josh Stone <jistone at redhat dot com>]

On 06/27/2016 11:16 PM, Nikolay Borisov wrote:
> 
> 
> On 06/28/2016 03:44 AM, Josh Stone wrote:
>> On 06/27/2016 05:40 PM, nborisov wrote:
>>>
>>>
>>> On 27.06.2016 20:14, Josh Stone wrote:
>>>> On 06/27/2016 09:46 AM, Nikolay Borisov wrote:
>>>>> Currently the example command which supposedly should compile the
>>>>> instrumentation module is missing the '-p4' option, meaning that
>>>>> upon running it will compile and run the module. In order to make
>>>>> the command more in sync with what this particular chapter is about,
>>>>> add the -p4 options so that after running the command the user gets
>>>>> to copy the resulting module.
>>>>
>>>> It's implicitly limited to -p4 already when the chosen -r kernel doesn't
>>>> match the locally running kernel.  You'll see:
>>>
>>> Actually when I ran the command given in the book, the script would
>>> compile and run.
>>
>> Was your "-r kernel" the same as the running kernel?
>> Otherwise it really shouldn't happen, so we may have a bug...
> 
> Yes, when the kernel being compiled for is the same as the running it
> seems the script is being loaded. In either case, though, I wasn't
> expecting for the script to actually load.

OK, that's fine.  Using an explicit -p4 is correct to make sure that it
always stops before loading.

>>>>   WARNING: kernel release/architecture mismatch with host forces
>>>>   last-pass 4.
>>>>
>>>> Making it explicit to avoid the warning is good though.  It looks like
>>>> fche already pushed your patch.
>>>
>>>
>>>>
>>