From: r02@Safe-mail.net
To: linux-kernel@vger.kernel.org
Subject: kernel version problem after patching
Date: Thu, 18 Sep 2014 07:34:49 -0400 [thread overview]
Message-ID: <N1R-QFWRbm96u9@Safe-mail.net> (raw)
There is a kernel version problem after patching the kernel. After
installing the kernel and the kernel modules, without patching the kernel,
then "uname" shows the right kernel version and in "/lib/modules/" there
was the right directory created.
But after patching the kernel, installing it and the modules, then the
kernelversion shown with "uname" and the modules directory in
"/lib/modules/" is not correct anymore.
For example:
If i download the kernel 3.14.19, patch it, and install the kernel and the
modules then "uname" shows kernel version 3.14.0 and the modules are
installed in "/lib/modules/3.14.0/" instead of 3.14.19 which would be the
correct version.
The same problem happens with other kernel versions too below 3.14.19 and
also to kernel version 3.16.3 and versions below. But probably much more
kernel versions are affected from this problem.
If someone has an older kernel installed correctly, 3.16 for example, and
wants to install a patched second kernel, 3.16.3 for example, then the
modules directory of the first one will be overwritten unwanted due to
this version error because both kernels have the same modules directory
"/lib/modules/3.16.0".
next reply other threads:[~2014-09-18 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 11:34 r02 [this message]
2014-09-18 12:00 ` kernel version problem after patching Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 13:58 e40
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=N1R-QFWRbm96u9@Safe-mail.net \
--to=r02@safe-mail.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox