I still have not connected the dots all the way from the coreos ebuild files to the resulting coreos image.
One problem that I have is the final image contains modules and includes under /usr/lib64/modules/4.7.3-coreos-r1 instead of something like /usr/lib64/modules/4.10.1-coreos* I would guess that some dependency was not updated.... but I don't even see where the modules get generated. Is the kernel being built twice? (I do seem to be running the kernel I expect). Thanks, --MM-- The best way to predict the future is to create it. - Alan Kay Privacy matters! We know from recent events that people are using our services to speak in defiance of unjust governments. We treat privacy and security as matters of life and death, because for some users, they are. On Tue, Feb 14, 2017 at 3:02 PM, David Michael <[email protected]> wrote: > On Tue, Feb 14, 2017 at 2:42 PM, 'Matt Mathis' via CoreOS Dev > <[email protected]> wrote: > > Thank you! > > > > Does COREOS_SOURCE_REVISION need to be monotonic (within the kernel > > version), or just not match any recently cached versions? If I never > plan > > to build a stock kernel, is it risky to stomp on future versions from > > coreos? > > The value of COREOS_SOURCE_REVISION doesn't really matter as long as > it matches a coreos-sources ebuild file. When your coreos-kernel and > coreos-modules ebuilds have newer versions than the stock CoreOS > ebuilds, they will be built and pull in whatever coreos-sources > revision you specified as a dependency. > > Thanks. > > David >
