Well, for a start, this bug doesn't exactly inspire confidence.
Even less inspiring was this quote from the former founder that his "main reason for leaving was that I am not satisfied with the way the MySQL server has been developed, as can be seen on my previous blog post. In particular I would have like to see the server development to be moved to a true open development environment that would encourage outside participation and without any need of differentiation on the source code. Sun has been considering opening up the server development, but the pace has been too slow."
Of course, you should be downright worried by the following:
"The reason I am asking you to be very cautious about MySQL 5.1 is that there are still many known and unknown fatal bugs in the new features that are still not addressed.
To prove my points, here is some metrics and critical bugs for 5.1:
* We still have 20 known and tagged crashing and wrong result bugs in 5.1 35 more if we add the known crashing bugs from 5.0 that are likely to also be present in 5.1. * We still have more than 180 serious bugs (P2) in 5.1. Some of these can be found here. * We have more than 300 known and verified less critical bugs that are not going to be addressed soon. (The total reported number of bugs to the MySQL server is of course much larger)"
And yet, that is not the definition of third line forcing.
As I have already stated above, the ACCC says that third line forcing is "a specific form of exclusive dealing prohibited outright by the Trade Practices Act. It is not subject to the substantial lessening of competition test. It involves the supply of goods or services on condition that the purchaser buys goods or services from a particular third party, or a refusal to supply because the purchaser will not agree to that condition."
Therefore, I am correct and Apple refusing to let me use any service but their own when they supply me with the iPhone is strictly prohibited under Australian law.
"Third line forcing is a specific form of exclusive dealing prohibited outright by the Trade Practices Act. It is not subject to the substantial lessening of competition test. It involves the supply of goods or services on condition that the purchaser buys goods or services from a particular third party, or a refusal to supply because the purchaser will not agree to that condition."
Apple forcing someone to only use their service is exactly what third line forcing is, and this is strictly prohibited under the Australian Trade Practices Act.
That argument doesn't work. eBay was not the only online auction system on the Internet, but they got done like a dinner for third-line forcing when they tried to make everyone in Australia only use PayPal.
Screw whether what was written was unrelated to the parent post, I'm more amazed that he thinks that Protected Mode has anything to do with insulating hardware from rogue programs!
Attached is the final email received from the Backline Support Engineer from Symantec. For all interested in purchasing this product... think twice.
Our problem was scheduled reports fail and no email attachment is generated.
The software performs correctly in demo mode but does not work once we enter the serial number.
I guess buyer beware!
Here is the message:
Chris / Bob,
I left voicemail for each of you explaining the present status of this case?s issues. This email will give further details. The first issue where scheduled report jobs could not be run with SBS licensing will be addressed in an upcoming HotFix. I do not know the exact release date of the HotFix. The Second issue regarding Report Job email notification not attaching a report when configured will not be addressed at this time. This was looked at by engineering and was determined to be in a different area of code from the scheduled job issue and since yours is the only case we have received related to this particular issue, the priority is not sufficient for developing an immediate patch. Since this case was opened through Dell, I have notified our internal Dell representative about the issue and status. From a Tech Support, we have done all we can do. Bob, since this issue is obviously of great importance to you, I would recommend working through Dell to engage engineering or sales to raise the priority / visibility of this issue. If you have any questions, please let me know. The link below is for the TechNote released to cover the issue:
Looks like the tech support guy was cutting and pasting from a document. See the slide "Pay up". Note how the sentence starts, then it starts again 3 words later. Almost certainly laziness or they are trying to juggle too many conversations.
For all those in the U.S. - NSW is one state in a big landmass. Not all State governments do this sort of stupidity. NSW is in terminal decline at the moment, it's only a few years till us poor New South Welshmen get to kick them out of government. Unfortunately, my member of parliament is Joe Tripodi. Oops, did I type that into Google? Silly me.
As a New South Welshman, I'm not really particularly concerned. Especially as I've not been able to read the actual source bill to see exactly what it states can and cannot happen.
According to the report, nobody can be certain of this fact because of BGP spoofing. BGP spoofing! Surely they are stretching a long bow on that one. What has that got to do with someone cracking a Windows XP PC?
I know, it's awful and unfair. But after only 8 short years of Bush being in power, it looks like its going to take a while for these prejudices to subside.
Sure... given that the compiled code basically gets broken into a set of instructions that are encoded using an executable format, the same way that assembly code gets broken into a set of instructions that are encoded using an executable format.
Seriously, most non-trivial programs are better optimized by the compiler. Humans miss stuff, and often don't optimize very well anyway.
I think that he doesn't want to leave on bad terms...
A better way would be to leave, then get a reference from the firm and if it's untrue or bad then sue the manager for slander. I knew someone who got a bad reference, and when he found out what was said about him immediately knocked on his soon-to-be-ex-manager's door. The manager was on the phone, but he politely waited for the conversation to end and when the manager was done he confronted him about what was said. He was told that it was a fair assessment and that it was tough cheddar and he shouldn't have asked for a reference. So then the guy I know pulled out his mobile, called a lawyer and handed the manager the phone. The manager was then told that if he didn't call the firm he gave the bad reference to and retract his statement and provide a more honest account he would soon receive a formal letter that he's being sued.
Then my friend watched as the manager's blood drained from his face, then waited in the office while that same manager called the firm's recruiter to inform him that the statement was unfair and inaccurate. He told me it was one of the sweetest and most satisfying moments of his career, watching that douche-bag who'd been torpedoing his career with the firm eat his own words.
Sure, he still left on bad terms, but you can bet your bottom dollar that manager didn't leave any record that my friend left on bad terms. After all, he knew what would happen to him if he did that - my friend would have taken him for ever cent he'd ever owned, or at least tied him up in the court system for months. My friend never gives in.:-)
I'll believe it when I see it for myself.
It's really not as good as the other animation they did - "Irving the Social Awkward Bee".
Well, for a start, this bug doesn't exactly inspire confidence.
Even less inspiring was this quote from the former founder that his "main reason for leaving was that I am not satisfied with the way the MySQL server has been developed, as can be seen on my previous blog post. In particular I would have like to see the server development to be moved to a true open development environment that would encourage outside participation and without any need of differentiation on the source code. Sun has been considering opening up the server development, but the pace has been too slow."
Of course, you should be downright worried by the following:
"The reason I am asking you to be very cautious about MySQL 5.1 is that there are still many known and unknown fatal bugs in the new features that are still not addressed.
To prove my points, here is some metrics and critical bugs for 5.1:
* We still have 20 known and tagged crashing and wrong result bugs in 5.1 35 more if we add the known crashing bugs from 5.0 that are likely to also be present in 5.1.
* We still have more than 180 serious bugs (P2) in 5.1. Some of these can be found here.
* We have more than 300 known and verified less critical bugs that are not going to be addressed soon. (The total reported number of bugs to the MySQL server is of course much larger)"
And yet, that is not the definition of third line forcing.
As I have already stated above, the ACCC says that third line forcing is "a specific form of exclusive dealing prohibited outright by the Trade Practices Act. It is not subject to the substantial lessening of competition test. It involves the supply of goods or services on condition that the purchaser buys goods or services from a particular third party, or a refusal to supply because the purchaser will not agree to that condition."
Therefore, I am correct and Apple refusing to let me use any service but their own when they supply me with the iPhone is strictly prohibited under Australian law.
From the ACCC's website:
"Third line forcing is a specific form of exclusive dealing prohibited outright by the Trade Practices Act. It is not subject to the substantial lessening of competition test. It involves the supply of goods or services on condition that the purchaser buys goods or services from a particular third party, or a refusal to supply because the purchaser will not agree to that condition."
Apple forcing someone to only use their service is exactly what third line forcing is, and this is strictly prohibited under the Australian Trade Practices Act.
That argument doesn't work. eBay was not the only online auction system on the Internet, but they got done like a dinner for third-line forcing when they tried to make everyone in Australia only use PayPal.
Surely a case could be made against Apple's anti-competitive behaviour?
In Australia, what Apple is doing is against the law, under our anti-third-line forcing legislation.
Yes, evidently the patent was filed during a meeting, so I guess that if IBM implement their patent in Notes then that won't happen again.
Perhaps you should have just asked whether Windows XP works on an AMD64 platform?
Screw whether what was written was unrelated to the parent post, I'm more amazed that he thinks that Protected Mode has anything to do with insulating hardware from rogue programs!
Here's a response from 2005 that was NOT cut and pasted:
The original URL was https://forums.symantec.com/syment/board/message?board.id=103&message.id=17080, but they removed it. However, Google cache reveals all:
(Post from was Bob Sanford)
Attached is the final email received from the Backline Support Engineer from Symantec. For all interested in purchasing this product... think twice.
Our problem was scheduled reports fail and no email attachment is generated.
The software performs correctly in demo mode but does not work once we enter the serial number.
I guess buyer beware!
Here is the message:
Chris / Bob,
I left voicemail for each of you explaining the present status of this case?s issues. This email will give further details. The first issue where scheduled report jobs could not be run with SBS licensing will be addressed in an upcoming HotFix. I do not know the exact release date of the HotFix. The Second issue regarding Report Job email notification not attaching a report when configured will not be addressed at this time. This was looked at by engineering and was determined to be in a different area of code from the scheduled job issue and since yours is the only case we have received related to this particular issue, the priority is not sufficient for developing an immediate patch. Since this case was opened through Dell, I have notified our internal Dell representative about the issue and status. From a Tech Support, we have done all we can do. Bob, since this issue is obviously of great importance to you, I would recommend working through Dell to engage engineering or sales to raise the priority / visibility of this issue. If you have any questions, please let me know. The link below is for the TechNote released to cover the issue:
http://support.veritas.com/docs/281743
Regards,
Russ Perry
Backline Support Engineer
Symantec Corporation
www.symantec.com
Office: 407-357-7237
russell_perry@symantec.com
I've worked in support also, and I'm sure it is a CYA, but I'd say that they have a lot more canned responses than just that one.
Looks like the tech support guy was cutting and pasting from a document. See the slide "Pay up". Note how the sentence starts, then it starts again 3 words later. Almost certainly laziness or they are trying to juggle too many conversations.
Judging by the high ratings enjoyed by the producers of Underbelly, lots of people.
Or you could complain to the Minister for Transport", David Campbell. Alternatively find your electorate by doing an Electoral District search, then look at this list to see who your state member is.
For all those in the U.S. - NSW is one state in a big landmass. Not all State governments do this sort of stupidity. NSW is in terminal decline at the moment, it's only a few years till us poor New South Welshmen get to kick them out of government. Unfortunately, my member of parliament is Joe Tripodi. Oops, did I type that into Google? Silly me.
I guess you've never seen any reports about Victorian police then.
As a New South Welshman, I'm not really particularly concerned. Especially as I've not been able to read the actual source bill to see exactly what it states can and cannot happen.
According to the report, nobody can be certain of this fact because of BGP spoofing. BGP spoofing! Surely they are stretching a long bow on that one. What has that got to do with someone cracking a Windows XP PC?
We do understand what is causing it.
All right.
I know, it's awful and unfair. But after only 8 short years of Bush being in power, it looks like its going to take a while for these prejudices to subside.
Sure... given that the compiled code basically gets broken into a set of instructions that are encoded using an executable format, the same way that assembly code gets broken into a set of instructions that are encoded using an executable format.
Seriously, most non-trivial programs are better optimized by the compiler. Humans miss stuff, and often don't optimize very well anyway.
Oh brother. Comparing virtual memory spaces to JVMs. Only on slashdot.
I think that he doesn't want to leave on bad terms...
A better way would be to leave, then get a reference from the firm and if it's untrue or bad then sue the manager for slander. I knew someone who got a bad reference, and when he found out what was said about him immediately knocked on his soon-to-be-ex-manager's door. The manager was on the phone, but he politely waited for the conversation to end and when the manager was done he confronted him about what was said. He was told that it was a fair assessment and that it was tough cheddar and he shouldn't have asked for a reference. So then the guy I know pulled out his mobile, called a lawyer and handed the manager the phone. The manager was then told that if he didn't call the firm he gave the bad reference to and retract his statement and provide a more honest account he would soon receive a formal letter that he's being sued.
Then my friend watched as the manager's blood drained from his face, then waited in the office while that same manager called the firm's recruiter to inform him that the statement was unfair and inaccurate. He told me it was one of the sweetest and most satisfying moments of his career, watching that douche-bag who'd been torpedoing his career with the firm eat his own words.
Sure, he still left on bad terms, but you can bet your bottom dollar that manager didn't leave any record that my friend left on bad terms. After all, he knew what would happen to him if he did that - my friend would have taken him for ever cent he'd ever owned, or at least tied him up in the court system for months. My friend never gives in. :-)
In a way, telling them their own passwords was a dumb move really. If someone had gained unauthorized access, they might have come back at you!