Slashdot Mirror
SuSE 7.3 vs XP
rutledjw writes: "This should be good for some flame wars. A story on HPWorld that I read about on NewsForge gives an interesting comparison between XP and Linux. I personally think the story wanders a little and wouldn't call it comprehensive, but it is interesting. It does point out a particular bottleneck in how the 2.4.x kernels handle asynchronous IO. Apparently this is being addressed in the 2.5 kernels..." It actually appears quite low-flame and balanced, and unlike some Linux vs. Windows comparisons, goes into decent detail rather than just glib generalizations.
Hi wish I could say something about Suse Linux. So bad they don't have a downlodable version. :-(
I have to agree. Microsoft recommends a machine equipped with at least 800Mhz and 256MB RAM just to run the OS! How in the world can an OS need that much power? Its rediculous and that alone is the reason I will not even try XP.
.NET frameworks. First of all, Visual Studio is a whopping 1.6GB! I can't remember the exact numbers, but NetBeans and other similar IDE's have never needed that much disk space. The IDE consumes at least 128MB of RAM and the IIS web server with the .NET frameworks installed runs at 70MB of RAM.
A little off topic but another product Microsoft makes that takes up a ton of resources is their new Visual Studio.NET and the
http://www.askthevoid.com
SuSe does not seem as polished as redhat or XP and is more buggy on my p700. I had no 3d acceleration for my geforce2 due to some "licensing" reasons. RedHat included the same driver and its free so I wonder what the deal is. Next Gnome was acting strange and was totally unusable. It had a 15 second lag. For example I clicked on home using gnome and had to wait 20 seconds for natulus to open it. Everything else was unbearablly laged. I have no idea what the problem is. I have 320 megs of ram so memory is not the reason. I also had several daemons failed during bootup for some unkown reasons. But what really got my attention was that I could not do kernel compiles without strange things happening and I couldn't get my machine to shutdown properly. I will get to the kernel compile errors in a minute. First, to shut off my system I need to pyhsically unplug it. The off switch will not work. I tried the 2.2 kernels on my system and even without apm support, I could at least hit the power button to shut it down. I tried disabling APM, re-enabling APM with different options and even attempting to recompile the kernel and nothing works. What is weird is that it works fine in failsafe. I fired up vim and changed the default linux entry in /etc/lilo.conf to have the same append arugements as the failsafe option but had no luck. I then even pointed the defualt kernel to the failsafe.SuSE kernel in /boot with the same appends and still no luck. How strange.
/USR/LIB/MODULES* FILES TO DO A SUCESSFULL RECOMPILE?? I know this is dangerous and that it may fuck up my system if its not done properly and is quite extreme. I figured what the hell and did and then did a major recompile. Guess what? Image too big error message popped again! I squirmed and did a "make modules" hoping it would place some of the modules back for a successfull Reboot. That went fine and all the modules were copied. I rebooted my machine and I got the chilling "can not find module "ext3" error. I know I compilied "ext3" as a module and yes it was copied! But for some reason it wasn't being used when I rebooted. My system was hosed yet again. At this point I had no idea what the fuck was happening and a whole day had gone by.
Also I have issues when compiling the kernel in SuSE 7.3. Even with a "make bzImage" I always get a "image too big" error when updating lilo or puting it in a deskette. WHen I rebooted I had a big suprise. My system was HOSED! I couldn't even use my orignal "defualt" kernel. All the modules like the "ext3" were not being executed at startup so I couldn't even read the hard drive. My backup could not save me. I had to do a new 2 hour re-install.
It turned out that the "make modules" command currupted all the system modules! Why didn't the recompile place the modules in a new directory under the kernels version number like the other distro's did? Under Redhat or mandrake the defualt kernel modules are placed in a different directory then the default supplied modules so a "make bzImage" corruption would not occur. I read the manual and it mentioned that you NEED TO DELETE ALL THE
How unbelieable it is to suffer through that all because I want to use the "shutdown now -h" command and have a kernel with apm support. WIth this and all the bugs I found in 7.3 I decided to happily put WIndowsXP and Redhat 7.1 back on. Sure redhat may not have a pretty bootup as SuSE but it is sleek, stable, and feels alot more professional and polished. You may hate the distro but redhat goes through great pains making sure its well tested. THe default kernels even used the better VM patch before linus switched to it in the main kernel series. I use to have great respect for suse but I lost it after my 7.3 install. I am not bashing SuSE and trying to start a flame war but just sharing my unfortunate experience with it. No distro is prefect and SuSE has its own problems.
http://saveie6.com/
Wouldn't the BSD logos be most appropriate for pitchforks?
I think that given another year or two, Linux will start making serious inroads into the workstation market.
LedgerSMB: Open source Accounting/ERP
"RPM's look like they were built by drunk chimpanzees." Just what the heck is that supposed to mean. You don't make no sense.
Don't make no sense == makes sense. (Double negatives)
ie: definition of "don't make no sense: see above" (tongue in cheek, of course).
We all make typos when we're typing as fast as a drunken chimpanzee.