-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gary Lawrence Murphy wrote: >>>>>>"B" == Buchan Milne <[EMAIL PROTECTED]> writes: > > > B> Gary Lawrence Murphy wrote: > >> I'm hoping I missed something, but the apm-tools (apmd) tell me > >> the 9.1 distro kernel > > B> Of course, this is the wrong list for this question ... > > Even if we're building cooker with options incompatible with laptops?
Well, asking on a list where more people run the affected kernel (2.4.21.0.13mdk or 2.4.21.0.18mdk) may help ensure the validity of your claim. FYI, my Thinkpad 600X runs either acpi or apm just fine on 2.4.21.0.13mdk (sorry, can't give definitive answers for other kernels, as I have so many installed on it now for other reasons). > > Maybe I'm mistaken. I thought the purpose of cooker was to ensure a > consistent and robust distribution through massively parallel > debugging under wide user circumstances -- unless there's good reason > to believe this subsystem has changed, aren't the lessons of > installing the just-prior release in unusual circumstance suitable > topics for discussion? > > For example, does the cooker list not care if the pcmcia_cs *.conf > files mistakenly assign prism2 wireless cards to hermes chipsets or > that the prism2_cs module, according to Google search results on > "mandrake prism2_cs" has _never_ been successfully configured? If you > ask me, we'll never get a distro 'perfect', but it still makes us look > bad if we include dysfunctional parts Of course it is all valid, but the points you are missing out are: 1)What relevance is a bug in the previous ditro to the next one if it's already fixed in cooker? 2)Cooker can't support people running a mix of a stable release and cooker So, if you are running full cooker, and you have problems, file a bug. If you are running 9.1, check first with another list (expert, a.o.l.m etc), and then file a bug for 9.1 (there is no official procedure for this though ... I think the current method is to abuse mandrakeexpert for this). If you are absolutely sure (ie it's a config file, and you have checked Mandrake's latest package in cvs) it's still applicable in cooker, then file a bug in bugzilla. For the kernel, and only the kernel, it may be valid to run the current cooker kernel (kernel-2.4.21.3mdk-1-1mdk) on 9.1, but you better be sure of your stuff if you do things this way. If it's any other package, rebuild it on your stable release, send any changes required to the maintainer, and hope he's interested in having the packages build on older releases (it is quite a bit of work). Sorry, but it's just too difficult to debug cross-release stuff, for instance there was someone who complained that libsmbclient packages were wrong (since it wanted him to install samba-common-2.2.7a-8mdk and uninstall libsmbclient0). But 2.2.7a-8mdk *is* only in 9.1, and in 9.1 there *is* no libsmbclient package. Having to track this down only to find what the user has done is simply a waste of time ... Regards, Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/FCGRrJK6UGDSBKcRAvp0AKCQxG/ptyvOiD7mKGpLPKohBZaoDQCgsnk1 wt5fA0XXNkB1QgkF2rwFzAA= =yCAj -----END PGP SIGNATURE----- ****************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. ******************************************************************
