Thanks for your help !
That was more or less my conclusion, but it would indeed be useful to
clarify that 4.1 and 4.21. are mutually exclusive.
And I must admit that the # vs $ steps had escaped me :(
Best regards.
-- Guy
Le 01/04/2023 à 18:56, Diederik de Haas a écrit :
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
I am in trouble... I first did "Obtaining the kernel source", and at the
end I got a /root/linux-source-6.1/ directory.
Then I did "Rebuilding official Debian kernel packages" and
"Preparation", and then I got among others a
/root/linux-source-6.1/linux-6.1.20 the content of which is similar to
the parent one, and where I can find, by the way, a debian directory.
It seems strange to me, is it correct?
No, this is not correct. No worries though as this is a great way to
learn how
we can improve the documentation :-)
With "Preparation" I meant paragraph 4.2.1 and you don't need to
follow 4.1.
Also worth noting is that command prefixed by `#` should be done as
root, but
the commands prefixed by `$` should be done as (normal) user.
So this is what you need to do:
# apt-get install build-essential fakeroot
# apt-get build-dep linux
While we're 'root', do this too:
# apt-get install devscripts
And then (as user):
$ apt-get source linux
$ cd linux-6.1.20
If you then do ``ls -lh`` you will see a ``debian`` directory.
So now you can run this:
$ bash debian/bin/test-patches <path-to-the-patch-file>
And now it should build a patched kernel for you.
If it is correct, in what order to do the patches (debian patches and
the revert patch)?
When you look at the output of the ``apt-get source linux`` you'll see it
download the linux source code and (automatically) applies the debian
patches
which are always applied when building a debian kernel.
This is excluding the patch I send earlier, but that gets applied when
you run
the ``bash debian/bin/test-patches`` command.
HTH,
Diederik
