Ditto! You did not describe the layout completely. If you are serving people in one school building and giving them shared access to the WWW, you do not need naywhere near that CPU power. Increase your bandwidth by loading up the motherboard with fast NICs to a good switch and you will make everyone happy. Spend lots on the WWW access. The only way you will need lots of CPU power is if you are running thin clients so everyone can use cheap terminals sucking on ahot server.
How many are going to be connected at once? How many from inside the building and how many from the WWW? If you are going to have many simultaneous sonnections, perhaps you need more RAM. You can get a dual processor board that can hold four sticks of 1 gB DDR 266 from TYAN, but it is pricey. One advantage is that you can use a gigabit NIC in copper in a 64 bit PCI slot and fan out to the building with a 24 X 10/100 switch to please a bunch locally.
Don't forget to use a cacheing name server to save bandwidth when folks go to find the IP address of yahoo.com for the 10000 time each day (bind). Users will appreciate getting the answer in a few milliseconds instead of the luck of the web. Also cache web content so that your limited bandwidth to the outside is conserved (squid?).
Slashdot Mirror
Ditto!
You did not describe the layout completely. If you are serving people in one school building and giving them shared access to the WWW, you do not need naywhere near that CPU power. Increase your bandwidth by loading up the motherboard with fast NICs to a good switch and you will make everyone happy. Spend lots on the WWW access. The only way you will need lots of CPU power is if you are running thin clients so everyone can use cheap terminals sucking on ahot server.
How many are going to be connected at once? How many from inside the building and how many from the WWW? If you are going to have many simultaneous sonnections, perhaps you need more RAM. You can get a dual processor board that can hold four sticks of 1 gB DDR 266 from TYAN, but it is pricey. One advantage is that you can use a gigabit NIC in copper in a 64 bit PCI slot and fan out to the building with a 24 X 10/100 switch to please a bunch locally.
Don't forget to use a cacheing name server to save bandwidth when folks go to find the IP address of yahoo.com for the 10000 time each day (bind). Users will appreciate getting the answer in a few milliseconds instead of the luck of the web. Also cache web content so that your limited bandwidth to the outside is conserved (squid?).