1) RPM/SRPMs are a huge headache sometimes, solve this solve that. I almost feel like I am back in Calculus in college. 2) Being able to divert easily from the main portage tree is a huge benefit when your Gentoo machines are production servers and you need to insure the stability of your packages and builds (example, apache, mysql, php, postfix, openssh, openssl packages). Also diverting from the main portage tree and creating your own ebuilds on production servers that are internet accessible is very handy in making those packages I listed earlier more secure and trust worthy because you can get the official source from the distributor yourself. 3) Gentoo has a very lively crowd when it comes to documentation, howtos, faqs, and bug listings. Their forums and gentoo-wiki.org are goldmines when it comes to setting something up quickly and there are plenty of diverse topics on systems administration out there so 10 day installs really shouldn't happen unless you have some highly experimental hardware you are working with. 4) You have two options, RTFM or install Windows and click the next button until something works.
I really don't understand how anyone can make an install drag on for 10 days. Upset with poor Redhat management and almost "MS Like" behavior I switched all my systems away from Redhat a while ago, during the 2004 season of Gentoo releases. I recently setup a dedicated Linux server for a client I work with and installed Gentoo Linux (starting with a stage1 tar file) over a running Redhat RHEL4 install using documentation I found on their website and their Wiki-site. It didn't take 10 days and amazing enough I didn't brick a server located in several states away from me.
The main reason I like Gentoo is because of their minimalist and simple approach to package management. Although RPM install faster I think the portage/emerge system is less of a headache and with an auto dependency solver built in it puts installing packages on ez-mode for any system administrator both novice and experienced.
Slashdot Mirror
Replies:
1) RPM/SRPMs are a huge headache sometimes, solve this solve that. I almost feel like I am back in Calculus in college.
2) Being able to divert easily from the main portage tree is a huge benefit when your Gentoo machines are production servers and you need to insure the stability of your packages and builds (example, apache, mysql, php, postfix, openssh, openssl packages). Also diverting from the main portage tree and creating your own ebuilds on production servers that are internet accessible is very handy in making those packages I listed earlier more secure and trust worthy because you can get the official source from the distributor yourself.
3) Gentoo has a very lively crowd when it comes to documentation, howtos, faqs, and bug listings. Their forums and gentoo-wiki.org are goldmines when it comes to setting something up quickly and there are plenty of diverse topics on systems administration out there so 10 day installs really shouldn't happen unless you have some highly experimental hardware you are working with.
4) You have two options, RTFM or install Windows and click the next button until something works.
I really don't understand how anyone can make an install drag on for 10 days. Upset with poor Redhat management and almost "MS Like" behavior I switched all my systems away from Redhat a while ago, during the 2004 season of Gentoo releases. I recently setup a dedicated Linux server for a client I work with and installed Gentoo Linux (starting with a stage1 tar file) over a running Redhat RHEL4 install using documentation I found on their website and their Wiki-site. It didn't take 10 days and amazing enough I didn't brick a server located in several states away from me.
The main reason I like Gentoo is because of their minimalist and simple approach to package management. Although RPM install faster I think the portage/emerge system is less of a headache and with an auto dependency solver built in it puts installing packages on ez-mode for any system administrator both novice and experienced.