[07:40] <fabbione> Mithrandir: there is very little point in adding modules to kernel-wedge.
[07:40] <fabbione> if you need to ship modules, you need to do it directly from the kernel.
[07:40] <fabbione> we removed the "lists" dependencies between kernel and kernel-wedge
[09:34] <Mithrandir> fabbione: how do I do that?  I didn't see a way.
[09:35] <fabbione> Mithrandir: debian/d-i/
[09:36] <fabbione> there is shared/ that has the same meaning as adding a module to kernel-wedge
[09:36] <fabbione> the trick is in what you include in the unionfs-modules per arch
[09:36] <fabbione> instead of <unionfs>
[09:36] <fabbione> that would be "shared/unionfs"
[09:37] <fabbione> but if unionfs udebs are required, just remind me on monday
[09:37] <fabbione> i need to unfuck the baz repo first
[09:37] <fabbione> and open proper devel branch first
[09:37] <Mithrandir> I did that, but kernel-wedge gen-control didn't output anything about unionfs-modukes
[09:37] <Mithrandir> modules, even
[09:37] <fabbione> Mithrandir: you still need to tell that you want the module in a per arch specific way
[09:38] <fabbione> and note that kernel-wedge is stupid
[09:38] <Mithrandir> yes, but gen-control needs to have a description and so on, that seems to go into kernel-wedge.
[09:38] <fabbione> if you check the debian/rules, you will see that we copy the info in another dir to make them available to kernel-wedge
[09:38] <fabbione> Mithrandir: you can always override it locally
[09:38] <Mithrandir> how?
[09:39] <fabbione> anyway did you commit anything about this into baz?
[09:39] <Mithrandir> not yet
[09:39] <fabbione> if so in which branch??
[09:39] <fabbione> ojk
[09:39] <fabbione> ok
[09:39] <Mithrandir> overriding where modules goes (per arch) is easy, but you can't _add_ modules without touching kernel-wedge, or at least it seems that way to me.
[09:39] <fabbione> Mithrandir: debian/d-i/$arch/package-list iirc or very similar
[09:40] <fabbione> Mithrandir: nah.. we override all the lists of modules from kernel-wedge
[09:40] <fabbione> anyway, don't worry..
[09:40] <fabbione> we will look at it tomorrow after i get a proper baz branch and stuff
[09:40] <fabbione> sunday.. last day of holidays :)
[09:41] <Mithrandir> shouldn't there be a description too in the package-list?
[09:42] <Mithrandir> and shouldn't there be a shared/package-list too?
[09:44] <fabbione> Mithrandir: description can be added to arch/packages-list
[09:44] <fabbione> shared/package-list is not taken into account afaik
[09:44] <fabbione> last time i did check kernel-wedge code it only use the global provided by kernel-wedge and per arch specific one
[09:47] <Mithrandir> ok
[05:06] <zul> hey
[05:17] <zul> fabbione: are you around?
 /boot/config-2.6.10-5-k7:CONFIG_PREEMPT=y
 /boot/config-2.6.12-6-k7:# CONFIG_PREEMPT is not set
 so... preempt has been turned off in later packages?
[10:18] <mdz> Diablo-D3: you seem to have answered your own question before asking it :-)
[11:18] <Diablo-D3> mdz: hrm?
[11:18] <Diablo-D3> thats the question Im asking, btw
[11:18] <Diablo-D3> I dont know whats really goind on
[11:18] <mdz> Diablo-D3: you answered it already
[11:18] <mdz> in 2.6.10-5-k7, CONFIG_PREEMPT=y, and in 2.6.12-6-k7, CONFIG_PREEMPT is not set
[11:19] <Diablo-D3> mdz: but that doesnt mean 2.6.12 doesnt have preempt
[11:19] <Diablo-D3> say, if, preempt is default in 2.6.12
[11:19] <mdz> the default is irrelevant; if it is not set, then it is not enabled
[11:20] <Diablo-D3> why?
[11:38] <Diablo-D3> #ubuntu-laptop is open for buisness