I'll do my part to see that Novell never sells another Suse install anywhere I have influence. I suggest you do the same. All these asshats could see were the dollar signs in theri eyes. I hope they enjoy it while they can. I wonder if the courts would say that the outcome was obvious, therefore Novell's executives are civilly liable to the shareholders for doing the deal in the first place.
A few days ago I got a pre-recorded sales call to my cell phone. In a noisy environment all I got was something about mortgage loan refinancing. I hung up on 'em. The caller ID said: 949-519-1007. I later searched [googled] for the phone number and found this number 800-606-1470. When I called the number, the gorilla that answered said, "Assured Lenders". I told 'em they made a telemarketing call to a cell phone, the gorilla insulted me and hung up on me.
I don't have the ooomph to persue these a**holes to ground, so, I'll leave this as a caution.
The tell you up front that they will install software ('plug-ins') on your computer. That they will share what they know about you with 'trusted partners'. That they e-pend what they can find from others about you.
All of a sudden we begin seeing MS mouthing off about being open with this that or the other vendor. BFD.
What I imagine is happening is that MS is setting the world up for another round of FUD. Watch this:
MS gets 'open' with a bunch of different equipment makers and announces to the world how open they are. The press will pick it up and report on it.
In the meantime, MS remains as niggardly as ever in its relations with Linux. They expect the FUD in other areas of business to give the appearance that they are open toward Linux too.
The Linux community complains that MS are being closed with the interfaces, file formats, packet formats. MS denies it in the press pointing out how open they are in other areas. The press buys it and dismisses the Linux community as being unable to compete.
... with their voting systems. The leaked documents saying how they were gonna screw the customers by over pricing a print capability, having back doors where elections officials could manipulate the results, and other stuff put some fear into their customers.
Would you want to do business with a company like siebel?
I suppose MS's first step is to provide warnings to ISPs about their spamming customers and zombies. The next and obvious question is, What Comes Next?
Will MS(Hotmail) begin blocking those ISP's? Will MS send them a notice saying something like, "... after $DATE we will bill you $BIGBUX per thousand spams. By continuing to spam our customers you agree to pay."
Frankly, it sounds good to me. Let the BigGorillas set the tone and practice for spam.
No doubt, you were the asshat running an MSExchange server connected directly to the internet.
In spite of what you might think, the listing was most likely fully warranted. Your lack of due dilligence in selecting an MTA is not a reason to whine when the rest of the internet refuses your traffic.
... That Dell signed a [very] long term contract with Intel not to use AMD parts? Is it possible that in exchange for those contract terms that Dell got very favorable pricing for Intel parts?
In the face of an apparent better mousetrap, Dell adheres to the inferrior supplier.
Occam's Razor. The simplest answer is usually the right answer.
The OP is extremely vague about exactly what IP range is involved. So, I smell a rat up front.
But, for sake of argument: Suppose the IP space had a notorious spammer in residence for a long time. Suppose the owner of that huge space had ignored complaints for a long time. Then, were I MAPS, or SPEWS, or SBL or any other block list, I'd have no qualms at all about dropping the space into a blocklist then leaving for a 2-week vacation.
As for the poster whose outbound email was blocked. I say, tough shit. Get a new provider and get over it.
There's really not much else to say, is there? Some mucky-muck at MS called up some muckey-muck at EDS and said they had a story they'd like EDS to publish as "news". EDS, seeing $$$ in their eyes, rolled over, spread its legs and begged, "Bring it on".... Nere once did the EDS muckey-muck think to ask how his own institution viewed Linux.
EDS's credibility has been sinking for a while now. I guess this pretty much puts the nail in the coffin. Eh?
I used to do tech support for friends and family. It bacame a burden when there was no apparent learning among my "customers". They still managed to get social engineered into opening virus infected spam, visiting malware links, installing malware tool-bars. They still continued using MSOE and MSIE in spite of warnings not to use them.
I now say, "I run Linux and don't remember much about Windows", then refer them to the local computer store.
Lessee if my foggy memory can reconstruct the details here. It ain't quite as simple as 4.5MB/sec.
The IBM 3278 and related terminals were just the end point of the display system. These terminals were connected via coax to a control unit: the IBM 3272 local control unit or the IBM 3271 remote control unit. There were some plug compatible makers of both control units and terminals, IIRC.
In the case of the 3272 control unit, it was channel attached to a block multiplexer channel. This was the high bandwidth attachment suggested by Alrecha. The distance from the mainframe of the 3278 display terminal was, at best a few hundreds of feet. In effect, in the same building as the mainframe.
In the case of the 3271 control unit, it was connected to the mainframe via WAN. From the mainframe end, a channel attached byte multiplexor channel sent data to a communication control unit such as a 2701, 2702 or 2703 which would send the 3270 data streams, via modem, to the 3271 control unit. Later connunications control units, the 3705 and its successors, did the same job as the 270x CUs and could handle many more lines. The data path was: mainframe to bytemux channel to communication CU to modem to WAN to modem to 3271 CU to 3278 terminal. Via modem, distances were limited by one's relationship with the phone company provided leased lines to branch offices. Bandwidth was similarly limited to what was possible line conditioning and/or with modems.
Most of my experience, as a user, with 3270 stuff was with the channel attached terminals (fast). I had some very limited experience with remote 3270 in about 1980 (slow). My last experience with 3270 related technology, about 1995, was as a user of a Sun workstation running Solaris 4-something with TN3270, a software emulator for 3270 data streams, attached to a mainframe running VM/CMS.
Marcia Peoples Halio's well researched and documented 1990 article in the Journal of Higher Education: "Student Writing: Can the Machine Maim the Message?" states that Macintosh users are as dumb as a fucking brick.
In the 15 years since the article was published, I have seen nothing to refute Ms.Halio's theory.
Alas, any first year accounting student would never have let RedHat perform the deception that it did by recognizing revenue all at once for a service to be delivered over time. It is a fundamental principle of accounting, demanded by the FASB, and accepted by any gorilla who practices accounting. That said, I am not an accountant. I have taken only one semester of accounting plus done a little independent study.
It is understandable why RedHat's CFO got sacked. Frankly, I'm not sure why he's not under indictment for fraud. Worse, were it mine to do, I'd charge the entire board of directors and officers for fraud.
That it was not a lot of money, that it only spreads the revenue recognition across some several months is the whole, the entirety, of the principle of accrual accounting. Any business must do it under similar circumstances.
I applaud their accountants [who was that again?] for insisting on the restatement.
I have used RedHat's products in the past. I might use Fedora one of these days. I think they do a good thing. They absolutely, positively have to tighten up their accounting, or they will almost certainly go bust.
In 1986, while working on a project for Amdahl in Sunnyvale California, I encountered a technique that appears to me to be exactly like MS ToDo.
The method used the "REMIND" macro to leave footprints in code not-yet-finished. Source code administration tools kept track of REMINDs in source code and reported on same.
Alas, my experience with Ph.Ds in the workforce has been less than satisfactory. I can recall one gorilla with a Ph.D at a former employer who could not seem to get anything done. Poor slob; his first manager, the poster child for the definition for PHB herself, could not seem to find a way to dismiss him. Instead, she transferred him, with no warnings or cautions to the receiving organization. He ended up working on a project I was on. It was dismal!... It took close to a year for the company to "get it" and release him.
Yet, my last boss at my last job before I retired had a Ph.D. A most brilliant fellow. Able, capable, competent, easy to work with. I suppose that in retrospect, I stayed even longer than I might otherwise have because he, and his boss too, were so easy to work with.
Recall in recent memory how IBM held on to the mainframe business (S/360 derived products) in the face of small systems products nearly sinking the company.
My own former employer, Amdahl, held on, right along with the IBM company to that same cash cow model. Amdahl was not as resilient as IBM and now is gone.... From lightbulb to number 200 on the Fortune 500, to out of business in 30 years!
At 60,000 employees in your company, your biggest challenge to getting Open Source software approved for use may not be internal. Given the brutal assaults committed by Microsoft on companies and nations considering OSS, your biggest risk is a direct frontal assault from Microsoft itself.
Been there, done that. Just that it was different players. Back in the days of the mainframe (IBM), I recall several incidents where an upstart company (Amdahl) was about to "win" product placement against IBM in some $BIGCOMPANY. IBM's response was consistent: go over the head of the person or group recommending the non-IBM solution. In many cases, this was effective. The old-boys played golf, etc. and a big gorilla on the board or in the executive suite would jawbone other executives with FUD, and the like. A good, well researched, well documented, OSS proposal can be shot down by a "well respected" executive doing some back room politicing.
Watch out for the back-stabbing tactics of the convicted felon company. They have no ethics, morals, scruples.
I recieved an Accutron, tuning fork type, as a present in 1967. I wore it for years, replacing a battery every few years, getting it cleaned every now and then. In the late 80's, while the Accutron was getting cleaned, I bought a cheap ($10) black plastic digital watch. When the Accutron came back, I put it in a drawer and forgot it.
I reaquainted myself with the Accutron recently. The battery was shot and had coroded a bit, but it cleaned up nicely and runs like new with the new battery. I think I'll wear it again.
The US Supreme Court has already ruled that a state cannot charge sales tax on goods ordered from another state; this is a direct violation of the commerce clause of the constitution. Now, suppose that the internet is declared to be present in all states simultaneously. This would now open the door to states charging sales tax on internet purchases, regardless of the nexus of the merchant.
Slashdot Mirror
Who the f*ck posted this article? -- Astroturfing his own site, no doubt.
In any case, this is the FUGLIEST site I've ever seen anywhere. Bar None!
Flash. Bah! Humbug! -- I won't visit it again. Ever.
... to naught.
I'll do my part to see that Novell never sells another Suse install anywhere I have influence. I suggest you do the same. All these asshats could see were the dollar signs in theri eyes. I hope they enjoy it while they can. I wonder if the courts would say that the outcome was obvious, therefore Novell's executives are civilly liable to the shareholders for doing the deal in the first place.
Oh my! ...
... DRM, spam, and the like.
Maybe Google can teach Intuit how not to be evil.
A few days ago I got a pre-recorded sales call to my cell phone. In a noisy environment all I got was something about mortgage loan refinancing. I hung up on 'em. The caller ID said: 949-519-1007. I later searched [googled] for the phone number and found this number 800-606-1470. When I called the number, the gorilla that answered said, "Assured Lenders". I told 'em they made a telemarketing call to a cell phone, the gorilla insulted me and hung up on me.
I don't have the ooomph to persue these a**holes to ground, so, I'll leave this as a caution.
... I believe life without posibility of parole in SuperMax, confiscation of all assets, and selling her family into slavery would almost do it.
I did. I don't want to play in that arena.
The tell you up front that they will install software ('plug-ins') on your computer. That they will share what they know about you with 'trusted partners'. That they e-pend what they can find from others about you.
No thanks.
... and not only no, but Hell NO.
I've got just one windows application to go, then this (my computing environment) is a 100% Microsoft Free Zone.
JMHO, YMMV, VWToP, HTH, HAND
$0.07USD for a tune
$0.40USD for a movie.
All of a sudden we begin seeing MS mouthing off about being open with this that or the other vendor. BFD.
What I imagine is happening is that MS is setting the world up for another round of FUD. Watch this:
MS gets 'open' with a bunch of different equipment makers and announces to the world how open they are. The press will pick it up and report on it.
In the meantime, MS remains as niggardly as ever in its relations with Linux. They expect the FUD in other areas of business to give the appearance that they are open toward Linux too.
The Linux community complains that MS are being closed with the interfaces, file formats, packet formats. MS denies it in the press pointing out how open they are in other areas. The press buys it and dismisses the Linux community as being unable to compete.
JMHO, YMMV
... with their voting systems. The leaked documents saying how they were gonna screw the customers by over pricing a print capability, having back doors where elections officials could manipulate the results, and other stuff put some fear into their customers.
Would you want to do business with a company like siebel?
I didn't think so.
I suppose MS's first step is to provide warnings to ISPs about their spamming customers and zombies. The next and obvious question is, What Comes Next?
Will MS(Hotmail) begin blocking those ISP's?
Will MS send them a notice saying something like, "... after $DATE we will bill you $BIGBUX per thousand spams. By continuing to spam our customers you agree to pay."
Frankly, it sounds good to me. Let the BigGorillas set the tone and practice for spam.
I made this up. Might happen. Might not. YMMV
No doubt, you were the asshat running an MSExchange server connected directly to the internet.
In spite of what you might think, the listing was most likely fully warranted. Your lack of due dilligence in selecting an MTA is not a reason to whine when the rest of the internet refuses your traffic.
Get over it.
... That Dell signed a [very] long term contract with Intel not to use AMD parts? Is it possible that in exchange for those contract terms that Dell got very favorable pricing for Intel parts?
In the face of an apparent better mousetrap, Dell adheres to the inferrior supplier.
Occam's Razor. The simplest answer is usually the right answer.
JMHO. YMMV.
I suppose that is the real question here.
The OP is extremely vague about exactly what IP range is involved. So, I smell a rat up front.
But, for sake of argument: Suppose the IP space had a notorious spammer in residence for a long time. Suppose the owner of that huge space had ignored complaints for a long time. Then, were I MAPS, or SPEWS, or SBL or any other block list, I'd have no qualms at all about dropping the space into a blocklist then leaving for a 2-week vacation.
As for the poster whose outbound email was blocked. I say, tough shit. Get a new provider and get over it.
There's really not much else to say, is there? Some mucky-muck at MS called up some muckey-muck at EDS and said they had a story they'd like EDS to publish as "news". EDS, seeing $$$ in their eyes, rolled over, spread its legs and begged, "Bring it on". ... Nere once did the EDS muckey-muck think to ask how his own institution viewed Linux.
EDS's credibility has been sinking for a while now. I guess this pretty much puts the nail in the coffin. Eh?
I used to do tech support for friends and family. It bacame a burden when there was no apparent learning among my "customers". They still managed to get social engineered into opening virus infected spam, visiting malware links, installing malware tool-bars. They still continued using MSOE and MSIE in spite of warnings not to use them.
I now say, "I run Linux and don't remember much about Windows", then refer them to the local computer store.
Lessee if my foggy memory can reconstruct the details here. It ain't quite as simple as 4.5MB/sec.
The IBM 3278 and related terminals were just the end point of the display system. These terminals were connected via coax to a control unit: the IBM 3272 local control unit or the IBM 3271 remote control unit. There were some plug compatible makers of both control units and terminals, IIRC.
In the case of the 3272 control unit, it was channel attached to a block multiplexer channel. This was the high bandwidth attachment suggested by Alrecha. The distance from the mainframe of the 3278 display terminal was, at best a few hundreds of feet. In effect, in the same building as the mainframe.
In the case of the 3271 control unit, it was connected to the mainframe via WAN. From the mainframe end, a channel attached byte multiplexor channel sent data to a communication control unit such as a 2701, 2702 or 2703 which would send the 3270 data streams, via modem, to the 3271 control unit. Later connunications control units, the 3705 and its successors, did the same job as the 270x CUs and could handle many more lines. The data path was: mainframe to bytemux channel to communication CU to modem to WAN to modem to 3271 CU to 3278 terminal. Via modem, distances were limited by one's relationship with the phone company provided leased lines to branch offices. Bandwidth was similarly limited to what was possible line conditioning and/or with modems.
Most of my experience, as a user, with 3270 stuff was with the channel attached terminals (fast). I had some very limited experience with remote 3270 in about 1980 (slow). My last experience with 3270 related technology, about 1995, was as a user of a Sun workstation running Solaris 4-something with TN3270, a software emulator for 3270 data streams, attached to a mainframe running VM/CMS.
Times change. My recall could be faulty. YMMV.
Marcia Peoples Halio's well researched and documented 1990 article in the Journal of Higher Education: "Student Writing: Can the Machine Maim the Message?" states that Macintosh users are as dumb as a fucking brick.
In the 15 years since the article was published, I have seen nothing to refute Ms.Halio's theory.
Alas, any first year accounting student would never have let RedHat perform the deception that it did by recognizing revenue all at once for a service to be delivered over time. It is a fundamental principle of accounting, demanded by the FASB, and accepted by any gorilla who practices accounting. That said, I am not an accountant. I have taken only one semester of accounting plus done a little independent study.
It is understandable why RedHat's CFO got sacked. Frankly, I'm not sure why he's not under indictment for fraud. Worse, were it mine to do, I'd charge the entire board of directors and officers for fraud.
That it was not a lot of money, that it only spreads the revenue recognition across some several months is the whole, the entirety, of the principle of accrual accounting. Any business must do it under similar circumstances.
I applaud their accountants [who was that again?] for insisting on the restatement.
I have used RedHat's products in the past. I might use Fedora one of these days. I think they do a good thing. They absolutely, positively have to tighten up their accounting, or they will almost certainly go bust.
In 1986, while working on a project for Amdahl in Sunnyvale California, I encountered a technique that appears to me to be exactly like MS ToDo.
The method used the "REMIND" macro to leave footprints in code not-yet-finished. Source code administration tools kept track of REMINDs in source code and reported on same.
This patent cannot stand.
Alas, my experience with Ph.Ds in the workforce has been less than satisfactory. I can recall one gorilla with a Ph.D at a former employer who could not seem to get anything done. Poor slob; his first manager, the poster child for the definition for PHB herself, could not seem to find a way to dismiss him. Instead, she transferred him, with no warnings or cautions to the receiving organization. He ended up working on a project I was on. It was dismal! ... It took close to a year for the company to "get it" and release him.
Yet, my last boss at my last job before I retired had a Ph.D. A most brilliant fellow. Able, capable, competent, easy to work with. I suppose that in retrospect, I stayed even longer than I might otherwise have because he, and his boss too, were so easy to work with.
Recall in recent memory how IBM held on to the mainframe business (S/360 derived products) in the face of small systems products nearly sinking the company.
... From lightbulb to number 200 on the Fortune 500, to out of business in 30 years!
My own former employer, Amdahl, held on, right along with the IBM company to that same cash cow model. Amdahl was not as resilient as IBM and now is gone.
I got mine. You get yours.
Been there, done that. Just that it was different players. Back in the days of the mainframe (IBM), I recall several incidents where an upstart company (Amdahl) was about to "win" product placement against IBM in some $BIGCOMPANY. IBM's response was consistent: go over the head of the person or group recommending the non-IBM solution. In many cases, this was effective. The old-boys played golf, etc. and a big gorilla on the board or in the executive suite would jawbone other executives with FUD, and the like. A good, well researched, well documented, OSS proposal can be shot down by a "well respected" executive doing some back room politicing.
Watch out for the back-stabbing tactics of the convicted felon company. They have no ethics, morals, scruples.
JMHO.
I reaquainted myself with the Accutron recently. The battery was shot and had coroded a bit, but it cleaned up nicely and runs like new with the new battery. I think I'll wear it again.
The US Supreme Court has already ruled that a state cannot charge sales tax on goods ordered from another state; this is a direct violation of the commerce clause of the constitution. Now, suppose that the internet is declared to be present in all states simultaneously. This would now open the door to states charging sales tax on internet purchases, regardless of the nexus of the merchant.