| 1 |
Everyone keeps telling me how brave I am. I have to say, it doesnt seem |
| 2 |
that way to me. Ive got a second drive (exact mirror of the first, same |
| 3 |
size) rsyncing every night (over to another server). That is my current |
| 4 |
backup solution. I havent had to go to it once. Since I set this up as a |
| 5 |
server and started getting these users I havent had a single outage that |
| 6 |
wasnt a problem with power (we had 2 real bad storms over the last month |
| 7 |
that took out power for 5 hours each, my UPS only does 3 hours tops for |
| 8 |
the 3 systems it runs.) Other than that, it has run flawless, and you |
| 9 |
want brave. emerge -up world shows nothing right now. It is as up to |
| 10 |
date as possible without gcc 3.2. Not a single problem. |
| 11 |
|
| 12 |
Gregg |
| 13 |
|
| 14 |
|
| 15 |
|
| 16 |
> On Friday 23 August 2002 04:22, Gregg wrote: |
| 17 |
> |
| 18 |
>> I run a server, it hosts 127 websites. |
| 19 |
> |
| 20 |
> Hope with that domain name that doesn't mean what I think it means... |
| 21 |
> <g> |
| 22 |
> |
| 23 |
>> Has many users for various other |
| 24 |
>> things. It is currently on a celeron 600 overclocked to 675, with 256 |
| 25 |
>> megs of ram. The motherboard supports celeron and pII. It is |
| 26 |
>> beginning to choke. It is time to upgrade the motherboard, cpu and |
| 27 |
>> ram. Since this is an old setup (celeron and old mobo) what do I need |
| 28 |
>> to do when replacing them. Everything is obviously compiled for it. |
| 29 |
>> I have not changed any of my flags in the configuration files. So it |
| 30 |
>> is all just i686 in the c*flags. I want to go up to an athlon 2200. |
| 31 |
>> So, what do I need to consider before switching them out, what do I |
| 32 |
>> need to do afterword . This is a 1.3b_test system with all the latest |
| 33 |
>> updates (except gcc 3.2, I am still on 3.1.1) |
| 34 |
> |
| 35 |
> I agree with some of the other posters. You're being REAL brave running |
| 36 |
> that on a 1.3 beta. On a server, I would have definitely gone with 1.2 |
| 37 |
> (and been a bit sweaty about the palms doing that -- Gentoo's strength |
| 38 |
> is not stability right now.) I hope most of those 127 sites belong to |
| 39 |
> friends of yours that are forgiving about outages. |
| 40 |
> |
| 41 |
> The one recommendation I would make would be to compile your kernel for |
| 42 |
> all the new stuff as well as the old (I'd do it with modules), and if |
| 43 |
> in doubt, make it a module. (You'd have to have support for modules |
| 44 |
> compiled in, of course.) |
| 45 |
> |
| 46 |
> I just had to replace a motherboard myself recently, and there were all |
| 47 |
> kinds of little oddities I had to clean up. Having support for |
| 48 |
> everything in the kernel will minimize your downtime getting the new |
| 49 |
> box up. (I assume you want it up as soon as practical.) |
| 50 |
> |
| 51 |
> One other little tidbit from recent personal experience. Be sure to |
| 52 |
> check things out with hdparm once you get the new motherboard in. My |
| 53 |
> new one had one of my hard drives running at about 4 MB/s. After I |
| 54 |
> turned on the usual stuff, it ran about 40.5 MB/s. Your mileage will |
| 55 |
> almost certainly vary, but it's always worth checking. |
Archives