| Munchkinguy | Lies! Centos 5 does not support i586 |
| cluster-aware | i686 the lowest it goes? |
| action | Munchkinguy shrugs. |
| Munchkinguy | shrugs. I tested it on my AMD K-6 machine and it would not install. |
| Evolution | for now that's correct. |
| Munchkinguy | For now? |
| Evolution | it was the same for centos4. that was an addition we made. upstream does not support k6 or < i586 processors. |
| Munchkinguy | Ok. So what if I install centos 4, download and compile the centos 5 kernel, download centos-release-5, and then upgrade all with yum? |
| Evolution | you'll spend quite a bit of time and frustration to end up with a system that won't work. |
| cluster-aware | Yeah Many of the binary RPMs depend on i686 minimum, I would assume |
| Munchkinguy | :-\ |
| n5red-4 | Not all of my machines are i686 |
| Evolution | yes. they expect certain things to be in place within glibc and other apps. n5red-4: welcome to the 21st century.. please consider upgrading to something made in the last 10 years. :-P |
| n5red-4 | My Soekris net4801 was made in the last few years It's an AMD Geode. |
| Munchkinguy | I guess I'll stick with 4.4, then |
| n5red-4 | I'm not sure if my mini-ITX system is a full i686. 1GHz Via processor |
| Munchkinguy | (plus the RHEL artwork, 'cause its pretty) |
| lexton | I'm installing yum on centos 4.4, and I'm looking for the centos-yumconf-4-4.3.noarch.rpm is this still needed for yum or should I install another rpm? yum utils? |
| ZBandit | is it the 9th yet? |
| cluster-aware | Yep |
| FireCat | Anyone know that when you start eclipse on CentOS5 Betsa the Splash screen comes up with Eclipse - Red hat Edition? ... not that I care mind you |
| ZBandit | perhaps that's why it's still beta? there are still 2 days (or so) to fix it. :) |
| FireCat | rofl |
| cosmic665 | can someone provide me with a nice comprehensive list of preferred yum repos? which ones do I defainately need to avoid? |
| cluster-aware | Stick with the default - you;ll be fine |
| D-side | i might not have tried that explicitly. lets see. |
| cluster-aware | Cripes, you could be looking at local overhead (CPU, mem, etc.), fragmentation, rate-limiting (802.3x or TCP flow-control), poor cabling, poor wiring (is the wire bound too tightly with wire-wraps or strung over a flourescent ballast?), poor performance on the host.... Dozens of things I agree - your host, assuming they guarantee any sort of SLA should be able to assist sysctl tuning isn't out of question, but may be a red herring |