Quote:
Originally Posted by TheEvilOne6620
testing and trying out as many other distros as possible.
|
Why?
Most of the important differences (especially among all the Debian based distributions) only matter to a beginner. Once you have some experience you can add and remove packages and edit startup scripts etc. and customize
any detail the way you want, rather than try to find the distribution that most closely fits.
Quote:
Just wondering if anyone can help me in figuring out what distro to end up with in the long run. Since I am fairly well versed in Ubuntu/Debian based distros this is were Im most comfortable.
|
If the point is to use Linux, that's your answer. (If you wanted to get a job as a Linux admin, you should learn Centos as well and maybe even one of the harder distributions).
Quote:
However, I have read that using distros like Gentoo give you the most performance as they are built around your system itself upon installation. Is this true
|
It isn't significantly true. In 64 bit it is even less true (I don't see any mention of 32 bit vs. 64 bit in this thread).
In any distribution, you can carefully tune which packages are installed and which services are activated in order to trim your use of disk space and ram. I don't know specifics of Gentoo, but a distribution that makes or even encourages you to look at each of those decisions would be more likely to get you to a better trimmed system. But with modern hardware the difference in ram use is trivial and the difference in disk space even more trivial.
In 32 bit mode, any distribution which forces (or even encourages) you to build from source may get you to select compiler options that are better tuned for your specific CPU. This may result in a small improvement in execution speed. But do you run anything that is CPU bound? Or is your cpu almost always waiting for you or for the network or for the disk? In 32 bit mode, if you use some specific cpu bound program a lot (re compress videos or some such task) maybe you want to investigate some cpu and compiler issues enough that you could rebuild
that specific program from source with better compiler switches for improved performance. Anyway, try that first with
some cpu bound program before even considering a distribution that makes you build everything from source.
In 64 bit mode there is less variation in the nature of optimized code by cpu model so there is no significant performance advantage available from compiler switches tuned to your specific cpu model.
Quote:
why is it that other distros like Ubuntu dont do this???
|
Because it would be a lot of extra work for the user for little or no benefit.
Quote:
what are pros and cons of both RPM and DEB based distros?
|
DEB has a much bigger pool of available software. Beyond that difference, I don't know any answers that could be considered facts rather than opinions.
I use both (RPM with Centos, and DEB with Mepis).
I find the GUI package management is Centos so lame that I gave up trying to use it even though I fundamentally prefer GUI to command line. So I use command line Yum in Centos but GUI Synaptic in Mepis. I find the apt command line tools much less effective than Yum, so lacking the GUI in a Debian distribution would be more of a problem than in Centos.
RPM packages available in Mepis 8 are almost always current enough to simply use them. DEB packages in Centos 5.3 are often based on source code so old that the only reasonable choice is too ignore the package and rebuild from source. But maybe comparing Mepis to Centos that way is unfair and I should compare Mepis to Fedora. But I never used Fedora.
In 64 bit Mepis it is practical but awkward to get and install the DEB file for the 32 bit version of some package. In 64 bit Centos, it is much easier to decide you prefer the 32 bit version of some package instead of or in addition to the 64 bit version and get it correctly installed. That is a fundamental Debian vs. Red Hat difference (not just Mepis vs. Centos).
There are more complicated (and cutting both ways) differences in multi lib (mixed 64 and 32 bit system) in rebuilding packages from source.