Charles Steinkuehler wrote:
> If you're talking about the offsets when applying the patches, these don't
> worry me...as long as no hunks fail :) If you've got the re-computed
> patches for 2.2.19, can you send them to me (or point me to them). I didn't
> see any patch files in the kernel tarballs you've got on the SF site...
I'll send them to you.
> BTW: Am I right about the CD having a full kernel source directory? If so,
> is it pre-patched, or are the patches available seperately, or both?
It does. It has the full source to the latest version of 2.2 and 2.4;
the one on SourceForge may have more than that. These are original
source from kernel.org, as well as crypto patches (in their original
tar.gz file). The patches are in a separate directory.
> Yeah, patches & configs, but mainly the patches (and if you've got it, the
> order you applied the patches). I need to be able to turn a 'virgin' 2.2.19
> kernel source tarball into the source tree you used for the 2.2.19 Oxygen
> kernels.
Remember that the Oxygen kernels also use the Openwall patch; this patch
is included in the patches subdirectory on the CDROM.
> Along the same lines, should we try to standardize a set of patches for LRP,
> (other than the mandatory linuxrc-always and initrd-archive), or just
> continue to leave this up to whoever's making a particular
> kernel/distribution?
I've never expected everyone to want to use Openwall, or other things.
I've also applied in the past patches like the Linux Progress Patch
(gives a pretty picture during loading) or the bridge firewall patch.
The LPP patch failed badly; the bridge firewall patch seems to work well
(or at least, not interfere).
There's also numerous other patches; check out the CDROM's
kernel/patches directory. Can't imagine everyone would want the same
thing.
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
