Re: kernel-patch questions
----------
>From: "Christian T. Steigies" <cts@debian.org>
>To: Russell Hires <rhires@earthlink.net>
>Cc: debian-68k@lists.debian.org
>Subject: Re: kernel-patch questions
>Date: Thu, Jun 8, 2000, 10:15 AM
>
> On Thu, Jun 08, 2000 at 09:53:09AM -0400, Russell Hires wrote:
>>
>>
>>
>> Hello list,
>>
>> I'm beginning to understand why I need to use the modified sources (not
> no, you are not, or why are you trying to compile 2.2.12? Or are you trying
> to compile some mac kernel source?
oops, not trying to frustrate you with my (foolish) persistence.
>> the ones from kernel.org) to compile the kernel. I first had a problem
>> with the fpsp040 code, which I patched with little trouble. Now I've got a
>> problem with the code not compiling at another point.
>>
>> Do I need to apply all the patches from the kernel-patches .deb
>> file, the 2.2.10 patch, or just give up and get the modified source? On
>> the other hand, how come the kernel patches haven't made it into the main
>> kernel source tree?
>>
>> Here's the latest compile errors from my most recent attempt to
>> compile the 2.2.12 kernel.
> Sing after me: there is no 2.2.12 kernel source for m68k
> look at sunsite.dk or a mirror:
> ftp.uni-erlangen.de:/pub/Linux/680x0/v2.2
> -r--r--r-- 1 ftplinux ftpfau 14037509 Jul 19 1999 linux-2.2.10.tar.gz
>
>
Fair enough. My question, then, is to the one who compiled the 2.2.14 kernel
for the macs: how did you do it? That's the one I'm running on right now,
and it works, I just want to build firewall stuff into a kernel after 2.2.10
(because the net-masq HOWTO says there is a bug in the 2.2.10 code dealing
with IP-chains IIRC)
Quote from the FAQ: "DO NOT try to use standard Linux kernel source trees
(from e.g. ftp.kernel.org) to compile Linux/m68k. These trees are often
out-of-date and may include serious bugs due to changes being made on some
architectures not being propagated to Linux/m68k. Stick to Jes's source
trees (or Jesper's for Linux/APUS) unless you really know what you are
doing."
Does this mean that we are forking the code for the linux kernel?
Part of the reason I'm using the standard source is because that's what I've
got. Another reason is to learn how to do stuff, and one thing I've learned
is how to do a patch. I'm now at the point where applying one patch was
easy, but applying several is difficult. I don't know what I'm doing, but I
thought this was a good way to learn. That's why I was asking about how to
do what I'm doing. That's also why I was asking about giving up and getting
the modified source. Is it too much trouble for me to learn how to go the
long way and patch the standard source? If so, I will give up, and ask
questions about other stuff.
>This is the latest 2.2.x kernel source for m68k. There might be other kernel
> sources specifically for macs if you are using that, better ask the mac guys
> for help then.
The mac-m68k site hasn't been updated for months, unfortunately...
>
> You either use the debian source and respective patch deb (2.2.10, if they
> still exist on the mirrors), or use the m68k kernel source and patches
> ftp.uni-erlangen.de:/pub/Linux/680x0/kernel-patches/2.2.10
> (the debian patch package might include more patches, though).
>
> Ask Linus why some of the patches have not made it into the main source.
> Or, maybe read the FAQ and the linux-m68k website first?
>
> Christian
>
Reply to: