Ok, first off, are you using this for just a desktop? If that's the case, you really don't need to compile everything for your computer. While there will be a bit of a preformance hit, it really won't be too large, and almost negligible when compared to the processing speeds of modern computers. For the most part nowdays, you will only really need to compile something if: your distribution doesn't support it and there's no RPM/DEB files for it, there are some kernel modules which you need but aren't in your distribution's source tree, you want to try to eke out the most preformance possible, or you need to dsable some features for security reasons.Hi, I'm relatively new to using Linux on a daily basis and I was looking for some information about what the "trends" are for production Linux machines. I installed RedHat 9, and have mucked about with rpm and thought that packages were the greatest thing since sliced bread. However, in the course of my reading and playing I've noticed that many places recommend that the binary executables actually be compiled by your machine (with all its kernel options, etc.) which is sensible. Everything is well when I ./configure them and then "make install" but if there is an update to a particular product it seems very inconvenient to upgrade versions. An example is the Apache httpd server - 1.3.xx stores its served files in /var/www/html/ and the actual httpd daemon in /usr/bin. Apache 2, however, sets the DocumentRoot as /usr/local/apache2/htdocs/ and the binaries in /usr/local/apache2/bin/. I know it's just a simple matter of changing the DocumentRoot entry in the httpd.conf file for served documents but is there a better/easier way to go about upgrading the binaries? Or is the de facto standard to simply run ./configure --with-prefix=/usr/bin? Any advice would be appreciated. Thanks,
-Phil
My suggestion would be to just be lazy and let the package manager deal with the big stuff that can be a total pain (like X, KDE, or GNOME), and just compile the little things that you need to customize your system (i.e. the version of Xine with lib-decss support built in :). Granted you won't be at the bleeding edge of things, but that's never stable, and if this is your desktop or production system you can easily loose data (I've had this happen, and it really sucks). Keep your system up to date with whatever update tool Redhat provides (I can't remember, I use SuSE).
Nathan
-- "Man mu� nicht gro� sein, um gro� zu sein." http://www.claytondevelopment.com
- To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
