Actually, it is possible to tune performance under NT... you just have to know what to look for. Most of the tuning takes place under settings in the registry. You can do nifty things like processor affinity under SMP (where you can lock a service/application to a single processor), network performance tuning for various services and drivers, etc.
The following site has some excellent information on taming the Beast that is NT:
There are other sites that go into this as well, such as System Internals, which also provide handy utilities for things like monitoring open files etc.
That's all the pimping I'm going to do for NT today. Back to Linux Mandrake on my laptop:-).
MSE best practices would entail putting in place practices to discourage, if not ban, code hacking when using Linux.
Now, what's wrong with this picture? Code hacking is the primary driver behind the acceptance and growth of the Linux marketplace. Why is it that dumb-ass consultants have to insist that everyone act as dumb as possible around technology - especially technology that is strategic to the function of your organization?
Right, I just answered my own question (it's so we always have to hire dumb-ass consultants).
Underground optics are good, as are the thick concrete buildings that COs reside in.
Don't forget about all the rebar that's inside of that thick concrete... makes for a nice Faraday cage I would guess.
Stupid Jamie Zawinsky quote...
on
Love of Unix
·
· Score: 1
If I spend the same amount of time on a system that I spent money on (specifically, because the commercial offering was supposed to save me time and trouble), does the company I bought the product from refund me for the "extra" time?
How about another quote:
"Linux is only free if your time has no value. Then again, you could pay for your software twice..."
I fail to see how fiber needs all this weighty shielding - it pushes photons, and is usually the network media of choice in electromagnetically noisy environments
Fiber isn't even close to being bleeding edge technology - I was splicing fiber with hand tools five years ago, no problem
10Base2 draws power - in fact, you can feed 12.5 volts to devices via a 10Base2 tap. I'm betting that laser diodes draw less, especially for multimode fiber
Who said this was going to be assembled in space? The modules go up pre-constructed
I can see the transceivers causing trouble - the damn things are so light, though, you could send up a few spares without feeling it
Yeah, I was ranting... I just wish I knew more about why they made the decisions they did. It would appear at first glance that they could have chosen better technology for space.
Who gives a rat's ass about 10Base2 being shielded
on
Space Station's LAN
·
· Score: 1
I guess they don't know how to use FIBER in space yet... I agree with everyone else, 10Base2 as a choice was pretty stupid. It ranks right up there with sending '95 and NT into space on COTS PC hardware. It's heavier, it's a single point of failure, its bandwidth limit sucks... I'd go on, but I'm foaming at the mouth as it is.
I'd love to see how much trouble they have when they need a patch right now from their precious COTS sources. If I had to operate the thing, I would be screaming GIVE ME THE CODE - GIVE ME THE SPECS - NOW!
Why is it we always end up with dinosaur brains designing "The Next Generation" platforms?
I seem to recall a story from a few months back where the engineers working on Mach v3 for the PA-RISC machines used Mk/Linux as their reference personality for development/testing. According to the article, this made Linux capable of running on all of their PA-RISC line, including everything from workstations clear up to the super-minis.
I'm surprised we didn't see more news about it at the time... I'll see if I can dig up the URL.
... is the way of things. It is wise to be prepared when living in such a world.
Arguing over who had weapons first is like arguing the chicken and egg problem. Wishing for all weapons to eventually go away is like Canute commanding the sea to recede.
There is nothing wrong with holding a philosophy which is against weaponry. If you can survive in such a fashion it is admirable and right to do so. There comes a time, however, when instruments of force and violence are necessary. When such times arise I would prefer to be ready for them. If this means having weapons in order to deter those who would use weapons against me, then so be it. If I choose to use said weapons in an immoral and unrighteous fashion, then it is only fitting that I expect those around me to prevent this by any means necessary - including their own use of weapons against me.
The existence of weapons has never been the problem; it's the willingness of people to use them against others to force their will that is the problem. Since there will never be a shortage of such people, and since eliminating the pursuit of weapons is impossible given our nature, it is proper to arm one's self for defense against them.
I'm rambling... I'll stop. It's people, not weapons.
... is not like the other, which one is different, do you know?
Linux == "here and working now"
Merced == "vapour CPU which will never see light"
Don't hold your breath waiting for Merced to be released... when it is, it will be called "McKinley", and will have much more to do with HP than with Intel.
Man, it must hurt to die as many times as SCSI has been reputed to...
SCSI will be with us for a long time. Fine by me... it's mature, stable, and plenty quick for 9/10 of the things that need to be done with storage. I'm all for Firewire and crew, but I just don't see the need to rip out my SCSI installed base yet. It does what I need it to do.
Slashdot Mirror
Whatever.
The following site has some excellent information on taming the Beast that is NT:
Click here for NT registry hacks
There are other sites that go into this as well, such as System Internals, which also provide handy utilities for things like monitoring open files etc.
That's all the pimping I'm going to do for NT today. Back to Linux Mandrake on my laptop :-).
Plus, these guys have a free download for this (stripped down, but still useful) that runs on FreeBSD.
MSE best practices would entail putting in place practices to discourage, if not ban, code hacking when using Linux.
Now, what's wrong with this picture? Code hacking is the primary driver behind the acceptance and growth of the Linux marketplace. Why is it that dumb-ass consultants have to insist that everyone act as dumb as possible around technology - especially technology that is strategic to the function of your organization?
Right, I just answered my own question (it's so we always have to hire dumb-ass consultants).
Don't forget about all the rebar that's inside of that thick concrete... makes for a nice Faraday cage I would guess.
How about another quote:
"Linux is only free if your time has no value. Then again, you could pay for your software twice..."
Oddly enough, I get the job done and have a life as well. I guess you just aren't very efficient.
- I fail to see how fiber needs all this weighty shielding - it pushes photons, and is usually the network media of choice in electromagnetically noisy environments
- Fiber isn't even close to being bleeding edge technology - I was splicing fiber with hand tools five years ago, no problem
- 10Base2 draws power - in fact, you can feed 12.5 volts to devices via a 10Base2 tap. I'm betting that laser diodes draw less, especially for multimode fiber
- Who said this was going to be assembled in space? The modules go up pre-constructed
- I can see the transceivers causing trouble - the damn things are so light, though, you could send up a few spares without feeling it
Yeah, I was ranting... I just wish I knew more about why they made the decisions they did. It would appear at first glance that they could have chosen better technology for space.I'd love to see how much trouble they have when they need a patch right now from their precious COTS sources. If I had to operate the thing, I would be screaming GIVE ME THE CODE - GIVE ME THE SPECS - NOW!
Why is it we always end up with dinosaur brains designing "The Next Generation" platforms?
I'm surprised we didn't see more news about it at the time... I'll see if I can dig up the URL.
Arguing over who had weapons first is like arguing the chicken and egg problem. Wishing for all weapons to eventually go away is like Canute commanding the sea to recede.
There is nothing wrong with holding a philosophy which is against weaponry. If you can survive in such a fashion it is admirable and right to do so. There comes a time, however, when instruments of force and violence are necessary. When such times arise I would prefer to be ready for them. If this means having weapons in order to deter those who would use weapons against me, then so be it. If I choose to use said weapons in an immoral and unrighteous fashion, then it is only fitting that I expect those around me to prevent this by any means necessary - including their own use of weapons against me.
The existence of weapons has never been the problem; it's the willingness of people to use them against others to force their will that is the problem. Since there will never be a shortage of such people, and since eliminating the pursuit of weapons is impossible given our nature, it is proper to arm one's self for defense against them.
I'm rambling... I'll stop. It's people, not weapons.
Linux == "here and working now"
Merced == "vapour CPU which will never see light"
Don't hold your breath waiting for Merced to be released... when it is, it will be called "McKinley", and will have much more to do with HP than with Intel.
SCSI will be with us for a long time. Fine by me... it's mature, stable, and plenty quick for 9/10 of the things that need to be done with storage. I'm all for Firewire and crew, but I just don't see the need to rip out my SCSI installed base yet. It does what I need it to do.