where to get kernel to build a custom one
lovecrea...@gmail.com
I'm currently using? If the one from kernel.org, will the
modifications to kernel source by by the distro lose and introduce
problems or bugs ever fixed by the distro?
Debian shows in his handbook[1] in sec4.4 and 4.5 that both are ok.
Thank you for your time.
[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
Ulrich Eckhardt
> From kernel.org, or the one of the distribution (manufacturer) which
> I'm currently using?
If you're afraid of breaking your system, try one that is close to what you
are currently running. That way, chances are lower that things suddenly stop
working.
> If the one from kernel.org, will the modifications to kernel source by
> by the distro lose and introduce problems or bugs ever fixed by the
> distro?
This sentence doesn't parse here. Guessing what you mean, I can say that the
one from kernel.org will probably not have changes that were made to the
distribution kernel, including bugfixes. You might be able to extract the
additional changesets from the distro kernel and apply them to the pristine
sources.
In any case, you can and will break your system. Make sure that you have a
working kernel around, available at boot time. Further, a bootable CD or
something like that, i.e. a rescue system should always be present. Lastly,
a second machine might be a good idea. Often you can still use SSH remotely
to shut down the machine even if you can't locally because you broke the
video drivers or similar stuff. Oh, and make sure important data is safe,
i.e. mirrored/backed up somewhere.
Welcome to kernel hacking! ;)
Uli
lovecrea...@gmail.com
Thaks for reply.
Sorry for my awful English.
Suppose I'm not submitting code, modules or drivers to linux kernel
right now (hope I will do it soon), and just going to make minor
changes in vfs (ie. some ../fs/*.c) for my own use.
I'm using Debian Lenny (503), and `uname -r` is 2.6.26-2-686. Do I
download a copy of kernel source from debian.org which produced /
correspoded to its `uname -r`, or do I download a 2.6.26.2 (?) copy
from kernel.org, and add my changes based on the just downloaded
source?
(Debian kernel `uname -r` 2.6.26-2-686 corresponds to kernel.org
2.6.26.2?)
Rainer Weikusat
> On Nov 20, 3:54 pm, Ulrich Eckhardt <dooms...@knuut.de> wrote:
>> lovecreatesbea...@gmai1.c0m wrote:
>> > From kernel.org, or the one of the distribution (manufacturer) which
>> > I'm currently using?
[...]
>> Welcome to kernel hacking! ;)
>>
>
> Thaks for reply.
>
> Sorry for my awful English.
>
> Suppose I'm not submitting code, modules or drivers to linux kernel
> right now (hope I will do it soon), and just going to make minor
> changes in vfs (ie. some ../fs/*.c) for my own use.
>
> I'm using Debian Lenny (503), and `uname -r` is 2.6.26-2-686. Do I
> download a copy of kernel source from debian.org which produced /
> correspoded to its `uname -r`, or do I download a 2.6.26.2 (?) copy
> from kernel.org, and add my changes based on the just downloaded
> source?
My suggestion would be to stay close behind the kernel.org releases,
eg use the highest-numbered minor version of the second most recent
kernel. This would be 2.6.31.x now. That's a conservative approach
which has worked mostly well for me for some years.
I have encountered exactly two issues so far: A 2.6 release from some
years ago broke the driver for a USB-to-serial adapater I needed to
use. This was a PITA, because the maintainer would neither believe in
bug reports nor accept patches. After months of occasional nagging and
presumably, complaints from user whose device were still not working
(mine did), he was at least willing to use the results of my work,
only doing a completely pointless rewrite of the code, dropping
while-loops and switch-statements with a reference to the
'undocumented coding style rules' I had violated. A fairly recent
release broke CD-ROM support for one computer I am using, arguably
because of a hardware bug. That was better: While it took me the
better part of a day to determine the cause of the problem and fix it,
the responsible person could at least be talked into actually applying
the patch. Overall, using the kernel.org code has caused me less
trouble than trying to work with the people who wrote it.
Ulrich Eckhardt
> Suppose I'm not submitting code, modules or drivers to linux kernel
> right now (hope I will do it soon), and just going to make minor
> changes in vfs (ie. some ../fs/*.c) for my own use.
>
> I'm using Debian Lenny (503), and `uname -r` is 2.6.26-2-686. Do I
> download a copy of kernel source from debian.org which produced /
> correspoded to its `uname -r`, or do I download a 2.6.26.2 (?) copy
> from kernel.org, and add my changes based on the just downloaded
> source?
I would suggest that you download the kernel from Debian. You could simply
use 'apt-get source linux-image-...' to get the sources. Build those,
install the resulting packages and reboot. If it works, you can start your
modifications. You can also download the sources from upstream, but in
general I would prefer going with the flow of Debian. If you think about
submitting patches, I also wouldn't download a tar archive from kernel.org
but rather use 'git' to retrieve the sources and manage your own changes.
Uli