Hi Brandon -
Yes and no. I've gone through the effort previously to use the developer
image to build the kernel modules and driver that I need. I've taken a
step back to rethink my options.
Initially I took the slice & dice approach by doing the following:
1) build my kernel driver, modules and userland libraries/executables
inside the developer image
2) package all of the relevant files together
3) take the published PXE image from a given stable release, unpack the
usr.squashfs file system from it, and patch it with the new files
- note that I include userland files because I want to test this both
inside of pure CoreOS and inside of Docker/rkt
4) PXE boot from this image
That all works fine (with some caveats) but I would ideally like a solution
that is more organic than this.
Next, I thought to add the build process to the SDK and have things built
along with the base CoreOS packages. With that being said, I'm not sure if
things like running depmod inside the context of the build process is even
an option. Surely that gets run at *some* point, but when?
What are your thoughts?
On Fri, Sep 16, 2016 at 5:45 PM, Brandon Philips <brandon.phil...@coreos.com
> Hey Jared-
> Would something like this help you from maintaining a custom build?
> On Fri, Sep 16, 2016 at 3:34 PM Jared White <jaredkeithwh...@gmail.com>
>> Apologies to all for being a newb at this. This is continued work along
>> the lines of including my own packages (a couple of kernel modules) within
>> an internal distribution of CoreOS.
>> The third party module that I would like to add requires kernel sources.
>> I can't seem to find those contained within the chroot when I drop into
>> *Question 1*: Does anyone know where these kernel sources are?
>> Surely they are accessible somehow?
>> Additionally, I'm completely new to ebuild and am trying to add my
>> package to be built when I run build_packages. I have added my package
>> ("foo/bar") to the RDEPEND list inside of third_party/coreos-overlay/
>> *Question 2*: is this the correct location to specify this
>> dependency so that it gets built when I invoke build_packages?
>> I have done the following:
>> 1) added my package ("foo/bar") under ~/trunk/src/third_party/foo/bar
>> 2) added a "bar.ebuild" file under this folder. All this does at the
>> moment is some boilerplate ebuild declarations and echo things to the
>> 3) For good measure, I re-ran "./setup_board --default
>> --board=amd64-usr --force" as well.
>> What occurs when I invoke build_packages follows:
>> emerge: there are no ebuilds to satisfy "foo/bar" for /build/amd64-usr/.
>> (dependency required by "coreos-base/coreos-0.0.1-r269::coreos"
>> (dependency required by "coreos-devel/board-packages-0.0.1-r5::coreos"
>> (dependency required by "coreos-devel/board-packages" [argument])
>> *Question 3*: What am I missing here? Do I have to register my
>> ebuild elsewhere?
>> Thanks in advance.