Re: kernel-patch questions
On Thu, Jun 08, 2000 at 11:02:49AM -0400, Russell Hires wrote:
>
> oops, not trying to frustrate you with my (foolish) persistence.
I am only frustrated about the non existant resonance on my plea for help
with the quick install documentation. And by the fact that I worked on it
until 1am last night and that I am terribly tired now...
> 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)
I did not build it. It must be some secret mac source, once I saw a pointer
to it, but I never got the source, even after I asked for it on this(?)
list. Usually the mac patches are synchronized with the m68k source tree,
seems this is not happening at the moment. Probably partially due to Jes'
new job, his vacation, the fine weather, the euro, general lack of time and
developers. Choose, but not more than three.
> 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."
Thanks for digging this out (can you put that into your sig, please? ;-)
I knew something like that had to be in there.
> Does this mean that we are forking the code for the linux kernel?
Yes. But Jes tries his best to get m68k patches into the main source.
Sometimes they are not accepted for various reasons, but if you look at the
diffs on erlangen, you should see that the diffs are becoming smaller with
time (the native diff converts the "main" (i386) source into m68k source or
vv, forgot which, I never use that). But this is very off-topic now and
belongs to the linux-m68k list...
> 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
order matters sometimes
> 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.
there must be a list for linux/m68k on macs. Better ask the people there,
they should know about it.
> The mac-m68k site hasn't been updated for months, unfortunately...
But maybe the mailing list is still alive?
Christian
Reply to: