We are in the process of collapsing our AD tree at the moment because queries against the directory are taking too long and it's becoming too unmanagable.
The suggestion that we had from our consultant was to break the directory into "users and groups" and "computers" It's just getting funnier and funnier about how this is all going to happen. I joked the other day to one of the other admins that we might as well go back to system policies, user manager and server manager. It's not that the JET database doesn't support it or anything, it's just that it's faster if it's flatter.
But the new server 2003 version is availiable for Itanium It's a hack, it is in no way shape or form as optimised as what the x86 versions are. It's also about to get dropped.
they are releasing a new version for the AMD_64 instruction set This isn't that much of a task as there isn't THAT much of a difference in the architectures between the x86 and AMD64 / EM64T platforms. It was ready ages ago. The problem was leaning on the hardware companies to get drivers together to ship with it to make it usable
and a modified version of windows will power the power pc based Xbox 2 Yup, it's the powerPC release of NT4 with a back port of DirectX 9.0c. That's the dev environment
Essentially there is a major trade off between performance and portability, something that every OS including Linux has to address. Microsoft uses the HAL to keep the hardware seperate from the software (kernel). The only problem was that everyone wanted to use the kernel to talk to the hardware to get better performance, which meant allowing more and more drivers into the kernel space. Given this, 2k and XP got faster and faster, but they became less and less portable because of how much they have riding on the kernel and how tied it is now to the x86 platform.
With what I know of cable segments, the only way to send a kill or reboot command to a cable modem is to send a command to the cable modem on a completely different subnet. (which the end user doesn't have access to any ability to route to)
I know that some of the motorola cable modems have the ability to reboot from a web interface and can be looked at from a web interface, but commands to these usually get sent to a private IP address such as a 10 address.
Given that the signals for the cable modem work in a COMPLETELY different signal space that is on a completely different level to TCP/IP, that has to be impossible.
Also DSL modems work completely different again, it's impossible to have a TCP/IP signal mess with this stuff.
Then there are those who were still so stuck with Trumpet Winsock, that they continued to use it on Windows 95.
I bought a version of it because I preferred it to the Win95 dial up connectivity. I guess when you use it for so long under Win 3.1 and worked with it on a day to day basis, it becomes something you don't want to let go of.
Further to that as well, if they think that one of the servers is being run at one of these junctions, they would end up having to talk to someone about the traffic that's flowing through there, get a port onto the network so that they can try to see what's going on.
What you could find is that the person who gives them the port is the one running the server and happens to pull the cable before the police or whoever could get their server booted.
SUS is only for the Windows platform itself, nothing more. Won't patch SQL server, won't patch the applications.
That's actually one of the things that MS is working on at the moment, if you ever go through and start installinga large amount of MS stuff, you will see that each different business unit has very different ways of installing apps, to be completely blunt it's a pain in the arse. MS can't patch everything using one platform at the moment, because their deployment platforms aren't the same. Essentially they are screwed. They are trying to get it together at the moment, and when they do they will bring out WUSS or Windows Update Services or something to that effect that will allow you to patch other MS apps, and presumably other vendors will have the ability to deploy using this platform too (I do believe this is to do with the installer system they "open sourced")
So it's nothing really that bad, it's just that they don't even have their shit together on their own applications and platforms, let alone trying to force everyone to do things their way (can very easily see it happening though...) apt / rpm / yum really do have the goods over MS at the moment on that front.
and only xferred once on the net. Try doing that simply with MS.
I hate to be a pest but where I am working currently we are only downloading once. It's just the standard HTTP proxy that we run for everything else. All the downloads come through HTTP and are easily cachable (just make sure that you set your object size big enough to get them all) it's not difficult. As for automated OS updates, use SUS.
At the end of the day, you knew this was coming up. Those with cable (or otherwise forethought, a mate of mine is on 256k dsl) are playing now. We pre-loaded and were awaiting the good things to come.
Nice to see that advance warnings of "Half life if preloading" fell on deaf ears.
Yes, the equipment itself will be compatible, but will the equipment that they replace it with (within the warranty period) still be compatible? Maybe not.
I say thism, as with Dell, I always get different revisions of network cards, IDE controllers and wierd other stuff that causes our Ghost builds to not work correctly in our test labs. The worst one was the other day a different revision of a CPU which RIS is now telling me requires a different HAL.
Basically Dell's answer was "If it will still boot with our system restore CDs, then it's your problem"
Given that it takes over an hour to F@#$ around with the Dell tech support in India essentially means that our ROI is gone, I believe it's now getting close to being cheaper to buy clone PCs even with the stuffing around with drivers and the labour costs on the org to install the parts ourselves.
I am going to move to HP and see what their support is like now.
1) I have a work PC, a home PC, a laptop, and a work PC at another site that I spend half my time at. Why does that mean I have to fork out for 4 X copies of Windows XP to keep the corporate standard so that I can connect into the network?
2) People see the OS as an enabler for the hardware, nothing more. People talk about Windows, it's the standard, they don't like the idea of paying for it, as if it's built into the cost of a PC as far as many consumers are concerned. A lot of people don't realise that they are paying for it when they purchase a new PC.
3) People don't mind paying a percentage of the cost of a PC for windows e.g. 10%. Now, the cost of an OEM license of Windows is about 1/5 or more the price of their PC. They aren't willing to wear it.
4) People have forked out for Windows again and again and again. They really want something new that will really impress them. (As a community, we really need this ourselves on linux to boot MS out of the market but nevertheless) They aren't recieving that at the moment because of the whole thing about it being the standard...
Either way, they are seriously lost here.
IBM bought Unix and made AIX as an enabler for the hardware they were selling, the market hasn't changed. Microsoft had better realise this fact and fast.
Educated guess would be that if the server, nor you can contact steam, it just lets you in.
Safest route really.
Imagine this: You turn up to a hall with 30 friends to have a LAN night. Who brought the modem or who has wireless to connect the LAN to the outside world to allow you to play HL2?
I don't think this is going to happen. If Steam is down, everyone plays, just means you get checked when the server turns on.
In all honesty, this all just sounds like Microsoft's implementation of Flash Remoting. If you don't want to work in Avalon /.Net; what we need to do is to get a hook into Flash and start working with that for forms etc.
Either way, this seems to me like it's going to be "Browser wars, round 2, FIGHT!"
Very much the case, the "Competitor" here isn't just Linux (It's just a kernel) It's fedora, it's redhat, it's debian, it's the FOSS movement as a whole that is getting to them. Linux by itself is such a small target, Apache and everything else is also within scope.
Slashdot Mirror
They probably will.
We are in the process of collapsing our AD tree at the moment because queries against the directory are taking too long and it's becoming too unmanagable.
The suggestion that we had from our consultant was to break the directory into "users and groups" and "computers" It's just getting funnier and funnier about how this is all going to happen. I joked the other day to one of the other admins that we might as well go back to system policies, user manager and server manager. It's not that the JET database doesn't support it or anything, it's just that it's faster if it's flatter.
It's a hack, it is in no way shape or form as optimised as what the x86 versions are. It's also about to get dropped.
they are releasing a new version for the AMD_64 instruction set
This isn't that much of a task as there isn't THAT much of a difference in the architectures between the x86 and AMD64 / EM64T platforms. It was ready ages ago. The problem was leaning on the hardware companies to get drivers together to ship with it to make it usable
and a modified version of windows will power the power pc based Xbox 2
Yup, it's the powerPC release of NT4 with a back port of DirectX 9.0c. That's the dev environment
Essentially there is a major trade off between performance and portability, something that every OS including Linux has to address. Microsoft uses the HAL to keep the hardware seperate from the software (kernel). The only problem was that everyone wanted to use the kernel to talk to the hardware to get better performance, which meant allowing more and more drivers into the kernel space. Given this, 2k and XP got faster and faster, but they became less and less portable because of how much they have riding on the kernel and how tied it is now to the x86 platform.
Just don't put it into a backpack and jog.
With what I know of cable segments, the only way to send a kill or reboot command to a cable modem is to send a command to the cable modem on a completely different subnet. (which the end user doesn't have access to any ability to route to)
I know that some of the motorola cable modems have the ability to reboot from a web interface and can be looked at from a web interface, but commands to these usually get sent to a private IP address such as a 10 address.
Given that the signals for the cable modem work in a COMPLETELY different signal space that is on a completely different level to TCP/IP, that has to be impossible.
Also DSL modems work completely different again, it's impossible to have a TCP/IP signal mess with this stuff.
Then there are those who were still so stuck with Trumpet Winsock, that they continued to use it on Windows 95.
I bought a version of it because I preferred it to the Win95 dial up connectivity. I guess when you use it for so long under Win 3.1 and worked with it on a day to day basis, it becomes something you don't want to let go of.
Further to that as well, if they think that one of the servers is being run at one of these junctions, they would end up having to talk to someone about the traffic that's flowing through there, get a port onto the network so that they can try to see what's going on.
What you could find is that the person who gives them the port is the one running the server and happens to pull the cable before the police or whoever could get their server booted.
SUS is only for the Windows platform itself, nothing more. Won't patch SQL server, won't patch the applications.
That's actually one of the things that MS is working on at the moment, if you ever go through and start installinga large amount of MS stuff, you will see that each different business unit has very different ways of installing apps, to be completely blunt it's a pain in the arse. MS can't patch everything using one platform at the moment, because their deployment platforms aren't the same. Essentially they are screwed. They are trying to get it together at the moment, and when they do they will bring out WUSS or Windows Update Services or something to that effect that will allow you to patch other MS apps, and presumably other vendors will have the ability to deploy using this platform too (I do believe this is to do with the installer system they "open sourced")
So it's nothing really that bad, it's just that they don't even have their shit together on their own applications and platforms, let alone trying to force everyone to do things their way (can very easily see it happening though...) apt / rpm / yum really do have the goods over MS at the moment on that front.
I hate to be a pest but where I am working currently we are only downloading once. It's just the standard HTTP proxy that we run for everything else. All the downloads come through HTTP and are easily cachable (just make sure that you set your object size big enough to get them all) it's not difficult. As for automated OS updates, use SUS.
Would that be angry looks as you run over their toes?
I am waiting for them to turn around and say:
"Just kidding!"
My personal hope is that they turn around and follow that up with:
"IBM didn't buy us, we used all our money on legal fees, we are now bankrupt, don't try to counter sue"
Sucks to be you.
At the end of the day, you knew this was coming up. Those with cable (or otherwise forethought, a mate of mine is on 256k dsl) are playing now. We pre-loaded and were awaiting the good things to come.
Nice to see that advance warnings of "Half life if preloading" fell on deaf ears.
Not in the states, still dealing with India....
I wish this were still the case....
Yes, the equipment itself will be compatible, but will the equipment that they replace it with (within the warranty period) still be compatible? Maybe not.
I say thism, as with Dell, I always get different revisions of network cards, IDE controllers and wierd other stuff that causes our Ghost builds to not work correctly in our test labs. The worst one was the other day a different revision of a CPU which RIS is now telling me requires a different HAL.
Basically Dell's answer was "If it will still boot with our system restore CDs, then it's your problem"
Given that it takes over an hour to F@#$ around with the Dell tech support in India essentially means that our ROI is gone, I believe it's now getting close to being cheaper to buy clone PCs even with the stuffing around with drivers and the labour costs on the org to install the parts ourselves.
I am going to move to HP and see what their support is like now.
Berny
My concern is that I am a single user with multiple job roles for different days.
Security requires me to have seperate PCs and applications in different places.
However, nobody can login into these machines but me, so it's not a case of multiple people using the machines (then I wouldn't have a problem)
BTW, it's my money that gets forked out as I own a good part of the business.
I have the distinct feeling that this isn't true.
1) I have a work PC, a home PC, a laptop, and a work PC at another site that I spend half my time at. Why does that mean I have to fork out for 4 X copies of Windows XP to keep the corporate standard so that I can connect into the network?
2) People see the OS as an enabler for the hardware, nothing more. People talk about Windows, it's the standard, they don't like the idea of paying for it, as if it's built into the cost of a PC as far as many consumers are concerned. A lot of people don't realise that they are paying for it when they purchase a new PC.
3) People don't mind paying a percentage of the cost of a PC for windows e.g. 10%. Now, the cost of an OEM license of Windows is about 1/5 or more the price of their PC. They aren't willing to wear it.
4) People have forked out for Windows again and again and again. They really want something new that will really impress them. (As a community, we really need this ourselves on linux to boot MS out of the market but nevertheless) They aren't recieving that at the moment because of the whole thing about it being the standard...
Either way, they are seriously lost here.
IBM bought Unix and made AIX as an enabler for the hardware they were selling, the market hasn't changed. Microsoft had better realise this fact and fast.
AWESOME!!!!
There were some new drivers released the other day.
I installed these applied the fedora patch and it runs just fine on a Radeon 9600. Not that fast mind you, but it certainly works.
BTW, if you are attempting to download, try the Bitorrent network, I pulled down the installer in about 30 seconds.
AWESOME!!!!!
There were some new drivers released the other day.
I installed these applied the fedora patch and it runs just fine on a Radeon 9600. Not that fast mind you, but it certainly works.
Berny
Only problem would be to ensure that I can burn it to CD to transfer it to another computer for when I format my drive.
Berny
Educated guess would be that if the server, nor you can contact steam, it just lets you in.
Safest route really.
Imagine this: You turn up to a hall with 30 friends to have a LAN night. Who brought the modem or who has wireless to connect the LAN to the outside world to allow you to play HL2?
I don't think this is going to happen. If Steam is down, everyone plays, just means you get checked when the server turns on.
One word: estoppel
If the copyright holders don't do anything about it now. They can't do anything about it later.
Do it for the common good. Aside from business, really what open source is for!
In all honesty, this all just sounds like Microsoft's implementation of Flash Remoting. If you don't want to work in Avalon / .Net; what we need to do is to get a hook into Flash and start working with that for forms etc.
Either way, this seems to me like it's going to be "Browser wars, round 2, FIGHT!"
Very much the case, the "Competitor" here isn't just Linux (It's just a kernel) It's fedora, it's redhat, it's debian, it's the FOSS movement as a whole that is getting to them. Linux by itself is such a small target, Apache and everything else is also within scope.
A tarago in an accident.
Call it lossy compression.