> bccz> Maybe you have an old page cached, but at least all the NVidia > kernel bccz> packages have been updated. I hope the ATI and winmodem > drivers could also I know how to check for a page in cache. It wasn't > it. > > bccz> BTW, this is better than 9.1, where Mandrakesoft did not update > any of the > bccz> proprietary kernel modules, and Club contributors did > it all. > > True. > > bccz> I don't think so. I think the current problem is not enough > resources (ie > bccz> more people sending patches, maintaining packages > would help). > > Well that's mandrakesofts problem.
It's your problem just as mich (if you have issues). > If they don't have enough money to > hire people they should ask for more volunteers. Development is totally open. If you want to help, you can. There is no need to ask for developers, because the policy is clear. Volunteers are welcome and always have been. > bccz> If you're going to use shorewall, get Florin's updated packages. > > Shorewall is a nice but when you have to build a firewall for network > which has 150+ users and 15+ classes of users that won't do. Your point? > bccz> I haven't seen the menu problem on my cooker box, so I don't > agree. And I > bccz> think the fact that many bugs have been fixed by > updates so fast is a good > bccz> thing. > > Well if you haven't seen it a loot of others have. But that doesn't help fix it. Mandrakesoft has problems reproducing it too (and 'just install a package' isn't a reproducible test case), so it's difficult for them to solve it. > Don't get me wrong updates are always good but they also show > that 9.2 wasn't tested enough. Or that bugs took longer to solve than the time available before they had to meet their commitments. Of course, Mandrake didn't go out telling people not to test this release ... > > bccz> Most people are just clueless, and run Redhat because everyone > else does, > bccz> Instead of dissing a distro you have significant > investment in, maybe you > bccz> could actually help to improve it? Many > of us do, and that is one reason bccz> why it *is* actually worthwhile. > > O now you really got me going. > Well let see. > I few years ago I needed postfix with mysql support. postfix in > mandrake didn't have it. I downloaded srpm and found that mysql was in > but switch in spec file wasn't activated. It took quite a while for a > new package to appear. Even one security update was released but the > switch wasn't activated. Once more i had to build it myself. Have you considered that maybe Mandrakesoft doesn't want postfix to depend on mysql by default, but *does* want to make it easy for someone to build the package with mysql support???? All you need to do is: $ rpm --rebuild --with mysql postfix*.src.rpm Luckily, ldap support is on by default. > What's the big deal? I had to avoid using automatic update procedure > since it would break my mail server. Yes, this needs to be solved in some way (but building postfix with mysql isn't the total solution, rather we need to deal with custom packages better). Anyway, you could just have added postfix to your /etc/urpmi/skip.list. > Next: > The same time I needed cyrus-imapd but no mandrake didn't have it. > Strange it was in 7.0/7.1. let me check. I pull from the closet my old > powerpacks and see that cyrus imapd was inside. > Ok again the same thing. I make a cyrus-imapd rpm. Test it for a few > days. everything is ok. After 2 years it's still working happily. > After some time I clean that spec file and send it cooker list. > Just wonted to help out. Nobody cares. > 2 years later cyrus-imapd still is not in standard set. No, it's in contrib, along with courier and binc and dovecot. There was resistance to having two IMAP servers in a desktop distro. IMHO, we should replace UW, and have Cyrus in main (reclaiming the space sendmail wastes ;-)). > I wasted all of my votes on it as so many others did but nobody > listens to us. So, then why is cyrus-imapd in contrib now? Why are there people who are working on making it easier to set it up? > The newest msn chat client or some other crap is > probably more important. Actually, it's not (as the gaim users will probably complain). > Next: a couple of posts concerning bugs missing functionality etc. all > passed by nobody cared. Please, post your bug numbers, otherwise there is no reason to give any credence to reports like this. > Next: mandrakeclub been a member since it was made. It wasn't worth the > money but still I'm a member. Why ? because I want to help. > It looks like nobody cares. How so? > bccz> Oh yes, of course you should always read the errata before > installing. And > bccz> maybe someone needs to add the menu issue to it > for now. > > How is errata being built. Look for yourself: http://qa.mandrakesoft.com/twiki/bin/view/Main/Mandrake92, look at the older revisions of that page to see the history of the errata, and you will see a number were up before ISOs were released. > Some user has complained that that is not > working. Possibly in a bug report on the RC or similar. How else do you make an errata? Report issues that no-one has tested?? > Lets look at a sample of current errata. At the end of install update is > not possible. Reality check - nobody bothered to check. Really ugly. > Fix : > "Format a floppy disk with a DOS filesystem > (in Linux, you can use the command "mkdosfs /dev/fd0"). > Copy patch.pl to the floppy disk. > Remove the floppy and reboot using the Mandrake Linux 9.2 > CD1 to do a CD-ROM installation. During boot, > press F1 at the splash screen, then place your floppy disk > that contains patch.pl in the floppy drive. At the prompt, > type "patch", then follow the installation as usual." > > Now i have to carry a floppy with me. How inconvenient. So, you have a better idea? Maybe you know how to patch CDs? Of course, you can always do the update after installation. It looks like you are new to cooker, so remember: 1)This is not a support list 2)Don't troll, contribute instead (that's the only way things get better). It also seems you are assuming the worst about everyone, instead of realising that there are constraints on many aspects (available time, number s of bad bug reports etc etc). Regards, Buchan
