ZDNet has published a evaluate by Jason Brooks of eWeek Labs comparing the Linux desktops. He writes: "eWeek Labs discovered that KDE (K Desktop Environment) comes a lot closer to delivering the type of clean interface that customers have come to anticipate from the Macintosh and Windows working techniques than does GNOME (GNU Community Object Mannequin Environment). In exams, KDE delivered snappier and extra polished performance than did GNOME on the same hardware." Nevertheless, he continues, "neither desktop interface has yet reached parity with the established players-pervasive help for options comparable to lower and paste throughout the interface can still be unpredictable." Strange to have picked out minimize-and-paste, as that ought to be a lot improved in Qt-3.0.It additionally could be nice to have uniform trying instruments throughout all distros of linux. A majority of these tools are problematic as distros fluctuate a lot. Please notice packages like Webmin which runs from inside konqueror very properly, handles practically anything you possibly can think about and works remotely through SSL. It's a fairly candy package deal and it is principally lots of Perl scripts. You would possibly take a look at kaptain too as a fast growth software, and there are advantages in these concepts. There's still time for you to discover ways to work on the code I suspect although.I personally assume that KDE improvement crew has extra expertise to put together an excellent desktop Linux distribution (or perhaps I am simply ticked-off that RedHat is just not using the complete capabilities of KDE 2.1.1 in RedHat 7.1). I am conscious of a number of issues that could make KDE an amazing desktop. I have performed this at dwelling with a severely modified RedHat 6.2 setup: 1. Get some real TrueType fonts. For some motive Type1 fonts don't show right, I think the Font Metrics is broken when anti-aliasing is enabled (the damaged-up format of the beginning page of the konqueror offers me this suspicion).When i used Win98 TrueType fonts, the whole lot looked good. It took me some time to search out some cyrillic TT fonts, however once these have been put in I used to be capable of learn Russian news AND the fonts looked significantly better than they ever did in Netscape, AND it seemed even higher then underneath IE5.Zero on a Win98 machine. 2. Allow lisa service utilized by KDE-2.1.1 to allow Community Neighborhood type SMB host/share searching.This can be a system startup degree service (just like sshd/httpd/inetd), and a daily desktop consumer wouldn't have a clue about how this must be put in/enabled. On a facet note - lisas' documentation below KDE-2.1.1 sucks. I had to go to the sources to figure out what needs to be performed to make it work. What bothers me, is that an trade chief like RedHat has missed these apparent (for my part) enhancements in their newest child - RedHat 7.1. After utilizing KDE-2.1.1 on my residence-rolled RH6.2 set up, the experience with RH7.1 was disappointing even after enabling anti-aliasing.I could also be paranoid, but it seems like RedHat just isn't giving all the attention KDE deserves. Fonts are a problem for Open supply software program. There simply aren't very many actually high-quality TrueType fonts on the market which have the proper licences. MS, in fact, has the most effective fonts, however you cannot just begin redistributing their Home windows fonts - that's a violation of their license. One factor that can be executed is you can download MS's freely accessible internet font bundle. Nonetheless, you can't embody it in a Linux distribution, because you can't redistribute the fonts.Someone needs to go out and make some high-high quality TrueType fonts and make them available to all of the world! I've had zero luck. I consider that KDE 2.2 will comprise a totally new SMB implementation (based mostly on a new SAMBA library) that can lastly embody correct SMB share looking with no configuration. Yay! The distro you describe in your final paragraph sounds an awful lot like Mandrake. Mandrake was started to add KDE to RedHat again earlier than KDE was in RedHat. Right now its practically a whole new distribution (still largely binary compatible with RedHat although). Mandrake has a default KDE desktop, straightforward graphical install, straightforward graphical system admin instruments, ReiserFS, grub, and more!All the things works great though, and you may simply ignore the ugly icons and GTK widgets. In case you have issues configuring lisa, contact me. Subsequent week I will spent some time on improving the state of affairs. I can't use lisa as a result of it uses portscanning and thats illegal right here(campus network). How does what lisa does examine with what Windows does for seeing who's on the network? I only know slightly about how Windows does it and even much less about lisa.Oh, and i have not gotten lisa to work on my machine, however I had not put that much effort into it yet. I feel I've figured out a part of the problem. Am I proper that so as to browse SMB shares, you must configure lisa to use nmblookup? I simply have the IP addres vary mistaken? Well, on a stock Debian system, the default is for under root to be able to run nmblookup. That may explain why nothing is showing up in lan:/ aside from localhost. I'll need to look into altering that.BTW, the documentation and configuration for lisa positively needs to be improved. Initially, going to smb:/ should not deliver up an error dialog! If what the person really needs in this case is to go to lan:/, they needs to be routinely redirected, not given an error! You may most likely deduce the right network settings (broadcast address, and many others for the commonest usage case) robotically 99% of the time without even asking the user to set it up. This wants work. For the opposite 1%, you should have extra helpful help textual content. The allow you to get from the "help" button reads one thing like: "For extra data, look in the README file. To read the complete handbook, click here." To start with, you are giving contradictory recommendation here (I do know it is most likely because of some kcontrol assist template, but it needs to be fixed anyway!).Second, clicking "right here" has no impact, as a result of there isn't a hyperlink there! Third, this does not assist the user Find the README file (out of the a whole bunch on the computer), and it is not obvious the place it is. I needed to run a search on my whole /usr listing to find it. Fourth, when you do find the README file, it's of NO assist if you don't already know so much about networking. The README explains quite a bit about how lisa works, but it does not let you know basic utilization information like how to find out what IP ranges are acceptable on your specific network.It seems fairly simple to configure lisa in a way that might either create lots of redundant community site visitors or start ringing sysadmin pagers because they think they're being portscanned or one thing. Sorry to rant, however lisa is just means too laborious to configure and use. With Home windows, you simply plug it in and it works (for 99% of the cases. I sit up for the improvements you plan to make. BTW, won't the KDE 2.2 smb ioslave be capable to browse accessible SMB shares in a community-neighborhood approach?In that case, what can be the purpose of lisa? Oops, I was incorrect about nmblookup. Apparently there's another cause that lisa will not use nmblookup. I have the "use nmblookup" field checked, however lisa won't list any SMB shares (or anything, for that matter). I do know I don't have the IP addresses set accurately, but should not lisa record the SMB shares utilizing nmblookup anyway? And how the heck DO you set the IP addresses accurately? I agree that the documentation for LISa isnt very helpfull to newby consumer.Has anybody had any success with this? If that's the case may you publish something that would clear up all of this newby confusion? I can see one simple improvement to the LISa configuration in KDE. It mustn't want one. Give it some thought, whenever you arrange a linux box for networking, you specify which network the field is related to. KDE LISa configuration instrument then asks you to specify which community you want to browse. For most people, it's the same community that they have set their field up for.It appears that evidently LISa configuration is confusing and redundant. When I used to be establishing LISa, I ended up giving it all the identical data that may be extracted by way of `ifconfig -a` command. Possibly LISa configuration will be simplified by extracting the default settings from the results of the `ifconfig -a` command, as an alternative of defaulting to 192.168.0.0/255.255.0.0 community settings? In any case, right here is how I received LISa working. I added the following commands to /and so on/rc.d/rc.native file on my RH6.2 box.LISa may be configured to use nmblookup, which is part of the SAMBA package, so be sure that you have it installed in case you configure LISa to make use of nmblookup. RH 7.1 ang this was the first time i have setup LISa btw is it attainable to mount the drives/directories utilizing LISa? For those who suppose that RedHat is not integrating KDE effectively you may try a distinct distribution. SuSE integrates KDE fairly nicely in their 7.1 distribution and that i had no issues with Mandrake either (haven't tested the most recent 8.0, though). Excuse me, however are you reviewing the same Mandrake 7.2 that I am?Mandrake 7.2 was the buggiest distribution that I've ever used. Adding a menu item by not utilizing the editor, but moderately by adding the .desktop entry? Installing anything however the default inst? Re-working the X configurator? I used Mandrake 7.2, but I didn't do any of the things that you mentioned. I installed the usual, everything labored right away and i installed additional program by hand (but not from the distro). I have been operating SuSE 7.1 for the final month and had no issues in any way. Perhaps my hardware makes it straightforward (I bought a VA Linux machine), however I've had little issues with both distribution.And the configuration tools in SuSE 7.1 are superb. I really have not tried SuSE myself, so I wouldn't know. I've heard YaST is sweet, and i keep which means to check it out. Sadly Mandrake has adopted the Debian menu system to sync totally different desktops. The idea is that your menus will probably be the identical under KDE, GNOME, WM, black box or whatever. What I find strange about that is loading these other desktops the menuing is Not really the identical on some. Anyway, I assist variety but don't have any time to play with other desktops and KDE works great!For those who write desktop information to /usr/share/applnk since mdk 7.1 the update-menus program will delete them. What I did was erase update-menus and /and many others/menu-strategies/kde. I built KDE from cvs in /choose/kde2. I now have each. As to mdk 7.2 being buggy, the early launch to get into Wallmart didn't assist things. The re-release is fairly strong. BTW I at all times do an professional install with plenty of customizaton. Re-release. Hadn't heard about that, appears like a decidedly MS type tactic.I might have anticipated Mandrake to not less than change the version quantity so it's prospects would know! Although the nice thing about how the Debian packages of KDE are arrange is that they use normal KDE menus for every part, then the shared Debian menu is a submenu off of the principle "Okay" menu. So, I've the comfort of getting the KDE organization and likewise the identical menu construction if I were to go to blackbox or something else. TT fonts take an individual about 6 month to make a full set of latin only characters, there are virtually no free TT fonts that you possibly can embrace in a linux distribution.There was speak throughout GUAEC II about getting a few of the large firms that back GNOME to contribute some cash in direction of fonts. Fonts are an X thing so KDE can use those fonts as well. So far as I do know such tools are part of Mandrake Linux. I do not know although how easy it would be to include them with other distributions. I've really received a configuration program that relies on KDE in early planning stages at SF. How are you planning to do this? I had given some thought to this myself.For many implementations of Linux/Unix, the uncooked information needed to configure a 'characteristic' is portable across platforms. For example, the network config wants interface names, and the interfaces need an IP tackle, network mask, broadcast deal with, and optional extras like MTU sizes are usually frequent too. The identical goes for network routes, NFS, NTP, basic user accounts, groups, Mail setup, aliases, and many others, and so forth. So to offer probably the most use, a GUI front end could be an information collector for all this sort of raw data, perhaps populating a easy database that callable standalone scripts or programs might query to do the actual config work.A aspect benefit of taking this approach could be that somebody may write a char-cell entrance finish to the identical database and scripts in the event that they needed to do system management over remote dial-up, or on headless systems. The actual heart of a tool like this can be the data repository and the API used to populate it and read from it. Writing the human interfaces could be something to do later and should be platform/toolkit agnostic. Re: System Administration instruments. I definetly agree. Considered one of the most important issues with MacOS and Home windows is that the GUI is just too tightly certain to the kernel. Since KDE have to be seperated from the kernel by X anyways, providing a entrance-end is the right solution.As others pointed out, it could contain much work for supporting the multitude of distributions. However I believe it is still a good idea. What KDE can do is present a uniform modular front-end interface for configuring different things. Then it could be up to the distribution maintainer to do the distribution-particular work within the again-end. For instance the interface within the control middle would offer the choice to set community parameters. By pressing apply, a script is executed with all the parameters obtainable. The script must be written by the distribution maintainer.Everyone should be pleased: - Customers have a normal interface on all distros. KDE staff doesn't must cope with each distro. Distro providers have a straightforward to use, intergrated configuration interface. Good idea! I was really interested by the difficulty of distro-specific config tools and especially how might KDE ensure (enforce?) a predictable and constant person experience while letting the distro distributors distinguish themselves from others? KDE Management Centre. For newbies and other non-Linux folks, it doesn't make any sense at all.MSWindows or MacOS in UI comparisons. So are you pondering a a unique thumbnail/pane within the Management Centre to perform distro-specific chores? Or are you pondering of blending those with the remainder? I believe this must be severely regarded into. GUI apps are written. UI from the performance. I haven't regarded intently at it, however I belive the backend are written in python and it makes use of xml as "registry". I wonder if a kde front end would be doable? I don't know if the tools introduce to many dependcies to the GNOME libriries, however it may very well be worth testing.This might be an important oppurtunity for co-operation between the 2 camps. Like the title says: are there any KDE developpers studying this? Folks like David Faure, these Mosfet or Jono guys, like, one of the "KDE Heavies"? This is necessary stuff! I run KDE on a Linux system, and on a FreeBSD system. Is that basically honest? KDE has been doing a fairly good job, although. I believe Linux users should first study now to configure their desktop by hand and not through the use of config Instruments. GhostScript 7.00,gotta look if KDE's printing system will solve that one out. Linux. The entire OS-specific stuff ought to be isolated in an appropriate bundle, like kdelinux, kdebsd, kdesolaris, and many others. What good would all these things do beneath FreeBSD or IRIX?Try easyLinux, it has all of the bells and whistles to offer these easy configuratuion tools. Ximian is creating some setup instruments. The backend and the frontend are separate packages. How exhausting might it be to put in writing a KDE frontend? I think it isn't simple to say which one is healthier, GNOME or KDE. It is just that I personally really feel extra confident to make use of KDE, just because it makes use of a lot better underlying GUI library (QT).IMHO. GTK on the other hand tries to be OO, however is seems to be to me nothing greater than C-ish hack for the OO. I don't need to discuss the look, or copy-paste options, since they are half of personal preferences. KDE simply has higher GUI library and this is an efficient cause to use KDE for me. Watch out not to take Object Oriented languages for Object Orientation. IS Object Oriented, but it's written in a programming language (C) that does not help OOP. C and the coding style looks like C, however it's fully object oriented in every definition of it.A button is a button, irrespective of in what language/toolkit you write it. I was not conscious you would do OOP in C. How does one do inheritance? Public vs non-public access? What about virtual features? If the programmer has to maintain monitor of it, I'd consider it a hack. There's nothing improper with C, most realy big, system intensive initiatives are written with C, look in any respect UNIX kernels, or big clustering techniques, or a GUI like photon. OO language like object pascal(good language for big initiatives).I never mentioned there was one thing flawed with C. I use it myself. OS kernels are particular programms which must be optimized for pace as much as doable. You'll be able to all the time write a big application in C (you can even do it in assembler, trust me), but it surely is easier to use an OO language. If you do not consider me, go to the closest software program firm and ask them what language are they writing their applications in.And i by no means said that I don't trust C, so please read my postings rigorously before blaming me for some stupidity I never claimed. I by no means mentioned there was something unsuitable with C. I use it myself. OS kernels are special programms which have to be optimized for velocity as much as potential. You'll be able to all the time write a big software in C (you may even do it in assembler, belief me), however it is easier to make use of an OO language. If you don't believe me, go to the nearest software program firm and ask them what language are they writing their functions in.And i never mentioned that I do not belief C, so please read my postings carefully before blaming me for some stupidity I never claimed. Object System can do that each one. 2.Zero can even do interfaces like in Java. OO. It will probably do inheritance, digital functions, public/private members, sort checking, bla bla bla. And about inherit two totally different buildings: Object Pascal/Delphi cannot try this both, but dispite that it's nonetheless an excellent language utilized by many individuals and firms. Most newer OO languages do not assist a number of inheritance as a result of it's thought-about a design flaw. OO would make issues more difficult to do and perceive. I am speaking concerning the definition of Object Orientation!The one true language is assembler. Each other one is just only a hack ( compiler does it for you ). Alerts/slots neither environment friendly nor sort safe, has no low-degree graphics layer. It's moderately a Windows toolkit ported to X11 ( and Gtk is X11 toolkit ported to Windows ). It's not developed by open-supply community - Sun and HP won't ever need to grow to be dependent on the opposite company - so they never put QT/KDE on ther Unices as a default desktop.I would not say Qt is just too expensive. 1500 with out batting an eye. It's a quality toolkit, and nothing even comes shut for crossplatform Home windows/X11 programming. Whereas Gtk has a hackjob win32 port, Qt has worked under Windows for as long as I can remember, and it is stable. Qt is skilled, and is the type of toolkit that people pay for. Trolltech must be doing fairly nicely too. They show no sign of slowdown.I do not see why Solar and HP wouldn't be excited by Qt. There are numerous large companies utilizing it. And it is very common for firms to be dependent on other corporations. Btw was "a Windows toolkit ported to X11" a determine of speech? I assumed the unique historical past of Qt is it began on X11. Lastly, I must say that KDE's success is basically attributable to Qt. The GNOME people may have Eazel creating purposes, but the KDE people have Trolltech making their base toolkit.This is far more beneficial, and it is this stable foundation that has made KDE improvement so clean. Also, Trolltech would not exist for KDE. They have an agenda of their own for supporting their paying customers. And KDE reaps the benefits. What if I write easy purposes for inner use in my firm - I have to purchase a commercial Qt license for every office. US/Western firms might affort to do this, however different most likely not.No, you don't should. You just have to stay GPL license to it and you might be off the hook. You may not make any money from it, however because it was an utility for inner use, you probably don't thoughts. Btw, Sun and HP have completely no downside paying money for GUI toolkit. They used and still use Motif and that wasn't free both. NT-to-Unix GUI port library as an alternative of Qt was an idiot manager on our aspect.HP appreciated the concept of Qt extra. Motif is an open standard, and Qt is owned by a single ( small ) firm. What is going to they do if Gates with friends buy TrollTech ? Jon already answered the second part. Properly, Motif wasn't at all times an open commonplace. You had to pay, if you happen to wanted to make use of it (that is why it by no means grow to be standard in Linux). As I've stated before, corporations together with Solar and HP never had downside with that.What if I write easy purposes for internal use in my agency - I have to purchase a business Qt license for each office. US/Western companies might affort to do this, however other most likely not. I assumed the business license payment solely applied to industrial growth, not industrial run-time. Qt run-time is free everywhere is not it? After all, I meant 'coder's workplace'. As was mentioned in earlier posts, if it is internal stuff that you are not reselling or something, you possibly can simply use GPL on it! No costs at all. 2.0, with interfaces like in Java. Just what exactly is your definition of "hack"? Does low-degree code work worse than excessive-degree code?I do not assume so: meeting works fine. OO. No, do not reply yet. Take a look on the source code or ask the mailing list first, before making any prejudgements. Just to be truthful, GNOME 1.4 is sort of a stepping stone to GNOME 2.0, the difference between the 2 is musch like KDE 1.x and KDE 2.x. GNOME 1.Four consists of alot of 1.Zero stuff that has not realy matured like Bonobo(Component Model), Natilus (MS-explorer clone), GNOME-VFS(like KIO-slaves) and extra. I might recomend GNOME 1.2 or KDE to non-builders. What is included with KDE 2.x simply to assist developers write for KDE 3.x? So very, very true. ZDNet has periodically presented misinformation.Almost each article that's OSS associated by them contains quite a few errors, and is responded to mostly by individuals saying "Linux sucks, (Mac / Home windows / DOS / WebTV / Microwavable Popcorn) does not, so there!". ZDNet is funded by Microsoft advertisements. They may as nicely be a subsidiary. I've learn the article, and IMHO makes some good, if previous, factors. Bother is, a lot of these 'drawbacks' are questions of interoperability among desktop environments --like drag'n drop and copy'n paste-- and even worse, of the very inside group of Linux and thus, in good religion, lie outside the scope of the KDE challenge. Nevertheless, I want to see them solved. KDE folks for the Best of the perfect among ANY desktop surroundings I've ever seen in all points.KDE is stable, efficient, and stunning. Nonetheless, it's important to note that KDE 2.1.1 has had the benefit of two bug-fixing updates since its major 2.Zero replace;we expect GNOME to make substantial good points between now and its personal 2.0 release, slated for the tip of this year. Does this make sense to anyone else? Gnome has had several bug-repair updates since its final main launch - if anything, it's had three or 4 occasions as lengthy to settle down for the reason that x.Zero release. And on condition that even GTK 2.0 is not finished, and even firmed up (appropriate me if I am fallacious), Gnome 2.Zero is properly on the horizon. Anyway, who cares? It seems to me the only related (or at the least answerable) query is how they compare right this moment.Re: How to compare? You are proper. By the time Gnome 2.Zero comes out there will be KDE 2.3.1 (or one thing like that). They at all times forget that within the critiques and make it sound like KDE will endure no improvement till then. Re: How to check? When reading a overview like this you may have to understand that little of what they are saying goes to be solely factual and reasoned. The intention behind the statement is not unhealthy; so it's not likely worth mentioning. They simply want to state that GNOME has potential.It could be imply to discredit GNOME fully. I might prefer to say kudos to the folks at Microsoft for as soon as again having the better technolodgy. You have got worked very laborious in your desktop and I am enjoying it very a lot, I'm using IE on windows proper now, and having no problems with lower-and-paste or bizarre inconsistices. Observe to the writers: You had barely any cover of windows, all you said was that it was better, the whole article itself was kind of fluffy and appeared sort of UNIX centric.I completely agree. In spite of everything, what likelihood have they against person-friendly options like useful MS Office registration screens (complete with a service to send the consumer helpful information from our associates), and context primarily based speaking paperclips. BTW, if you cannot tell, both this text and the article I'm replying to are very much finished tongue-in-cheek. I agree that at this second Microsoft has a greater desktop atmosphere. However I believe that Alernative OSes are fast catching up. OS X, is on its heels, KDE 2.1.1 isn't too far behind.GNOME is an excellent setting nevertheless it seems to be considerably barely less professional to KDE in the intervening time. I am wanting forward to GNOME 2.Zero If Windows is your kettle of fish. Superb. Others relatively work with options. It is never correct for one company to have a digital monopoly in any area. Competitors is Rattling GOOD. GO KDE Team!! All u rough. Sustain the good work. In case you did not notice, the whole article was about Unix desktops.By the best way, seen any blue screens these days? Hiya I use the newest kde desktop (211) and i believe it is the best, but would not say it isn't good enough. I would say it is not good in any respect. The not-pace of kde is driving me nuts, and then all purposes, as it is common in linux, crash most of the time. I say I'm a linux fan and i hate home windows, however no one ought to actually say linux is best than windows. Linux will get more and more like windows. The brand new kernel is unstable, the kde 2.Zero (so known as release model) was more then unstable.And nearly each softwareproduct for linux (count on tex and emacs) that is known as release is for my part early beta. slots online para celular brasil is actually strange. I am utilizing a 2.4 Kernel, XFree 4.01 and a KDE 2.2 Alpha (!) that I downloaded from CVS 2 days in the past. Noting crashes. However I've compiled my complete system from floor, perhaps that is the rationale it really works so properly. Just a few days in the past I tried to put in SuSE 7.1 -- a nightmare. That might the actual drawback of Linux: We're struggling with totally different file programs, generally completety incompatible libraries (RedHat), buggy distros (did not Mandrake ship a Beta-Version of KDE within the US last chistmas?) and mega distros which have 1000's of packages that no one ever makes use of -- amount as a substitute of quality.You should have a have a look at the essential distros: Linuxfromscratch, Slackware, Debian. They have the standard you are in search of. 2.96-RH generates 100% suitable code for C packages. C program with it and use in any system suitable with glibc-2.2. 1.1.2, gcc 2.95, gcc-2.96-RH and gcc-3.Zero (cvs department). 7.1 until now (you). KDE beta. their 7.2 launch comes with 2.0-last, however they did make just a few bins with kde 2.0-rc (not beta, release candidate) for wall-mart.2.96-RH generates 100% suitable code. RH7 is buggy. you can't even compile your individual kernel with it. SuSE 7.1 goes, i not too long ago put in it. 640x480 mode. nothing else would work. 2. nope. clean display. 2fsck. when my system recovered from that, i ran sax1 and it autodetected my graphics card (s3 virge/DX. 2 work when the graphical set up did? why cannot you choose your monitor in the course of the set up to abvoid all these publish-set up configuration problems? why did my computer crash at the tip of an attempted install? SuSE is an effective distro, however they should take some pointers from corel with out sacrificing any flexibility. 2.96-RH generates 100% suitable code.RH7 is buggy. you cannot even compile your individual kernel with it. SuSE 7.1 goes, i lately installed it. 640x480 mode. nothing else would work. 2. nope. blank screen. 2fsck. when my system recovered from that, i ran sax1 and it autodetected my graphics card (s3 virge/DX. 2 work when the graphical install did? why can't you choose your monitor during the set up to abvoid all these put up-set up configuration issues? why did my pc crash at the end of an tried set up? SuSE is a good distro, but they need to take some pointers from corel without sacrificing any flexibility.2.96-RH generates 100% compatible code. RH7 is buggy. you cannot even compile your own kernel with it. SuSE 7.1 goes, i not too long ago installed it. 640x480 mode. nothing else would work. 2. nope. clean display screen. 2fsck. when my system recovered from that, i ran sax1 and it autodetected my graphics card (s3 virge/DX. 2 work when the graphical install did? why can't you select your monitor throughout the install to abvoid all these put up-install configuration problems? why did my computer crash at the end of an tried install? SuSE is an effective distro, but they should take some pointers from corel with out sacrificing any flexibility.I am a sysadmin for a large ISP and I exploit Linux alone in my notebook. There's not a single activity that I have to get achieved for which I am unable to find a superb and stable Linux app to do the job. I take advantage of Mandrake 7.2, kernel 2.2.19, and KDE 2.1.1 and I don't even remember when my system final crashed, it simply would not happen although I take advantage of it fairly closely with several apps working all the time. If your Linux/KDE is crashing so often, there's actually something flawed together with your installation.What do you mean by saying that kernel is unstable? I have been utilizing Linux with 2.2.x kernel for four years and by no means skilled a kernel crash! I mean, even X server crashed few occasions, but Linux kernel was still running. I do not know how is the state of affairs with 2.4.x kernels, however I believe it cannot be worse than 2.2.x. Some unfinished KDE functions (like the KOffice ones) have been crashing, but no person mentioned that they have been launch variations, they are still developed.I do agree with you though, that KDE 2.0 was a bit too buggy for a release version, however hey, that's why they equipped KDE 2.0.1 so soon as a bugfix. Though I recognize the work of people that work on KDE very much, I might suggest that when KDE x.0 is released, it may be even few months late (prefer it was a case with 2.Four kernel). It is nothing worse in software development than attempting to release variations of software precisely on time, as a result of it might cover far more hidden bugs because of all of the hurry to launch on time. In any manner, KDE is admittedly great desktop and everybody who is saying that KDE individuals did not do an exquisite job, ought to use Windoze for the rest of his(her) life.I utterly agree with you. Specifically along with your final sentence. KDE applications crash generally, that is true. But its completely ok, you'll be able to restart them and proceed. Of course, as soon as KOffice starts doing that, I'd be more pissed, so they better make it stable (and/or) do this auto-saving stuff ms has tried to use for covering up their sloppy programming. However the 2.4 kernel is indeed a bit of unstable, even Linus & Alan confirmed that.2.4.0 kernel crashed on me once. 2.4 since 2.3.35 (or so) and the only drawback i had the last 1 or 2 years is that my new cd-burner does not run and block my linux. I'm additionally utilizing kde-2.1.1 since 2.0 beta1 and it received very stable to model 2.1.1 Also the java and plugin support in konqueror acquired very wonderful, and the only wish i have is better msoffice help in koffice but that is comin in the next koffice release.However I'm compiling my apps by myself, my slackware is stable but some apps are slower than selfcompiled (for instance kde). Hey! My linux kernel also will get stopped when my CD reades has issues with some CD's. When this example arrives I am unable to umount /dec/cdrom. This is basically a giant downside and havn't discovered how to resolve this. Hello, what planet are you from? Complaining about something and all the pieces is a troll. If you don't like it, but haven't got something useful to say, then go join a home windows dialogue group. 1534: If it looks like every little thing is crashing, then one thing is misconfigured. KDE is currently at 2.1.1 release, not 2.0. Complaing about 2.0 will not be solely pointless, it is laughable.366: If you happen to discover a bug, report it, with a selected example. Don't make imprecise comments about "crashing". Wow, that is fairly a sweeping comment there. Now not only is KDE and Linux at fault, however now it is virtually every OSS product (besides tex and emacs) that is at fault? 1534: If it looks as if every thing is crashing, then something is misconfigured. Oh yeah? I had KDE crashing all the time last year.My file system was getting corrupted and KDE would not even compile with out taking down my system. Know what the problem was? Unhealthy RAM! That's right! I tested 36 bytes on certainly one of my 128 MB DIMMs choking badly. Frankly I am extremely dissapointed that KDE, the kernel and different OSS software program could not operate appropriately with defective hardware! In fact if I had been operating windoze I would not have seen something unusual since I expect it to crash. Since I haven't gotten a response on my dangerous RAM bug report I'm beginning to suspect that, as I do not run winblows, OSS software program will need to have broke it! Clearly this proves that KDE will not be only buggy but harmful.To the rational empirical evaluations yield results. To the rest the revelations of trigger and impact are just one other conspiracy idea and illusion is extra substantial than proof. To the rational empirical evaluations yield outcomes. To the remainder the revelations of cause and effect are just another conspiracy concept and illusion is extra substantial than proof. Effectively mentioned. Is that a quote from someplace? Hi! I know i ought to do some extra detailed failure descriptions, but maybe you might be only taking part in with your linux field.And the principle factor I wished to say is that the linux-community ought to realy cease to release every buggy extension to the kernel as so referred to as launch. And what ought to be relly accomplished is a few critical testing. Testing is one of the crucial importand components of software program engeniering. You'll be able to go on an play with each little kernel quirk and recompile all your apps. But I've received some work to be done.You fully missed my point. Right here, I am going to make it easy : what you might be doing is trolling. Trolling is a waste of bandwidth, completely unhelpful, and very annoying. You are trolling as a result of you're doing this : complaining endlessly in a completely unhelpful manner. You seem to have nothing to say but "Haha, I am better you then, trigger my software is stabler then yours, so there". Furthermore, I do not recompile all my apps commonly, and i don't play with every little kernel 'quirk'. Neither do the individuals who run Linux boxen and serven on a manufacturing stage basis. If you have no time to waste, and need to get to work, then please, by all means, get to it! How do I get my floppy back? Where did my other mouse buttons go?