None of the linux drivers seem to take advantage of SMP, as they do in Quake3 under windows NT
I remember you can enable Q3 to be multithreaded in Win32, which is all you need on NT and Win2K to take advantage of SMP. I know a little about threads on Win32 to understand it's not difficult to use them. How easy is it to use threads on Linux?
Driver writers need to understand threads too. Come to think of it I don't even know if there's such a thing as a multithreaded driver.
The cpu and ram may handle it, but remember that on a BX board to go 133 means running the AGP at 87MHz, a speed which has been known to fry some video cards.
Important point.
Have a look at An exploration into overlocked AGP. Of particular note, cards designed and cooled well (like ATI's Rage Fury MAXX) operated without a hitch. They also went overboard overlocking the 440BX to 150 MHz FSB cranking AGP up to 100 MHz.
If you're timid about overlocking, this is a good reason to wait for i815.
RAMBUS is an expensive joke! The i820 can't even keep up with the "old" 440BX based solutions. Have a look at a March 8th article that goes into all the gory details. To quote Mr Pabst: "Rambus seems to be a rather nasty disappointment."
Not everyone will want to overclock a 440BX board to 133 MHz, but since so little hardware is actually overclocked, and even then only by 30%, you stand little chance of ruining anything. Just make sure you use a CPU and SDRAM rated for 133 MHz FSB.
If anything, wait for i815 to come out. This is supposed to be the "real" successor to 440BX.
Dialups have a legitimate use for using direct to MX mailers: switching ISP. No one wants to fuck around reconfiguring their smarthost parameter so it's easier to go direct.
Besides the fact AOL can do whatever the fsck they want with their network since it's their property, so can ISPs running mail servers who don't want to accept SMTP directly from dial-up or end user IPs because of all the spam coming from them, refuse SMTP traffic from them. Have a look at the MAPS DUL Rationale for a better explanation.
About that time, our mail server vendor had just
released a new version of their software, including a fix for the problems ORBS detected. And it was bargain priced - only $1,500 US to upgrade to version 4.0!
Perhaps a little off topic, but I continue to be amazed with how many NT sites get taken by gougeware that can't even protect itself against relay theft. The ISP I used to work for used a free mail system for over three years with very few problems and no relay spam incidents. The filter developed for this (Antirelay) blocked all of ORBS' tests successfully.
If you're an NT site visit the IMS support page above and learn how to secure your mail servers and get off of ORBS.
As for AOL, it wouldn't surprise me that they _asked_ for servers to appear on ORBS. I'm still trying to determine why they asked for two IP proxies to appear in the MAPS DUL. Granted there should only be end user SMTP traffic coming from there and they're not mail servers, but AOL users using POPAUTH to access other mail servers are getting snagged because the POP3 connection comes from a different IP than the SMTP connection. SMTP AUTH still works though.
The various distros of Linux became this popular, not because of marketing or word of mouth or whatever, but because Linux has evolved and can continue to evolve. The other platforms referred to, especially Netware, haven't. You could throw a whole TCP/IP suite on top of Netware and make it look like an Internet server, but it still hasn't changed since Netware 4.x introduced NDS five years ago. Its age is showing.
NT, on the other hand, has also evolved, even if only to overtake competition from Novell and the *ixes. Despite what most of you all think, M$ programmers do not sit on their laurels all day and rake in the dough, but rather they tweak and twiddle with NT constantly trying to improve performance. ISAPI and ASP are results of this tweaking.
Of course Linux coders do this too. Java Servlets and JSP are also examples of this tweaking. You don't see this on Netware or anywhere else.
The way I see it is M$ will continue to improve NT/Win2K even if they break older stuff along the way, and even if only to beat competition from GNU/Linux. One thing Linux will do for sure, is ensure continued development of NT/Win2K.
Slashdot Mirror
I remember you can enable Q3 to be multithreaded in Win32, which is all you need on NT and Win2K to take advantage of SMP. I know a little about threads on Win32 to understand it's not difficult to use them. How easy is it to use threads on Linux?
Driver writers need to understand threads too. Come to think of it I don't even know if there's such a thing as a multithreaded driver.
Important point.
Have a look at An exploration into overlocked AGP. Of particular note, cards designed and cooled well (like ATI's Rage Fury MAXX) operated without a hitch. They also went overboard overlocking the 440BX to 150 MHz FSB cranking AGP up to 100 MHz.
If you're timid about overlocking, this is a good reason to wait for i815.
RAMBUS is an expensive joke! The i820 can't even keep up with the "old" 440BX based solutions. Have a look at a March 8th article that goes into all the gory details. To quote Mr Pabst: "Rambus seems to be a rather nasty disappointment."
Not everyone will want to overclock a 440BX board to 133 MHz, but since so little hardware is actually overclocked, and even then only by 30%, you stand little chance of ruining anything. Just make sure you use a CPU and SDRAM rated for 133 MHz FSB.
If anything, wait for i815 to come out. This is supposed to be the "real" successor to 440BX.
Besides the fact AOL can do whatever the fsck they want with their network since it's their property, so can ISPs running mail servers who don't want to accept SMTP directly from dial-up or end user IPs because of all the spam coming from them, refuse SMTP traffic from them. Have a look at the MAPS DUL Rationale for a better explanation.
Perhaps a little off topic, but I continue to be amazed with how many NT sites get taken by gougeware that can't even protect itself against relay theft. The ISP I used to work for used a free mail system for over three years with very few problems and no relay spam incidents. The filter developed for this (Antirelay) blocked all of ORBS' tests successfully.
If you're an NT site visit the IMS support page above and learn how to secure your mail servers and get off of ORBS.
As for AOL, it wouldn't surprise me that they _asked_ for servers to appear on ORBS. I'm still trying to determine why they asked for two IP proxies to appear in the MAPS DUL. Granted there should only be end user SMTP traffic coming from there and they're not mail servers, but AOL users using POPAUTH to access other mail servers are getting snagged because the POP3 connection comes from a different IP than the SMTP connection. SMTP AUTH still works though.
The various distros of Linux became this popular, not because of marketing or word of mouth or whatever, but because Linux has evolved and can continue to evolve. The other platforms referred to, especially Netware, haven't. You could throw a whole TCP/IP suite on top of Netware and make it look like an Internet server, but it still hasn't changed since Netware 4.x introduced NDS five years ago. Its age is showing.
NT, on the other hand, has also evolved, even if only to overtake competition from Novell and the *ixes. Despite what most of you all think, M$ programmers do not sit on their laurels all day and rake in the dough, but rather they tweak and twiddle with NT constantly trying to improve performance. ISAPI and ASP are results of this tweaking.
Of course Linux coders do this too. Java Servlets and JSP are also examples of this tweaking. You don't see this on Netware or anywhere else.
The way I see it is M$ will continue to improve NT/Win2K even if they break older stuff along the way, and even if only to beat competition from GNU/Linux. One thing Linux will do for sure, is ensure continued development of NT/Win2K.