2006/12/19, Vincent Panel <[EMAIL PROTECTED]>:
On 12/19/06, Luiz Fernando N. Capitulino <[EMAIL PROTECTED]> wrote: > Em Tue, 19 Dec 2006 11:09:05 +0000 > "Vincent Panel" <[EMAIL PROTECTED]> escreveu: > > | On 12/19/06, Buchan Milne <[EMAIL PROTECTED]> wrote: > | > On Monday 18 December 2006 21:21, [EMAIL PROTECTED] wrote: > | > > | > > Mainly the 3rd party addons should be documented/listed. > | > > Most users don't know what has been added. > | > > I only happen to know these things cause > | > > some time ago i did rebuilds of mandrivas kernel for myself, > | > > so i know most of those additions. > | > > > | > > Mostly it comes down to the point that new users > | > > want to compile things manually, and then i see that the module > | > > they need is already in mandriva kernel. > | > > | > They don't run 'modinfo <module>' first ? IMHO this is a mistake of upstream > | > module authors, they should always recommend that the user first check > | > whether the module is available (and the version, if that is critical, as in > | > less mature drivers). > | > > | > | Documenting 3rd party modules is one thing. Thanks to the previous > | mail, I wrote these two command-lines and it gives some interesting > | results : > | > | find /lib/modules/`uname -r`/kernel/3rdparty -name "*.ko.gz" -exec > | basename '{}' .ko.gz ';' > ~/3rd_party_module > | > | for a in `cat ~/3rd_party_modules`; do echo -n "$a :"; modinfo $a | > | grep description; done > | > | But there's still several problems : > | 1) 3rd party modules without description : what are they ? > > Keep them on the listing w/o the description. I'll take that list > and fix those modules and submit patches upstream. > > | 2) Hardware support is one thing, but everybody knows you have to make > | some choices during kernel compilation. Important choices should be > | documented somewhere (and no, "zcat /proc/config.gz" isn't enough) > > Sorry kid but this is very basic, we cannot teach people how to compile > kernels. Google is your friend.I think you misunderstood. What did the Mandriva kernel team has done to the default vanilla kernel configuration : that's all I want to know, nothing more, nothing less. Google won't tell me. Mandriva should.
I'm all for this... I'm still trying to get how mandriva changes default kernels. this could improve other people making patches.
> What we _must_ document on the other hand is how patches are handled in > Mandriva's kernels. There're some documentation about that already > though, in the kernel tree. How patches are handled ? This is purely internal documentation and users do not care about it, or maybe I did not understand what you mean.
a short methodology can be usefull, also for people wanting to help/submit patches/trying to debug some problem.
> | 3) None of these things are mentioned in a manual (choices and 3rd > | party modules) or even a readme file. That's exactly what the bug > | report is about. Having the necessary information using a specific > | command-line isn't enough. Harddrake may be another good place to > | mention these "hardware" things. > > Hm, didn't get this one. > Simply said : all of this should be written somewhere (kernel-sources package + wiki ?). It was an answer to replies saying "you just have to run XXX and you get what you're looking for" : this isn't enough.
also a very usefull thing is a small script that list the files that are missing for a successfull FTP installation (2007.0 and cooker) to see if the FTP is installable without installing... -- Alien is my name and head-biting is my game
