Hi dMb;

Am Donnerstag, 30. September 2010, 23:16:40 schrieb davidMbrooke:
> Hi kp,
> 
> On Thu, 2010-09-30 at 22:53 +0200, KP Kirchdoerfer wrote:
> > Looking on your list and having in mind that (all?) ISDN module are
> > missing in the current config, which I do not see on your list, I
> > believe that your comparision is for shure a start, but may be flawed by
> > changes in the kernel config file between 2.4 and 2.6.35.
> 
> Agreed. I did not intend this comparison to be exhaustive, just a
> starting point... 

That's how I understood, and hoped to say in my response. 

> There are certainly lots of new modules in 2.6 which
> need to be separately reviewed for inclusion, and other less obvious
> changes as you describe.
> 
> > I'd think, just add what you think is necessary, it most probably might
> > not have been catched on the first round of kernel config. As long as
> > you just add modules it won't harm anyway. everything else is open for
> > discussion.
> 
> OK. For now I will just add the modules that I need for my hardware
> since these should not cause any other problems. For the rest we can
> perhaps agree some general policies rather than reviewing every item.

My first policy for the second round of kernel config would be: if something 
can 
be added as module it doesn't need a review (unless it breaks the current 
stuff).
In the third round we shall review new options compiled _into_ the kernel.

IMHO the more important question is "what should be added to kmodules?".

As long as we did have a floppy only versin in mind, we've been very 
restrictive adding modules to save space for the floppy image. 
This can be changed, as we are not forced to fit to a floppy any more.

kp

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to