linux-2.6.33.3-patched.tbz2

[hiro]

Is linux-2.6.33.3-patched.tbz2 up-to-date?

[gerald_clark]

The kernel has not changed.

[hiro]

But then what is this for?

Code: [Select]

squashfs-20100427.patch                                        30-May-2010 14:48   22K  
 squashfs-20100505.patch                                        30-May-2010 14:48  2.3K  
 squashfs-try-harder.patch                                      09-Jul-2010 22:47  549  
An other related question:
When I create my own kernel, do I also have to remaster the tinycore.gz, in order to also include the base modules?

[tinypoodle]

An other related question:
When I create my own kernel, do I also have to remaster the tinycore.gz, in order to also include the base modules?

Well, you could possibly get away with dynamical remastering, placing them in an an additional cpio archive as they would be in a different path, relative to 'uname -r'

[gerald_clark]

The shipped bzImage has not changed from 3.0rc1 to 3.4.
Therefore the "patched" sources on the web also have not changed.

[hiro]

Ok, thanks. I will use that as a base then.
I guess I should remove this thread? Or perhaps someone might move it somewhere more appropriate...

[gerald_clark]

Please leave it as it is useful searchable information for others.

[^thehatsrule^]

Those patches are for squashfs.ko which may be applied to get the same as the shipped module.

[hiro]

Ok, but in which sequence?
I don't know what to do with the line where the WARNING has been changed to an ERROR or vice versa.

[^thehatsrule^]

by alpha/date order or the way you have it should patch cleanly.. although for that line it probably doesn't matter in which order it happens in