The policy should state that if the company wants employees to work from home, the company will provide a VPN, otherwise the employees will only work during work hours.
Not quite. Dave Cutler and his band of merry men left DECwest in Bellevue, WA, drove a few blocks east and north to Redmond, and wrote an operating system based on the same ideas they had used before several times. They wanted to stay at DEC, but DEC didn't want another operating system or computer architecture to compete with VMS and VAX. DEC was busy driving the company out of business. So the tribe moved to MS and "started over". This time it was in C instead of some home grown systems language they had invented. This time on commodity hardware instead of their own homegrown architecture. (I believe NT first ran on some custom MIPS RISC boards built for the purpose.) It was portable, and ran on I86. MS insisted that the Windows UI be ported to run on the new kernel. Dave was a CLI guy.
They mostly started from scratch, except for the parts that were alleged to be "translated" and became a source of a lawsuit most people never heard of. They didn't buy NT, they bought people.
The funny part is that Dave used to call PC's "Fucking toy computers".
From the linked article:
"It may take sometime to fix the cut but we are rerouting the traffic to another cable in the U.K. and U.S...." How convenient. As far as the US is concerned, it's definitely legal to spy on foreign communications that transits US borders. FISA doesn't even apply (not that it really does anymore, but that's another story.) And I wouldn't be surprised if Britain thinks the same...
[...]or use plural conjucations for corporations. "Apple are selling.." just never sounds right. Yah, but you probably have no problem using "they" when referring to them, do you? "They just introduced a new iPod..." Bit inconsistent, no?
...doesn't mean that they look at it all. True, but it does mean they can and there's no oversight or assurance they're not. This is a clear departure from the past.
Historically, law enforcement had to show probable cause to obtain a court order to intercept the communications of a person, and the communications provider would direct just that traffic to them. This would take the collusion of three independent parties to violate your privacy (law enforcement, the courts, and the communications provider.)
Now we have a spy agency taking all of the traffic handled by a major communications provider, with no court order. Clearly the communications provider have abdicated their responsibility under the law (and they are now seeking protection from the Congress), the courts aren't involved, and instead of law enforcement, we have a secret agency who's operation we know very little about.
Whether they use a filter or not is irrelevant, they have the ability, without oversight, to do anything they want. So your point is so weak as to be meaningless. If you don't see this a problem, then I'm afraid our forefathers wasted their time and the terrorists have indeed won by depriving you of the liberties paid for with the blood of the former.
It's not a longstanding history. It started in mid-1990s. In the early 1990s, if you bought a 300 MB drive, you got 300*1024^2 = 314,572,800 bytes. Please provide some proof for that claim.
I bought a Quantum Q105 (still have it) back in the late 80's and I can assure you that it has 105 million bytes on it. The Amiga OS, thought different, of course, and is just as broken today as it was then.
I've been working on computers with hard drives for a long time, possibly before you were born. As long as I can remember, hard drive capacity has been measured in powers of 10, so I don't believe any of your mid-90's claim unless you'd like to back it up with some specifics.
Ok, this is going WAY too far! [...]
I mean other than the FUD that the NYT and Democrats spread which also is not based on any actual proof. [...]
If you're going to make outrageous claims, you need to back them up with actual proof. If only the administration held itself to that same basic standard...
Heavy gauge lamp cord is a really poor way to buy speaker cable. You can find speaker cable that will be more flexible and easier to handle/work with in the same price range... So it's "really poor" because there's a "more flexible" and "same price range" alternative? I think you're exaggerating the value of flexibility.
The issue here was sound quality, and I haven't noticed that flexibility affects sound quality any more than oxygen content, and I've never been disappointed in the flexibility of what I buy.
...appropriate length of oxygen free copper cable/wire with sufficient shielding... Oh please. Apparently something more than the copper has been deprived of oxygen. Shielding? Speaker cables? I hope you're shielding your power cables too.;-)
...and appropriate gauge. The only correct thing you said. Go to the hardware store, buy heavy gauge lamp cord. You'll be fine.
Heh, OSI "lost" for a number of reasons, but in my mind the chief reason is because their standards were designed by committees of vendors and telcos instead of users (i.e. people that wanted to build networks). Each participant tried to get his idea of networking defined as standard. Since the ideas varied quite a bit, and there was no consensus, nor experience from actual implementations, these differing ideas became "options". When vendors started releasing actual OSI compliant systems users quickly found out that with all the options at each layer (e.g. TP0-TP4) it was a miracle if any two vendors systems would interoperate. All the while the vendors claimed to be standard.
So a big reason why OSI lost is because it wasn't a standard, it was a smorgasbord of of implementation options.
If the OSI gang had had the sense to make their docs available free on the Internet, they might not have lost so badly.
Think about that for a second and I think you'll find it as funny as I did. If the Internet existed for the docs to be available on, what then is the point of developing OSI? (Yes, I agree that the cost of specifications is an issue, and that the ISO charged way too much for OSI specs.)
Latency/jitter tolerance is greatly improved with larger window sizes in your network layer. Yah, whatever. Enjoy your VOIP at ~1000 ms network latency. This will be some of the most expensive dialup-like service on the planet.
"Security guru" is just Computerworld headline hype. His title is "program manager", meaning he really works for Marketing telling Engineering what to build. The "program" he's managing is the one to make the security of Microsoft operating systems not look so bad. As is obvious from his comments, his interests are more in perception than facts and metrics. He's trying to use "relativist" arguments to convince us that Vista is better than the facts would indicate. He's trying to get some press that says: "It's better than XP!"
I don't now about them Winders servers, but as far as I know, their answer is correct for Linux/Unix.
Except for perhaps their email messages or logs having the wrong date, it shouldn't cause any real problems. Any software that cares about times would be using *internal* times (e.g. time_t in C) which doesn't change with DST anyway. If software uses *external* time, it likely broken with any DST change, no matter when it happens. DST changes only change the external representation of the internal value of the clock, not the actual value of the clock. Geez, changing the clock for DST would be stupid.
It seems the U.S. Coast Guard was able render aid admirably without the need for any need for martial law. This is what makes the actions of the other "responders" so obviously lacking.
...using the 64K service offered by Inmarsat. Ping times are typically 850-1000ms, which is just over the physical limit imposed by geo satellites
The round-trip delay due to the speed of light for the geosynchronous satellites used by Inmarsat is at most ~500ms. The extra 350-500ms is caused by Inmarsat processing delays.
Not really sure why you were seing such high latency with Connexion.
I'm guessing they were having a bad day, or there are places in the world they don't route well to. Measurements of Connexion's system on various flights seems to indicate a typical round trip delay of ~700ms. (I seem to recall a figure as low as 650.)
For interactive network usage (anything other than file transfer) latency is critical, and that extra 150-300ms in Inmarsat's system makes it marginal at best. I'm sure the corporate users you speak of think the service is acceptable, but they're comparing that to not being connected at all.
Note: I do not work for Connexion, never have, and probably never will.
Of course proper unit tests are necessary; I wouldn't dream of suggesting otherwise. My point was simply that for this kind of project, they aren't sufficient. The XP approach inherently assumes that they are, and is fundamentally unsuitable for this type of work.
XP does not assume unit tests are sufficient. Your opinions are fundamentally unsuitable to be followed for this type of work.
It seems odd to blame this on Google. According to the linked mailing list posting, the problem is caused by the "auto detect character set" feature in IE (and probably other browsers,) and the lack of a "charset" parameter in the HTTP response from Google. The HTTP spec is pretty clear that a missing charset parameter means ISO-8859-1, not "browser should guess", and certainly not UTF-7.
So isn't it really the "auto detect" feature in the browser that causes the vulnerability, and not Google's lack of "charset encoding enforcement" as the mailing list posting from Watchfire Research claims? Let's put the blame where it belongs. I say we should applaud Google for going the extra kilometer to protect users with non-compliant browsers.
I think it's great that libraries are seeing a rebirth, and I'm pleased that Melinda is spending some of Bill's enormous wealth helping some of the worst off.
The NYT and/or the University should also pay a visit to the Remdond branch of the King County Library, here in Micro$oft's backyard. I estimate they have about 50 internet surfboards running Windows XP Embedded. They've removed quite a few stacks of dead-tree books over the years to make room for more kiosks.
On a recent weekend trip to help my daughter with a school report, about an hour after opening, more than half of the workstations were unusable - clearly booted, but hung. While my daughter was writing notes, I rebooted several nearby workstations using CTRL-ALT-DEL. A woman with her child was power-cycling the ones in her area to help frustrated patrons. The librarians were busy restarting the ones near their desk, and obviously trying hard to spend time actually helping patrons find information instead of supporting the systems....
Slashdot Mirror
The policy should state that if the company wants employees to work from home, the company will provide a VPN, otherwise the employees will only work during work hours.
Thanks for finally getting around to the car analogy. I really didn't understand all that MIPS CISC RISC stuff, but that cleared it up!
Not quite. Dave Cutler and his band of merry men left DECwest in Bellevue, WA, drove a few blocks east and north to Redmond, and wrote an operating system based on the same ideas they had used before several times. They wanted to stay at DEC, but DEC didn't want another operating system or computer architecture to compete with VMS and VAX. DEC was busy driving the company out of business. So the tribe moved to MS and "started over". This time it was in C instead of some home grown systems language they had invented. This time on commodity hardware instead of their own homegrown architecture. (I believe NT first ran on some custom MIPS RISC boards built for the purpose.) It was portable, and ran on I86. MS insisted that the Windows UI be ported to run on the new kernel. Dave was a CLI guy.
They mostly started from scratch, except for the parts that were alleged to be "translated" and became a source of a lawsuit most people never heard of. They didn't buy NT, they bought people.
The funny part is that Dave used to call PC's "Fucking toy computers".
I can't figure out if that's 266,240 and 51,200 or 260,000 and 50,000. Oh, it has something to do with computers, so it must be powers of two, right?
...doesn't mean that they look at it all. True, but it does mean they can and there's no oversight or assurance they're not. This is a clear departure from the past.Historically, law enforcement had to show probable cause to obtain a court order to intercept the communications of a person, and the communications provider would direct just that traffic to them. This would take the collusion of three independent parties to violate your privacy (law enforcement, the courts, and the communications provider.)
Now we have a spy agency taking all of the traffic handled by a major communications provider, with no court order. Clearly the communications provider have abdicated their responsibility under the law (and they are now seeking protection from the Congress), the courts aren't involved, and instead of law enforcement, we have a secret agency who's operation we know very little about.
Whether they use a filter or not is irrelevant, they have the ability, without oversight, to do anything they want. So your point is so weak as to be meaningless. If you don't see this a problem, then I'm afraid our forefathers wasted their time and the terrorists have indeed won by depriving you of the liberties paid for with the blood of the former.
I bought a Quantum Q105 (still have it) back in the late 80's and I can assure you that it has 105 million bytes on it. The Amiga OS, thought different, of course, and is just as broken today as it was then.
I've been working on computers with hard drives for a long time, possibly before you were born. As long as I can remember, hard drive capacity has been measured in powers of 10, so I don't believe any of your mid-90's claim unless you'd like to back it up with some specifics.
Haven't seen anyone mention the OS distro website: http://www.thinkgos.com/
"An alternative OS with Google
Apps and other Web 2.0 apps
for the masses"
Also says "Website coming 9am, November 1, 2007", which is almost 10 minutes ago!
The issue here was sound quality, and I haven't noticed that flexibility affects sound quality any more than oxygen content, and I've never been disappointed in the flexibility of what I buy.
...appropriate length of oxygen free copper cable/wire with sufficient shielding... Oh please. Apparently something more than the copper has been deprived of oxygen. Shielding? Speaker cables? I hope you're shielding your power cables too.
...and appropriate gauge. The only correct thing you said. Go to the hardware store, buy heavy gauge lamp cord. You'll be fine.So a big reason why OSI lost is because it wasn't a standard, it was a smorgasbord of of implementation options.
Think about that for a second and I think you'll find it as funny as I did. If the Internet existed for the docs to be available on, what then is the point of developing OSI? (Yes, I agree that the cost of specifications is an issue, and that the ISO charged way too much for OSI specs.)...updating atime on close(2). It's been a long time, but I think that's what the best operating system of all time (TOPS-20) did.
"Security guru" is just Computerworld headline hype. His title is "program manager", meaning he really works for Marketing telling Engineering what to build. The "program" he's managing is the one to make the security of Microsoft operating systems not look so bad. As is obvious from his comments, his interests are more in perception than facts and metrics. He's trying to use "relativist" arguments to convince us that Vista is better than the facts would indicate. He's trying to get some press that says: "It's better than XP!"
I don't now about them Winders servers, but as far as I know, their answer is correct for Linux/Unix.
Except for perhaps their email messages or logs having the wrong date, it shouldn't cause any real problems. Any software that cares about times would be using *internal* times (e.g. time_t in C) which doesn't change with DST anyway. If software uses *external* time, it likely broken with any DST change, no matter when it happens. DST changes only change the external representation of the internal value of the clock, not the actual value of the clock. Geez, changing the clock for DST would be stupid.
Higgins claims to be a trust framework. OpenID claims to not be a trust framework.
It seems the U.S. Coast Guard was able render aid admirably without the need for any need for martial law. This is what makes the actions of the other "responders" so obviously lacking.
If the choice isn't obvious, then you belong at Microsoft. You're made for each other.
The round-trip delay due to the speed of light for the geosynchronous satellites used by Inmarsat is at most ~500ms. The extra 350-500ms is caused by Inmarsat processing delays.
Not really sure why you were seing such high latency with Connexion.
I'm guessing they were having a bad day, or there are places in the world they don't route well to. Measurements of Connexion's system on various flights seems to indicate a typical round trip delay of ~700ms. (I seem to recall a figure as low as 650.)
For interactive network usage (anything other than file transfer) latency is critical, and that extra 150-300ms in Inmarsat's system makes it marginal at best. I'm sure the corporate users you speak of think the service is acceptable, but they're comparing that to not being connected at all.
Note: I do not work for Connexion, never have, and probably never will.
It seems odd to blame this on Google. According to the linked mailing list posting, the problem is caused by the "auto detect character set" feature in IE (and probably other browsers,) and the lack of a "charset" parameter in the HTTP response from Google. The HTTP spec is pretty clear that a missing charset parameter means ISO-8859-1, not "browser should guess", and certainly not UTF-7.
So isn't it really the "auto detect" feature in the browser that causes the vulnerability, and not Google's lack of "charset encoding enforcement" as the mailing list posting from Watchfire Research claims? Let's put the blame where it belongs. I say we should applaud Google for going the extra kilometer to protect users with non-compliant browsers.
People use the 'you should comment your code' excuse because they are lazy and don't want to take the time to actually write understandible code.
I think it's great that libraries are seeing a rebirth, and I'm pleased that Melinda is spending some of Bill's enormous wealth helping some of the worst off.
The NYT and/or the University should also pay a visit to the Remdond branch of the King County Library, here in Micro$oft's backyard. I estimate they have about 50 internet surfboards running Windows XP Embedded. They've removed quite a few stacks of dead-tree books over the years to make room for more kiosks.
On a recent weekend trip to help my daughter with a school report, about an hour after opening, more than half of the workstations were unusable - clearly booted, but hung. While my daughter was writing notes, I rebooted several nearby workstations using CTRL-ALT-DEL. A woman with her child was power-cycling the ones in her area to help frustrated patrons. The librarians were busy restarting the ones near their desk, and obviously trying hard to spend time actually helping patrons find information instead of supporting the systems....