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