On Tue, Feb 14, 2017 at 1:46 PM, 'Matt Mathis' via CoreOS Dev <[email protected]> wrote: > I am trying to inject custom kernel code into CoreOS, to add experimental > instrumentation to TCP. This can not be done in a module: it requires > changes to the resident part of TCP. > > I am having difficulty connecting the dots from the upstream kernel, through > the gentoo build and release process, as wrapped in the CoreOS build > containers. > > I can inject patches at > coreos-overlay/sys-kernel/coreos-sources/coreos-sources-*.ebuild, but I > don't see the kernel build and the changes do not propagate into the target. > What am I missing?
You have to bump the ebuild revision to declare that there is a new version of coreos-sources to be built. Also bump coreos-modules and coreos-kernel, substituting the new coreos-sources ebuild revision in their ebuild files. Check the Git history for examples. > Alternatively can I substitute my own local kernel sources? I wrote some notes on manually building a kernel a while ago: https://gist.github.com/dm0-/1f656b68491cd22e65ae0f33d4f1dd25 . It's a bit dated now, but the idea might help. It is also possible to define other sys-kernel/*-sources projects and build on those, but that isn't documented by CoreOS and is a bit of a chore. Thanks. David
