Slashdot Mirror

• Lameness filters (It blocks a lot of legitmate posts)
• Unnessary posting delays. Hasnt taco learned to touch type? A lot of posts are typed in less than 20 seconds and it is a ANNOYING DELAY! 2 minute ban? Come on, so some are faster then others, big deal, some people have more to say than others
• Broken moderation system, The whole point is to sort the gems from the crap, yet a lot of posts designed to make a LIVELY DISCUSSION are MODERATED as flamebait! Come on, not everyone likes X, but just because some one bashes it dosent mean its Flamebait. Flame bait is more useful for DIRECT INSULTS and not legitmate discussions.

• Crapfloods, a meaningless flood of random letters or text, which the lameness filter does a crappy job at trying to stop, besides trolls have written tools using the opensource slashcode to generate crapfloods which bypass the filter
• Links to offensive websites, the most common one is known a http://www.goatse.cx, a awful site which shows a bleeding anus being stretched on the front page. Trolls sneak these links in by posting messages that look legitimate, but infact are sneaky redirects to the site. Common examples include rd.yahoo.com, www.linux-kernel.tk, goatsex.cjb.net, and googles "Im feeling lucky".
• Trying to break slashdot, this is actually a good thing, as it helps test slashdot for bugs. Famous examples include the goatse.cx javascript pop-up, the pagewidening post and the browser crashing post!

• Lameness filters (It blocks a lot of legitmate posts)
• Unnessary posting delays. Hasnt taco learned to touch type? A lot of posts are typed in less than 20 seconds and it is a ANNOYING DELAY! 2 minute ban? Come on, so some are faster then others, big deal, some people have more to say than others
• Broken moderation system, The whole point is to sort the gems from the crap, yet a lot of posts designed to make a LIVELY DISCUSSION are MODERATED as flamebait! Come on, not everyone likes X, but just because some one bashes it dosent mean its Flamebait. Flame bait is more useful for DIRECT INSULTS and not legitmate discussions.

• Crapfloods, a meaningless flood of random letters or text, which the lameness filter does a crappy job at trying to stop, besides trolls have written tools using the opensource slashcode to generate crapfloods which bypass the filter
• Links to offensive websites, the most common one is known a http://www.goatse.cx, a awful site which shows a bleeding anus being stretched on the front page. Trolls sneak these links in by posting messages that look legitimate, but infact are sneaky redirects to the site. Common examples include rd.yahoo.com, www.linux-kernel.tk, goatsex.cjb.net, and googles "Im feeling lucky".
• Trying to break slashdot, this is actually a good thing, as it helps test slashdot for bugs. Famous examples include the goatse.cx javascript pop-up, the pagewidening post and the browser crashing post!

• Lameness filters (It blocks a lot of legitmate posts)
• Unnessary posting delays. Hasnt taco learned to touch type? A lot of posts are typed in less than 20 seconds and it is a ANNOYING DELAY! 2 minute ban? Come on, so some are faster then others, big deal, some people have more to say than others
• Broken moderation system, The whole point is to sort the gems from the crap, yet a lot of posts designed to make a LIVELY DISCUSSION are MODERATED as flamebait! Come on, not everyone likes X, but just because some one bashes it dosent mean its Flamebait. Flame bait is more useful for DIRECT INSULTS and not legitmate discussions.

• Crapfloods, a meaningless flood of random letters or text, which the lameness filter does a crappy job at trying to stop, besides trolls have written tools using the opensource slashcode to generate crapfloods which bypass the filter
• Links to offensive websites, the most common one is known a http://www.goatse.cx, a awful site which shows a bleeding anus being stretched on the front page. Trolls sneak these links in by posting messages that look legitimate, but infact are sneaky redirects to the site. Common examples include rd.yahoo.com, www.linux-kernel.tk, goatsex.cjb.net, and googles "Im feeling lucky".
• Trying to break slashdot, this is actually a good thing, as it helps test slashdot for bugs. Famous examples include the goatse.cx javascript pop-up, the pagewidening post and the browser crashing post!

Confronting the KDE propaganda machine.

The KDE project is famous for its funded and organised trolling of weblogs and message board associated with Linux and Free software/open source. Outrageous newbie impressing claims are made for the software and huge quanities of FUD are spread to destroy competitors. If this sounds familiar, then you are correct, most of these tactics were lifted straight from Microsoft's arsenal of dirty tricks. The Windows look and feel is not the only thing the KDE project has copied! In this short article I will address some of the lies and FUD spread by the KDE trolling teams. It is my hope that this, in some small way, will redress the balance and re-introduce two things almost eradicated by the KDE project: Honesty and facts.

• Myth #1 - KDE is more integrated than GNOME

  The oft-heard cry of the noisiest KDE advocates. No explanation is given, the reader is expected to simply grok the wholesomeness of KDE and the lack of this mystical quality in GNOME. It is nonsense of course. Neither desktop is particularly "integrated" compared to Windows XP, and certainly not compared any version of the Apple Mac. Whatever "integrated" actually means.

• Myth #2 - KDE is easier to use

  Again, such nebulous arguments are never explained, and the reader is expected to simply understand the truth of the zealots statement. Both KDE and GNOME have user-interface irritations (all systems do), but "ease of use" is not a simple thing to measure. KDE has never been subjected to detailed user testing, unlike GNOME, and the claims of user-friendliness are from crazed supporters and not average users. Furthermore, the KDE faithful rarely look beyond simple-minded copying of Windows, and forget that administering a desktop system is just as important as having widgets in the correct place on the toolbar. For example: What about application installation and removal? GNOME has the excellent RedCarpet by Ximian, which makes the installation, removal and updating of applications trivial. KDE users are expected to fend for themselves with brutal command line driven systems. GNOME also has the excellent Ximian setup tools to handle various tricky cross-platform and potentially risky system configuration operations. KDE offers none of this, only a few small and lame Linux-only tools, which make no attempt at check-pointing to return to known working configurations.

• Myth #3 - KDE is more popular

  In what sense? Arguably more people use KDE, but it is a close run thing. Most KDE zealots use the results of online polls as proof of their superior userbase - which is, quite frankly, complete and utter nonsense. Online polls are the joke of the century; it doesn't even require a motivated script kiddie to render then worthless. A single post alerting the faithful on a zealot-ridden site can skew the result so much it makes American presidential elections look fair and well organised. Popularity is also difficult to measure when *both* GNOME and KDE are frequently installed on the same system. The systems can co-exist and even run at the same time, except for certain applications such as panels. Many KDE users actually run GNOME applications for their superior features and stability, not realising that by doing so they are barely running KDE at all.

  One of the few solid measures of popularity is commercial use of a desktop, and here, GNOME is far ahead with both Hewlett Packard and Sun committing to using GNOME as the desktop for their Unix systems. This also ties in with the previously mentioned ease of use. Sun's major contribution to the GNOME project is in the areas of user/developer documentation, testing, accessiblity and user-testing. Three of the less glamourous parts of desktop development. The arrival of the GNOME 2.x series will see these contributions reach fruitition and allow GNOME to make a quantum leap ahead of KDE in most of the basic computer/user issues.

• Myth #4 - Konqueror is the best Linux browser

  Oh for a penny every time this lie is told in any KDE story! Konqueror not a bad piece of software. It's authors deserve praise for the work done on it. However, the sheer amount of orgasmic gushing by the KDE faithful is completely out of proportion to its actual quality. It is quite unreliable and even simple standards compliant pages can crash it quite comprehensively. It is also lax in its support of basic web standards compared to either Mozilla or Opera. It is also extremely slow - much slower than the latest incarnations of the GNOME Nautilus filemanager/browser (a target of much KDE FUD during its development).

• Myth #5 - KDE applications are better/more advanced than GNOME ones due to the ease of developing in C++ using the Qt toolkit

  This is the most common wail heard by KDE developers, and yet it is easily disproved by looking at the actual applications for GNOME/GTK and KDE/Qt. KDE applications often have larger version numbers than GNOME ones... an old trick played by commerical software developers. Most KDE apps seem to jump for 1.x releases long before they are ready - KOffice being the best example. None of the components in Koffice are worthy of a 1.0 release, let alone 1.1 or 1.2.

  GNOME applications get a good deal more testing in their 0.x stages, and despite shorter development phases they mature and reach stable featureful release versions much more quickly. Some examples of this are: the superb Evolution (groupware/email), Gnumeric (spreadsheet), Pan (newsreader), The GIMP (image manipulation), Abiword (word processing), RedCarpet, X-Chat (IRC client), XMMS (media player), Galeon (web browser), and for developers: Glade and Anjuta. All of these packages ooze quality, and far outclass their KDE counterparts. It is no understatement to say that GNOME is at least 18 months ahead of KDE in applications, and pulling still further ahead.

  It's not just in the area of user applications that GNOME is vastly more advanced. With the forthcoming 2.x release, a number of impressive behind the scenes technologies will finally mature: component technology (bonobo), media (Gstreamer), internationalisation (pango). As a developement platform, GNOME 2.x is, conservatively, 2-3 years ahead of KDE. And what is more, because it is not tied to a lowest common denominator cross-platform bloat-fest like the Qt toolkit, the lead (as with applications) can only increase further.

  It is also worth noting that GNOME also develops code for use outside the project (see the XML libraries as one example) - the KDE project rarely (if ever) engages in this kind of work. KDE developers ensure that all software must link with Qt, and hence tie it closely with the Qt toolkit preventing re-use and enhancing the value of TrollTech intellectual property.

  
  Yet despite all this, we are still regularly fed the lie that Qt and C++ makes application and desktop development easier. Judge for yourself.

• Myth #6 - KDE is faster and takes less memory than GNOME

  KDE is written in C++. While this is not necessarily a problem, it can be when Visual Basic reject programmers (which the KDE project is overrun with) do not know enough to avoid important pitfalls that plague C++ software projects. Stupid use of autoincrementing operators and iteration with C++ objects; and masses of unnecessary allocations and deallocations of memory are two of the most common. KDE suffers badly from both problems.

  Perhaps the most cretinous of all problems is blaming the extremely slow startup times of KDE apps on GCC. The GNOME 1.x releases were hardly svelt (2.x fixes many of these issues - in fact, GNOME 2 is significantly faster with fewer resources than previous version, a feat quite beyond the KDE project), but GNOME is a fashion cat-walk superwaif when compared to KDE's 500lb fat-momma cheese-burger scoffing trailer trash. One need only look at the recent fuss over ugly KDE hacks (such as prelinking) used to bandage up the design and coding flaws in the decrepit KDE architecture to see the truth.

• Myth #7 - GNOME development is slower. KDE releases faster.

  Fundamental misunderstanding. The KDE project releases as one big lump of code due to its use of C++ and the many problems this causes with libraries. The project bumps the version number of the entire KDE system for the smallest modifications. GNOME, on the other hand is componentized and each component releases on a (almost) separate schedule, bumping it's own version number but not the main GNOME version (1.4, for example). Occasional releases of the entire GNOME system happen, and that's when the GNOME version number is bumped (currently it is at 1.4). To see this in action, use RedCarpet and you will regular updates to GNOME components. GNOME development is not slower, it is in fact faster and more advanced. Lamers and newbies, however, fail to understand the advantages of this method and just see KDE 1.1.1 followed a few weeks later by KDE 1.1.2. Wow! KDE roolz.
  
  Perhaps the greatest example of KDE release games occured with the recent KDE 3.0 release. In a desperate race to beat GNOME 2.0 to, the KDE team did not put back their schedule in the middle of a late release freeze when they suddenly added lots of new features - and, as expected, this has proved to be disasterous. KDE 3.0 is the worst KDE release yet in terms of reliablity - and is essentially early beta software put out as a stable release. Compare this with GNOME, which has had a number of betas and quality assurance procedures leading up to the eventual release of GNOME 2.0. The difference in approach is obviously due to the ultimate destinations of the systems and the vastly more experienced developers behind GNOME. GNOME is heading for commerical use on Sun and HP desktops, and hence requires commericial release quality. While KDE is destined for the porn and MP3 boxes of noisy advocates who don't mind huge numbers of crashes while waiting for KDE 3.0.0.4 to fix issues overlooked in the mindless rush to release. Quality control is an afterthought to the KDE project - the version number and releasing first are everything.

• Myth #8 - The Qt toolkit is cross-platform and yet takes advantage of each individual platform

  The Qt toolkit (the software at the heart of KDE) is supposedly a cross-platform toolkit allowing the lucky developer the opportunity to write Windows/Linux/Mac software all at once. And yet, among the magical mythical claims made, the most nonsensical is that it makes applications which take advantage of the distinct features of the different platforms. This is of course, nonsense. Qt is a bloated, slow layer that is slapped over a native system's APIs in an attempt to make all the systems look alike. It no more takes advantage of Linux/Windows/Mac than Java does - in fact it offers many of the disadvantages of Java with few of the advantages. If you have ever wondered why the KDE desktop looks so much like Windows... you need look no further than Qt. Qt is a lowest common denominator toolkit, and that LCD is Windows - Trolltech's, the creator of Qt, real market.

• Myth #9 - TrollTech is a friend of Free software

  To Be Written. Ideas: Qt started out as non-Free. KDE developers knew this violated the GPL, didn't care, stole others' GPL code by porting it to link (in violation of the license) with Qt and are therefore untrustworthy. KDE core developers work for TrollTech. Expensive per developer licensing for writing closed-source with Qt, and hence KDE. Trolltech only moved towards the GPL because of the success of GNOME. Labyrinthine licensing nightmare (3 licenses to deal with). Gradual migration of features belonging in KDE into Qt (and so into TrollTech's IP portfolio), allowing easy porting of apps to the revenue generating Windows world (see TheKompany for a perfect example), thereby making KDE an irrelevant launcher of Qt applications. Claims made that Qt is GPL, while true, hide the real truth. There cannot be a real fork of Qt for the KDE project: Core developers work for Trolltech; any fork would need to be full GPL and hence ban any closed-source apps from KDE altogether (all KDE apps must link with Qt); Any commerical licensees of Qt (non-GPL) would and could only follow TrollTech. KDE is stitched up good and proper.

• Myth #10 - KDE is more than attractive, but GNOME/GTK is ugly

  To be Written. Ideas: Mosfet liquid theme is an ugly and unstable hack. GNOME GTk icons are better thought-out and of a far higher quality than the poorly drawn and cartoonish and confusing KDE ones. Qt is basically a Windows-look on a Unix platform.

You don't need a fancy fetchmail/procmail setup to use SpamAssassin. MandrakeForum has an excellent HOWTO on how to set it up in KMail, or indeed any MUA that supports filtering through an external process/program. Works like a charm here - I'm never looking back!

Mandrake 8.2 was loaded onto a server and placed into the DMZ of Sec33.com's network. Without a firewall Mandrake sat and waited while an invitation to hack this system was broadcast around the globe. 1 week has passed, the base install of Mandrake 8.2 is rock solid. Without any protection from a firewall or packet filtering device the OS has seriously stood up and taken a beating. This latest version of the Mandrake flavor has received well over several thousand individual attacks and hasn't needed so much as a simple killing of a process or reboot. If you haven't taken a look at what we have going here. It is a must. The project has been named 'Simple Simon', and is available at www.sec33.com/page.php?page=simon.html. Check it out. Mandrake 8.2 is definately a winner.

Linux is a washing powder, didn't you know? Those of you who don't believe me read, read or read

I've got the feeling that Sun was the one not being very fast to tell/decide about what should happen with Star Office. This collapsed with the release date of 8.2. Of course Mandrake could have delay 8.2 because of Sun being unclear be that wouldn't have made us happy as well...

Read Deno's story about this. That will make things a bit clearer.

Besides the fact that we'll have to pay now if we want SO6, wich of course is Sun's decicion, I think the Mandrake guy's worked out a great deal, after all they did manage to make SO6 available early for Club members. They have managed to get everything they could possibly get out of this situation, so hail them for it and blame sun for the fact that you'll have to pay for SO6.

If you want to read this response by Deno you can find it in Mandrake Forum.

This is the only place I saw mention of membership level benefits being the same but it sure seems to imply they could change at any time.

on Mandrakeforum tom says: Update Mar 20, 2002: It looks like KDE 3.0 RC2 is not included in Mandrake Linux 8.2. My apologies for any confusion my contrary statement in this article might have caused.

For details: MS: Keep Your Filthy VNC Off Our XP

I've been holding off grabbing any of the release
candiates hoping the zlib, OpenSSH and other
recent security fixes would be incorporated.

I can't find mention of these updates for 8.2 on
the Mandrake announcement site, or forums.

Anyone know if zlib and the gang have been fixed?

My query about this on the Mdk forums was
immediately marked as "-1: Offtopic" suggesting
to me the fixes are not there. :/

Its for Mandrake forum

Are there GUIs for this? Sure. Are they sufficiently easy to use for a newbie (Are they easily accessible from the system menu or an icon)? Not yet.

Browse to software site and download (or insert CD), double-click on file, and have it installed and ready to run without ever opening a command prompt or needed to read a manual or a HOWTO. You want Joe Sixpack who doesn't "get" computers and has no desire to "get" computers? This is the entrance fee.

Moderation is broken on slashdot, want to know how its DONE! then visit MANDRAKE forum!

And why is this article coloured like piss and shit?

Details can be found here. The isos can be downloaded from here and all bug reports can be discussed here.

Very few 'really ugly' bugs have been found in the first beta, and we have been able to concentrate on hardware recognition, improving the *drake* tools, and updating the packages. For more details about what has changed since the beta1, and what should be tested, please wait for the articles in the "test this" serial.

MandrakeForum has much of the same info (and hasn't been hammered yet).

First beta of Mandrake Linux 8.2 escaped!

And how I am supposed to report bug for this 8.2 beta 1?

MandrakeForum has much of the same info (and hasn't been hammered yet).

First beta of Mandrake Linux 8.2 escaped!

And how I am supposed to report bug for this 8.2 beta 1?

MandrakeForum has much of the same info (and hasn't been hammered yet).

First beta of Mandrake Linux 8.2 escaped!

And how I am supposed to report bug for this 8.2 beta 1?

Mandrake Linux has recently opened a new site called MandrakeSecure which is focused on securing a mandrake box.

A recent article posted on MandrakeForum talks about ways to handle SPAM using postfix and qmail. Maybe this can be useful to the larger slashdot crowd?

You can find one of many tests here. Please return to your hole now.

Devfs is causing many people no end of grief, I wonder if Mandrake is going to actually fix a few things while their "production delays" are taken care of. If they don't, I suspect 8.1 is going to be one bumpy ride for them.

Well, for one.

Also, read through some of the past articles on Mandrakeforum starting with this.

You know I had a very strong sense of deja-vu here. Strangely enough, there was a comment on www.mandrakeforum.com with almost identical wording, except that poster had tried to install Mandrake 8.1. The I got curious and turned up a post to comp.os.linux.misc (here at Google) by purporting to be by one John Thompson with identical wording. So either you are trolling multiple places or you are plagerising someone else's trolling effort.

I know this is (slightly) off-topic, but maybe of interest anyway...

recently I've been looking for an alternative to Mandrake (now running 8.0 with kde2.2), so I've been checking out the web-sites of Suse, Debian and now also Progeny Debian...

One thing both debian and mandrake have in common is a convenient way to get security updates. With suse and progeny, the process of getting updates and security fixes isn't very clear from the website. (they may have a similar tool/service like MandrakeUpdate or dselect, but I don't know if they check mirrors and security sites...)

So I guess the createria for selecting a distro, for me are:

• ease of use/install
• up-to-date apps/gui
• security fixes and upgrades in one simple app
• text-based configuration and package tools
• ... (probably a lot more, but the above are most important)

Of course Mandrakeforum is very interesting and useful for news and tips. I think more distros should have them!

You posted the exact same message on Mandrake's forum. I think you have an agenda you're pushing, and I'm not buying it. Do you work for Red Hat? Linus Torvalds called RH with gcc 2.96 horribly broken. The people behind gcc 2.96 said they never expected what was essentially a pre-release version of 3.0 to end up in a distribution. I'm chalking your post up to misinformation.

http://www.mandrakeforum.com/article.php?sid=1191& lang=en : "Download speed has been decent at 30 K/s, but better get it before Slashdot announces it *grin*."

I understand Mandrake works real sweet on the thing. Check out the Mandrake Forum for the details for the work around needed to install it. Basically during install you need to pass the parameter :
linux mem=128

Here's a PDF describing the market.

Here is Mandrakes information page on the IPO.

Finally, this a price-per-share page.

I've long said this. Subscriptions are the way to go. I'm up for the FreeBSD one ;-). BTW. Mandrake is offering subscriptions of sorts now also with FREQ stuff, you can get a FREQ Subscription.

Yes there is: MandrakeFreq is a semi-stable release of Mandrake-Linux for folks who want to have the newest stuff, but do not dear installing cooker.

Yup, Tyan S2462 dual-athlon mobo has been tested with LM 8.0, and it works great.

Details here.
--

There is some discussion on MandrakeForum, and somewhere else I read a response that said the person simply recompiled the kernel and it worked. Sadly, the dependencies on the Kernel-source RPM are also wanting... they need a ncurses-devel RPM that is unavailable on the CDs and the FTP sites.

http://mandrakeforum.com

This is the general news forum and discussion board for Mandrake, it contains (or will contain, the format just changed) all the announcements and discussions for ALL the Mandrake sites. There are links on the left to the sites you want:

http://www.mandrakeuser.org

This is meant to have all the knowledge base articles for Mandrake. It seems to be down at the moment, but it does have a section on networking from what I remember.

http://mandrakecampus.com

This is the free Linux training site, and it provides instructions on setting up Mandrake for both desktop and server stuff. This does have a section on NFS setup and the like. If neither of these sites fix your specific problem there is:

http://mandrakeexpert.com

This is a combination knowledge base/expert question-answer site. You can post problems and other questions and find an expert to answer them.

If all else fails there are two Mandrake mailing lists available (newbie and expert) and you can try to post your problem as an article to MandrakeForum too.

G'D Luck!

"I'll take the red pill, no, blue. AAAHHHHHHHHHHHHHHHH........"

You have only been planing to send the email, but dosens of other people have actually been DEMANDING this donation page since we published the MandrakeFreak.

FYI, unlike some other companies Mandrakesoft lets people download the ISOs as soon as they are finished. This means that people will have ca. one monat of time for downloads before boxes hit the shops. This doesn't seam to hurt our sales, and we hope that at least some of people who download the ISOs will be happy to donate some money for further developement of their favorite distribution.

Hardly compliant with your paranoic idea, isn't it?

Reality is much simpler: it's hard to find people ready to mirror tons of different ISOs and directories. If you are willing to offer your super-ultra ftp server as a mirror, feel free to contact us imediately.

If you had done any background reading before posting about something you didn't know, you would see that people requested that mandrake set up a donations page. http://mandrakeforum.com/article.php?sid=694&lang= en

There is a world of difference AFAIK. However these differences are all in "bug-fixes" domain, and may not concern you at all. FYI, RC1 may be one day old for you, but it has been out since April 09-th

Install LM 8.0 on some old 486 machine, let it start KDE (or gnome, doesn't matter), open star office, maybe netscape too... Then go to cinema and by the time you come back some of the progs may already be ready and waiting for you...

OK, you could go for some lighter GUI, and avoid real slowware, but the sad fact is: old machines are too slow for modern GUI software. So what's the point on installing the newest disto on it?

• X-terminal. No need to install general purpose distribution on machine if it is going to be used as X terminal.
• firewall/rooter: If you have cable or (A)DSL connection at home or in some small office, install a firewall-distribution on it. Mandrake is working on one, and I'm sure there are other out there too.
• Smalish server on i486 box would be fine too.

Civileme has been investigating this for quite some time, and he wrote about it on Mandrakeforum. It looks as if WD has severe QA problems, and this time it got a help from chipset and a bug (or at least lack of workaround) in kernel.

• Numerical Analysis & the Walrus
• What Now? WINDisks, of course
• Is this Computer Science or Voodoo?

Civileme has been investigating this for quite some time, and he wrote about it on Mandrakeforum. It looks as if WD has severe QA problems, and this time it got a help from chipset and a bug (or at least lack of workaround) in kernel.

• Numerical Analysis & the Walrus
• What Now? WINDisks, of course
• Is this Computer Science or Voodoo?

Civileme has been investigating this for quite some time, and he wrote about it on Mandrakeforum. It looks as if WD has severe QA problems, and this time it got a help from chipset and a bug (or at least lack of workaround) in kernel.

• Numerical Analysis & the Walrus
• What Now? WINDisks, of course
• Is this Computer Science or Voodoo?

This article chimes in on the latest euphoria about 'apt-get' and the related bashing of RPM. Let me explain why I think Mr Petreley has no clue ...."

Have you tried Mandrake 7.2? They have both ATA66 and ATA100 support. However, only the ATA66 supports auto-detection. There's an article in here regarding how to install Mandrake on an ATA100.

As discussed recently on Mandrake Forum, this isn't actually the final release of Mandrake 7.2. Walmart required any products to be stocked for the Christmas season to be released at a certain time, and the final 7.2 release would not have made that, so instead they used the final Release Candidate of 7.2. It futures all the functionality of the final release, with only a few bug fixes implemented since then. I'm not sure it was the optimal choice, but if money's concerned, they really had to go with it.

I made a small investigation, and found out that Roblimo used a machine with two network addresses, which exposed one well-known (to me) CUPS weakness. The solution is simple and I have made it available on the Mandrake Forum.

About that, there is an interesting article that tries to explain the truth about the so called "numerous" bugs in RH 7.0. The funny point is that it's apparently been written by the Mandrakesoft folks! Read: http://www.mandrakeforum.com/article.php3?sid=2000 1005082533

[by the way, Mandrake 7.2 is coming along - start flame: potentially better than SuSE 7.0 ??? :-)))]

Mandrakeforum.com already had a story explaining it. As someone noted above, this data is pretty old, and Mandrake has some data from July that gives Mandrake the lead with 31.5%.

Mandrakeforum.com already had a story explaining it. As someone noted above, this data is pretty old, and Mandrake has some data from July that gives Mandrake the lead with 31.5%.