1 |
On Sun, 2006-10-22 at 18:02 +0200, Michiel de Bruijne wrote: |
2 |
> On Sunday 22 October 2006 16:24, Chris Gianelloni wrote: |
3 |
> > I've started maintaining the genkernel kernel configs pretty much |
4 |
> > exclusively. I see no problem with iptables support being added. The |
5 |
> > best would be if you attached a patch against the current configs, as it |
6 |
> > would be easier on me, as I actually have to apply them to two places |
7 |
> > (genkernel SVN, and releng kconfigs for 2007.0) for the next release. |
8 |
> > The main change is that (for at least x86/amd64) we're trying to make |
9 |
> > the default kernel, which is also used on the LiveCD, as generic as |
10 |
> > possible and as feature filled as possible. |
11 |
> |
12 |
> That's good to read. |
13 |
> |
14 |
> Currently there are two kernel configs used for (2.4 and 2.6). |
15 |
> Features/modules are added and removed with every kernel release. Or entire |
16 |
> sections are moved to different parts in the kernel dependency hierarchy |
17 |
> (e.g. netfilter/iptables). There is also the problem that some modules wont |
18 |
> build in a specific kernel version but build/run fine in another version of |
19 |
> the kernel. |
20 |
> |
21 |
> I think if we want genkernel/livecd as feature filled as possible we should |
22 |
> extend the default configs to a x.y.z scheme. A new kernel version is |
23 |
> released about four times a year so this shouldn't be to hard to maintain. |
24 |
> I'm willing to do the work (creating patches and maintaining future kernel |
25 |
> configs), but do you agree and are willing to apply it? |
26 |
|
27 |
Sure. |
28 |
|
29 |
What would be best is if it looked for x.y.z first, then fell back to |
30 |
x.y, in the case of us not being as fast with the config as the kernel |
31 |
team with the kernel. ;] |
32 |
|
33 |
Another thing to realize is that while I will apply new configs/patches, |
34 |
I'm not planning on making a genkernel release for changes as minor as a |
35 |
new config. What I would suggest is that we make the "2.4" and "2.6" |
36 |
configs be equal to the latest config, with the x.y.z being preferred, |
37 |
if it exists. That way, when a new kernel comes out, it will start out |
38 |
using the last good config, until it gets updated with its own x.y.z |
39 |
config. |
40 |
|
41 |
> The next thing on my annoyance list is I need to put too many items in |
42 |
> modules.autoload.d that should be handled in init-scripts (e.g. acpid and |
43 |
> cpufreqd), but I deal with those later. |
44 |
|
45 |
Those should have bugs filed on their own. Truthfully, that stuff |
46 |
should all be loaded by the kernel automatically when the service is |
47 |
run. I don't have any ACPI/cpufreq stuff in my modules.autoload.d on |
48 |
this laptop, and both work fine for me. |
49 |
|
50 |
-- |
51 |
Chris Gianelloni |
52 |
Release Engineering Strategic Lead |
53 |
Alpha/AMD64/x86 Architecture Teams |
54 |
Games Developer/Council Member/Foundation Trustee |
55 |
Gentoo Foundation |