From: "W. Trevor King" <[email protected]>
On Sat, Feb 09, 2013 at 04:56:43AM -0800, Chris White wrote:
> > What's changed? Why do I need to seed catalyst with a config file,
> > when I don't need to from the handbook instructions? Maybe this usage
> > is just unimplemented because nobody has needed it yet?
> > …
>
> It's a TODO[1] right now. Personally though I recommend setting up a config
> manually, as it's a lot easier to debug kernel setup related issues when
> you're the one who configured everything and not genkernel.
Now it's done ;). I tested it today, and genkernel (unsurprisingly),
built its kernel fine without a seed config.
W. Trevor King (6):
generic_stage_target: Split ._build_kernel() out of .build_kernel()
generic_stage_target: Split ._copy_kernel_config() from
._build_kernel()
generic_stage_target.py: Dedent the bulk of ._build_kernel()
generic_stage_target: Split ._copy_initramfs_overlay() from
._build_kernel()
generic_stage_target: Handle unspecified boot/kernel/<kname>/config
kmerge.sh: Make /var/tmp/${clst_kname}.config optional
modules/generic_stage_target.py | 198 ++++++++++++++++++++--------------------
targets/support/kmerge.sh | 21 +++--
2 files changed, 114 insertions(+), 105 deletions(-)
--
1.8.1.336.g94702dd
