Now that it's on the Internet (maybe), everyone has access to it. It would be very hard for Microsoft to say "hey you had access so that's our code you're copying" because the obvious answer is "well so does everyone else." The fact that the code would be ubiquitous nullifies Microsoft's claim that you might be writing tainted code.
I'm a little confused. The BBC website has this in the news section. Now I've always understood news to be the (hopefully) unbiased reporting of facts. The "article" seems little more than the rambling musings of someone who clearly doesn't understand the situation at all - which ordinarily would put it under "editorials".
This sort of baseless conjecture should always be clearly marked as such. To pass this off as "news" smacks of the kind of wild sensationalism the BBC is world famous for.
I hear what you're saying as far as system overhead goes but I've been running Vet Anti-Virus for years without a single incident. The system overhead damage? try 2MB when fully resident.
I was in the same boat a few weeks ago. I was moving away from Red Hat 9 and needed a new distro. After a bit of tinkering with various distros I settled on Mandrake and have never looked back!
In my opinion Mandrake is the most user friendly distro out there and is certainly the best one if you want to get on to your computer and get your work done without a lot of tinkering.
Apart from how bloody quick it is is the fact that you can log every transaction. This is immensely useful in a mission critical environment when you have to figure our exactly why one person in particular out of the entire network is having trouble. Check your Samba logs and 99.9% of the time your answer will be there.
As a system administrator I appreciate having that level of scrutiny on any network I take care of.
Microsoft did this a few years ago with.NET itself. Lo and behold it suddenly appeared. When asked why it didn't come sooner, Microsoft said that it was up on the whiteboard but had to go due to timing, departmental and budget issues.
Moral: Microsoft never kills off the technology, they just delay it until they think the time is right.
What about Windows XP: Judgement Day?
Now that it's on the Internet (maybe), everyone has access to it. It would be very hard for Microsoft to say "hey you had access so that's our code you're copying" because the obvious answer is "well so does everyone else." The fact that the code would be ubiquitous nullifies Microsoft's claim that you might be writing tainted code.
I'm a little confused. The BBC website has this in the news section. Now I've always understood news to be the (hopefully) unbiased reporting of facts. The "article" seems little more than the rambling musings of someone who clearly doesn't understand the situation at all - which ordinarily would put it under "editorials".
This sort of baseless conjecture should always be clearly marked as such. To pass this off as "news" smacks of the kind of wild sensationalism the BBC is world famous for.
Now it's Earth - Eater of Mars!
I hear what you're saying as far as system overhead goes but I've been running Vet Anti-Virus for years without a single incident. The system overhead damage? try 2MB when fully resident.
Vet Anti-Virus (aka InoculateIT) detects this virus as of 18th January 2004.
I was in the same boat a few weeks ago. I was moving away from Red Hat 9 and needed a new distro. After a bit of tinkering with various distros I settled on Mandrake and have never looked back!
In my opinion Mandrake is the most user friendly distro out there and is certainly the best one if you want to get on to your computer and get your work done without a lot of tinkering.
You're writing a thesis on gay System Administrators who smell bad??
Wow that doctorate must be right around the corner...
Adding a machine to a domain is trivial. I did it to about 10 machines on a network once and it was a walk in the park.
/dev/null -c "machine id" -s /bin/false machine_name$
If you don't want Samba to do it automagically you can add machines (trust accounts) as follows:
Make yourself a machine group
#/usr/sbin/useradd -g trust-group -d
That's it. It writes the entry for your machine. You connect your machine Voila!
Easier to set Samba to do it for you though...
Apart from how bloody quick it is is the fact that you can log every transaction. This is immensely useful in a mission critical environment when you have to figure our exactly why one person in particular out of the entire network is having trouble. Check your Samba logs and 99.9% of the time your answer will be there.
As a system administrator I appreciate having that level of scrutiny on any network I take care of.
Microsoft did this a few years ago with .NET itself. Lo and behold it suddenly appeared. When asked why it didn't come sooner, Microsoft said that it was up on the whiteboard but had to go due to timing, departmental and budget issues.
Moral: Microsoft never kills off the technology, they just delay it until they think the time is right.
Unfortunatly Microsoft have already beaten you to the punch: some distros of the .NET framework had an (albeight inactive) infection of the Nimda worm.
After it was discovered on the CD Microsoft went into damage control and had to convince a whole bunch of people that it wasn't dangerous.
Guess Microsoft got a taste of it's own medicine when its own servers were compromised.