Indeed, chances are they'll still be dealing with childish personalities and 6th grade comprehension skills (some of the MBA's can occasionally surpass 8th grade levels in marketspeak).
SC is far from perfect, it is performed on a scheduled basis just like a conventional backup. We had a customer's file store configured for noon and 17:30 checkpoints, for quite awhile and it came in handy on a couple occasions, sure beats digging out a tape and performing a restore. Recently one user spent several hours in the evening revising a document, the following morning the document was accidentally over written by another user. Because it was outside of the window, they lost those hours of work. We scheduled 23:00 and 04:00 checkpoints to improve the odds of saving late night sessions.
Larry Niven makes an interesting argument that any computer that reaches human level intelligence will go insane in months or less as it discovers that it is not human and can never be human, analyzing these deductions and their consequences at electronic speeds ultimately drives the intelligence to catanoia.
MS should PAY subscribers an annual stipend for as many years as they have been convicted as a monopolist and have withheld the information. I recall a time where you had to pay several hundreds of dollars to get the complete specification for facsimile transmission and reception. So how about $666, (999 upside down and the number of the beast, heh, any suggestions on how work in some kine of depiction of Mohammed?). Sent each year to any company subscribing who was a legitimate software business when MS was convicted, latecomers can get a softbound copy by paying the same $666 value. I could live with it never being produced in anything but hard-copy to reduce copyright violation by electronic distribution.
> I still don't understand why anyone would need DHCP
Pretty much any enterprise needs the ability to place some hosts within certain IP address blocks. Firewalls must be configured with known IP addreses for WWW hosts, mail servers, Thin client servers, VPN gateways, etc. Lots of stuff needs to have a permanant address. It's nice to have all the printers in one administrative subnet to restrict telnet access to them. In a multi-site scenario it is needed even more because you want your sites to be as identical as possible so that field engineers can learn where these resources are without regard to the site to which they are dispatched. DHCP allows an administrtor to consolidate and distribute the details of DNS, WINS, NTP that are so so easy to screw up by hand (and time consuming as well) into DHCP. If you have more than a couple hosts you should be using DHCP.
What flavor of kool-aid do you want today? Trusting MS or any other sociopathic corporation marketdroids to be honest or complete in their touting is naive at best. None of URL given reference the lack of IPv6 DHCP stateful address acquisition in the stacks noted in my post. A painful 30 minutes of searching through the boasting turned up "IPv6 protocol for the Windows Server 2003 family does not currently support DHCPv6 or any other stateful address configuration protocol" http://technet2.microsoft.com/WindowsServer/en/lib rary/6c05c210-e5f9-4882-b760-d275a80f35091033.mspx I am well aware the MS has done its typical "bragging rights" half-assed preliminary implemtation of standards for IPv6. Even if they had stateful DHCP implemented in the client, they don't have a functional DHCPv6 server yet to provide the addresses and options (e.g. static CIDR route or NTP server) and wont even be taking a swat at it until 2007Q4 (http://forums.microsoft.com/TechNet/ShowPost.aspx ?PostID=1436592&SiteID=17) for pity's sake. My point still stands, without the ability of DHCP to shape and organise address allocations according to enterpise requirements, any IPv6 implementation beyond a trivial single site is pretty much masturbatory, while it might feel good to you, nobody else gets anything out of it.
Currently there is little, if any, support for static leases. None of the MS stacks support it. I frequently use IPv4 static leases to put "special" hosts (servers, printers, etc) at known addresses and to administratively subnet host ranges, makes it easier to assign access control lists for firewalling and QoS. Until enterprise level capabilities arrive, IPv6 will remain primarily a laboratory curiosity.
Don't "representation" contracts usually have a morals clause? I wonder if I clever lawyer might be able to hold both sides to the same standard and let a conscientious artist get his contract terminated for these types of acts?
I see a couple Oracle employees sitting a parking lot across the street from the Houston SAP branch office using a cantenna and a LINKSYS wireless SSID to create all the clumsy incriminating access attempts.
To say nothing of monkeyboy "squirting" something. Although I prefer to replace the marketspeak with my own term "Dryping" (Dripping, transformation in the same vein as byte and nybble) a far more accurate representation of the action and much better negative connotation index.
Ehm, sir, what would be the advantage of it instead of installing on bare metal?
How about not having to co-ordinate the monthly re-boot of 8 virtual machines with the reboot of the host because the host is running windoze too. ESX (currently based on Linux 2.4 kernel) as a much sparser update cycle and the fixes are far less likely to be critical security issues exposing you to a 0 day vulnerability. Far better people than I have ranted on the advantage of OS diversity. Exercise you favorite search engine for additional points.
Slashdot Mirror
Whats a /. post without a good MS bash? (on-topic perhaps?)
a) perform a web search of that sophistication
b) perform that type of higher math calculation
SC is far from perfect, it is performed on a scheduled basis just like a conventional backup. We had a customer's file store configured for noon and 17:30 checkpoints, for quite awhile and it came in handy on a couple occasions, sure beats digging out a tape and performing a restore. Recently one user spent several hours in the evening revising a document, the following morning the document was accidentally over written by another user. Because it was outside of the window, they lost those hours of work. We scheduled 23:00 and 04:00 checkpoints to improve the odds of saving late night sessions.
MS should PAY subscribers an annual stipend for as many years as they have been convicted as a monopolist and have withheld the information. I recall a time where you had to pay several hundreds of dollars to get the complete specification for facsimile transmission and reception. So how about $666, (999 upside down and the number of the beast, heh, any suggestions on how work in some kine of depiction of Mohammed?). Sent each year to any company subscribing who was a legitimate software business when MS was convicted, latecomers can get a softbound copy by paying the same $666 value. I could live with it never being produced in anything but hard-copy to reduce copyright violation by electronic distribution.
You are alone, and don't call me Seams.
The sword is made of Diamond 9 and if it touches other diamonds they too become Diamond 9
(Apologies to the late KV).
interesting point, I'll see if you make it in that article too.
It's probably some kinda [sic] joke.
> I still don't understand why anyone would need DHCP
Pretty much any enterprise needs the ability to place some hosts within certain IP address blocks. Firewalls must be configured with known IP addreses for WWW hosts, mail servers, Thin client servers, VPN gateways, etc. Lots of stuff needs to have a permanant address. It's nice to have all the printers in one administrative subnet to restrict telnet access to them. In a multi-site scenario it is needed even more because you want your sites to be as identical as possible so that field engineers can learn where these resources are without regard to the site to which they are dispatched. DHCP allows an administrtor to consolidate and distribute the details of DNS, WINS, NTP that are so so easy to screw up by hand (and time consuming as well) into DHCP. If you have more than a couple hosts you should be using DHCP.
What flavor of kool-aid do you want today?b rary/6c05c210-e5f9-4882-b760-d275a80f35091033.mspx x ?PostID=1436592&SiteID=17) for pity's sake. My point still stands, without the ability of DHCP to shape and organise address allocations according to enterpise requirements, any IPv6 implementation beyond a trivial single site is pretty much masturbatory, while it might feel good to you, nobody else gets anything out of it.
Trusting MS or any other sociopathic corporation marketdroids to be honest or complete in their touting is naive at best.
None of URL given reference the lack of IPv6 DHCP stateful address acquisition in the stacks noted in my post. A painful 30 minutes of searching through the boasting turned up "IPv6 protocol for the Windows Server 2003 family does not currently support DHCPv6 or any other stateful address configuration protocol" http://technet2.microsoft.com/WindowsServer/en/li
I am well aware the MS has done its typical "bragging rights" half-assed preliminary implemtation of standards for IPv6. Even if they had stateful DHCP implemented in the client, they don't have a functional DHCPv6 server yet to provide the addresses and options (e.g. static CIDR route or NTP server) and wont even be taking a swat at it until 2007Q4 (http://forums.microsoft.com/TechNet/ShowPost.asp
Currently there is little, if any, support for static leases. None of the MS stacks support it. I frequently use IPv4 static leases to put "special" hosts (servers, printers, etc) at known addresses and to administratively subnet host ranges, makes it easier to assign access control lists for firewalling and QoS. Until enterprise level capabilities arrive, IPv6 will remain primarily a laboratory curiosity.
Don't "representation" contracts usually have a morals clause? I wonder if I clever lawyer might be able to hold both sides to the same standard and let a conscientious artist get his contract terminated for these types of acts?
I see a couple Oracle employees sitting a parking lot across the street from the Houston SAP branch office using a cantenna and a LINKSYS wireless SSID to create all the clumsy incriminating access attempts.
anything with a MS copyright or a ".exe" suffix.
To say nothing of monkeyboy "squirting" something. Although I prefer to replace the marketspeak with my own term "Dryping" (Dripping, transformation in the same vein as byte and nybble) a far more accurate representation of the action and much better negative connotation index.
"Windows Vista ... designed to ... prevent the software from working correctly".
Hmmm, wonder what it says when played backwards at 78RPM.
I am sure you have a point in there somewhere, but if you cant be bothered to format and preview, I certainly can't be bothered to read it.
Your post has revealed the need for a "+1 Funnier".
My visual is the trigger guard, chamber port and magazine slot obscured by manufacturer logo stickers.