Perhaps. But was the hard part configuring LVS, or configuring your web apps to play nice in a even more-stateless enviroment? Its been a few years, but I suspect that if necessary, I could get up and running a pair of (fall over) LVS director boxes, and configure a handfull of backend systems in a good day. Tweeking the backend systems, testing... thats another story; but that time would be consistant across LVS and commercial solutions.
Application Service Providers are not new. Selling cycles, selling services provided by hardware and software; these are not new business models. Compuserve started as an ASP in the 1960s. Multics, started in the 1960s was writen specificly to be used for a "computer utility": an ASP.
How is it that they missed this the first two trys?
unlimited access, upgrade protection and technical support...
Is not an unusual concept, or at least not with the Novell pricing scheme. Any price list for a Novell product includes: media, new/upgrade license, 1 year "upgrade protection" and "full term" "upgrade protection". "upgrade protection" provides both technical support for the product in question and, as the name suggests, automatic upgrades to newer releases in that product line.
Ive never been clear on how much "upgrade protection" a simple license gets you, or how long a "full term" is, but it stands to reason that this anouncement is not the purchase of licenses (a one time cost) but a contract for licenses today and "upgrade protection" in the future. Likely with custom terms that dont quite fit in with Novells "off the shelf" licenses, but close enough to what they do usualy that they are resaonable sure that this deal will be profitable.
Well, actually, MSA does not require authentication. The MSA RFC can be sumerized as "SMTP with the right to less strict rules (missing headers) and more strict policy (site specific)". There are only two MUST clauses in MSA:
4.2. Ensure All Domains are Fully-Qualified
The MSA MUST ensure that all domains in the envelope are fully-
qualified.
If the MSA examines or alters the message text in way, except to add
trace header fields [SMTP-MTA], it MUST ensure that all domains in
address header fields are fully-qualified.
--snip--
8.1. Add 'Sender'
The MSA MAY add or replace the 'Sender' field, if the identity of the
sender is known and this is not given in the 'From' field.
The MSA MUST ensure that any address it places in a 'Sender' field is
in fact a valid mail address.
And the second one is conditional if you decide to add a Sender field, which is optional.
A reasonable mailserver can enforce varrying policy on: existance of authentication, source IP address. The only reason to run a "MSA" server is if you have a network clients who expect to talk to MSA.. So far as I know, none exist, and assume they are talking to a straigh-ESMTP system, generating themselves the headers which MSA MAY add.
Actually, as for Aspirin, Bayer lost it as part of The Versailles Treaty that ended WWII. (At the same time they also lost "Heroin"). At least in some countries, anyway. In Canada Aspirin is still a TM...
It wasn't Canadians, it was the British. And it wasn't the Whitehouse until after it burned down, and some low-bid contractor "fixed" the building by painting it white.
Well, it may have been sarcastic, but it does bring up a good point. "Show me the code" is the stock answer to users requests for features/bug fixes.
One of RMSs fixes was "Lets fork OOo". You want to fork OOo, RMS? Fine, go crazy. But the reality is that at least for the last decade, the FSF hasn't been a significant contributor to GPLd software, or even the GNU Project. GCC is built mainly by developers paid by places that are not the FSF. By all accounts, the overwhelming majority of OOo code is done by Sun employees, and by all accounts OOo is a complex beast all but impossible for one person to understand compleatly, and undoubtably having a very steep learning curve for new devs. So who would have built this forked OOo? Not FSF, they seem to be fresh out of developers. Not the "communinity", there isnt anyone contributing to the mainline OOo.
The FSF may be a very effective political movement. And they foster and provide support for some amazing projects. But they have contributed supprisingly little technology in a long while now. At the top of the list of technology they have not delivered, or are delivering very slowly and not as good as the alternatives, is Hurd.
Well, Windows Lite (whatever) is Windows with slightly different userland apps, and somewhat castrated by licensing - not by technology. The incremental cost to product 'Lite is basiclly 0 to MS. Getting Wine to a level that Microsoft could call "comptabale" with Windows is a huge undertaking. Ya, it can do a lot. And ya, other people are selling it as "compatable", and ya, MS is not at the top of the list when you think of "compatability", even within their own products. But they sure cant call Wine compatable today, and wont be able to without a massive amount of work. And even if they could, such a step is compleatly contrary to their entire practice of tying products together. If anything, MS would be more likely to drop the cost of Windows to $0 to protect their apps, rather then trying to port their apps (with Wine(lib)) to alternate $0 OSs. While Windows may never get to $0, the existance of "Lite" is an indication that MS is, to some degree, moving in this direction.
As for Novell supporting their products on other OSs "now", you have a unusual definition of "now". NDS runs on about as many diverse OS/hardware systems as any commercial products, and and ran on at least Windows almost since the begining (10 years ago). Groupwise has always been cross platform - its native system not being Netware, ever. The server bits of ZenWorks, also multi platform for a fairly long time. And no, they are not migratign Netware to a Linux base, they are (have, actually, its done) migrating all Netware services to both/either a Netware or Linux base. There is a subtle but significant difference there.
While SuSE was a big developer/user/promoter of KDE, Ximian was the single biggest developer/user/promoter of Gnome. Currently, it seems that Novell has decided they are both wrong, and is going with Mono. Sadly, I am only half joking.
As for MAC, not even hearing of this thing before today, Im going to side with Novell. SELinux was developed at the NSA as a research project. While Im not saying that security is the opposite of usability, it is fair to say that a NSA research project is about as far detached from the requirements of reality as you can get. Novell, Netware, NDS, NSS, they have forgotten more about security and the real world - the real business world, then RedHat knows. Novell could taken SELinux for free, NDS-ized it, iManaged-ized it, YaST-ized it and made it distinct from any RH offering. But they went out of their way to buy a system that compeats with SELinux. Either it is significantly better today, or it will more easily be N-ized tomorrow, so it will be radically better next year.
Does anyone have a copy of their "what we're running" page? I remember reading a fairly detailed description of the hardware they had, but for some reason the number 10GB of RAM is stuck in my head.. That was a crapload back then, now not so much. In 5 years MSI/Nvidia will have a 10GB video card.
Try guru.com or rentacoder.com.. The former is "high end" requiring some serious creds for the more interesting projects, the later has a increadably horrible interface, but has far far more projects.
Ive been in enough classes this year (well below my level.. dammit, I need the "letters") that Ive come to the conclusion that introductory programming courses are taught all wrong.
Write 5 lines. Write 20 lines. Write 100 lines. Of useless and pointless code.
What should be done is: Take this 1000 line programme. Add on 5 lines. Add on 20 lines. Add on 100 lines. Beacuse that would require being able to read code, too. Being able to understand what is already there is frequently more then half the battle. Saying "What the fuck does this mean?" a few dozen times is the only way to get to write comments. Being a sysadmin, rather then a full time programmer, this took me litteraly years to learn. And it was usualy "What the fuck were you doing here, brain? Dammit, one of these days were going to have to start commenting our code."
About 6 months ago, I read through a project request on one of these ebay-for-coders sites. Language optional; 1 comment per 5 LOC, but if using Perl, 1 comment per 2 LOC.. With requrements like that you are only asking to get BS comments like "Print X to the console".
Slashdot Mirror
Perhaps. But was the hard part configuring LVS, or configuring your web apps to play nice in a even more-stateless enviroment? Its been a few years, but I suspect that if necessary, I could get up and running a pair of (fall over) LVS director boxes, and configure a handfull of backend systems in a good day. Tweeking the backend systems, testing... thats another story; but that time would be consistant across LVS and commercial solutions.
And Ill say it again.
Application Service Providers are not new. Selling cycles, selling services provided by hardware and software; these are not new business models. Compuserve started as an ASP in the 1960s. Multics, started in the 1960s was writen specificly to be used for a "computer utility": an ASP.
How is it that they missed this the first two trys?
My prefered quote would be: "Having a meeting with Bill Gates is like going on a date with Mike Tyson: you should expect to get raped"
Is not an unusual concept, or at least not with the Novell pricing scheme. Any price list for a Novell product includes: media, new/upgrade license, 1 year "upgrade protection" and "full term" "upgrade protection". "upgrade protection" provides both technical support for the product in question and, as the name suggests, automatic upgrades to newer releases in that product line.
Ive never been clear on how much "upgrade protection" a simple license gets you, or how long a "full term" is, but it stands to reason that this anouncement is not the purchase of licenses (a one time cost) but a contract for licenses today and "upgrade protection" in the future. Likely with custom terms that dont quite fit in with Novells "off the shelf" licenses, but close enough to what they do usualy that they are resaonable sure that this deal will be profitable.
If they are holding stock, then they arn't daytraders.
A reasonable mailserver can enforce varrying policy on: existance of authentication, source IP address. The only reason to run a "MSA" server is if you have a network clients who expect to talk to MSA.. So far as I know, none exist, and assume they are talking to a straigh-ESMTP system, generating themselves the headers which MSA MAY add.
Actually, as for Aspirin, Bayer lost it as part of The Versailles Treaty that ended WWII. (At the same time they also lost "Heroin"). At least in some countries, anyway. In Canada Aspirin is still a TM...
*BZZT* Wrong. We are talking about the War of 1812, not the American Revolution. HTH, HAND
It wasn't Canadians, it was the British. And it wasn't the Whitehouse until after it burned down, and some low-bid contractor "fixed" the building by painting it white.
The FedEx tracking number?
Well, it may have been sarcastic, but it does bring up a good point. "Show me the code" is the stock answer to users requests for features/bug fixes.
One of RMSs fixes was "Lets fork OOo". You want to fork OOo, RMS? Fine, go crazy. But the reality is that at least for the last decade, the FSF hasn't been a significant contributor to GPLd software, or even the GNU Project. GCC is built mainly by developers paid by places that are not the FSF. By all accounts, the overwhelming majority of OOo code is done by Sun employees, and by all accounts OOo is a complex beast all but impossible for one person to understand compleatly, and undoubtably having a very steep learning curve for new devs. So who would have built this forked OOo? Not FSF, they seem to be fresh out of developers. Not the "communinity", there isnt anyone contributing to the mainline OOo.
The FSF may be a very effective political movement. And they foster and provide support for some amazing projects. But they have contributed supprisingly little technology in a long while now. At the top of the list of technology they have not delivered, or are delivering very slowly and not as good as the alternatives, is Hurd.
It is entirely possible that it did say "Porno" the first time you read it, only to be silently "edited" after the fact".
People who have email addresses in the form of user@sun.com use com.sun classes regularaly.
Well, Windows Lite (whatever) is Windows with slightly different userland apps, and somewhat castrated by licensing - not by technology. The incremental cost to product 'Lite is basiclly 0 to MS. Getting Wine to a level that Microsoft could call "comptabale" with Windows is a huge undertaking. Ya, it can do a lot. And ya, other people are selling it as "compatable", and ya, MS is not at the top of the list when you think of "compatability", even within their own products. But they sure cant call Wine compatable today, and wont be able to without a massive amount of work. And even if they could, such a step is compleatly contrary to their entire practice of tying products together. If anything, MS would be more likely to drop the cost of Windows to $0 to protect their apps, rather then trying to port their apps (with Wine(lib)) to alternate $0 OSs. While Windows may never get to $0, the existance of "Lite" is an indication that MS is, to some degree, moving in this direction.
As for Novell supporting their products on other OSs "now", you have a unusual definition of "now". NDS runs on about as many diverse OS/hardware systems as any commercial products, and and ran on at least Windows almost since the begining (10 years ago). Groupwise has always been cross platform - its native system not being Netware, ever. The server bits of ZenWorks, also multi platform for a fairly long time. And no, they are not migratign Netware to a Linux base, they are (have, actually, its done) migrating all Netware services to both/either a Netware or Linux base. There is a subtle but significant difference there.
While SuSE was a big developer/user/promoter of KDE, Ximian was the single biggest developer/user/promoter of Gnome. Currently, it seems that Novell has decided they are both wrong, and is going with Mono. Sadly, I am only half joking.
As for MAC, not even hearing of this thing before today, Im going to side with Novell. SELinux was developed at the NSA as a research project. While Im not saying that security is the opposite of usability, it is fair to say that a NSA research project is about as far detached from the requirements of reality as you can get. Novell, Netware, NDS, NSS, they have forgotten more about security and the real world - the real business world, then RedHat knows. Novell could taken SELinux for free, NDS-ized it, iManaged-ized it, YaST-ized it and made it distinct from any RH offering. But they went out of their way to buy a system that compeats with SELinux. Either it is significantly better today, or it will more easily be N-ized tomorrow, so it will be radically better next year.
Third mellenium, at least, dumbass. God is not a EE and does not count from 0.
I dont know... There probabaly is a bunch of OS/2 v0.0.2 code kicking around Seattle.
To round out the story, FC-1 was more or less the non-existant RH 10, renamed.
Where are my teledildonics? We were promised teledildonics!
Donut Wednesdays? WTF? Do tell....
/me registers amifairandbalancedornot.com
Does anyone have a copy of their "what we're running" page? I remember reading a fairly detailed description of the hardware they had, but for some reason the number 10GB of RAM is stuck in my head.. That was a crapload back then, now not so much. In 5 years MSI/Nvidia will have a 10GB video card.
Thats the beauty of being a University. The students pay you!.
Try guru.com or rentacoder.com .. The former is "high end" requiring some serious creds for the more interesting projects, the later has a increadably horrible interface, but has far far more projects.
Ive been in enough classes this year (well below my level.. dammit, I need the "letters") that Ive come to the conclusion that introductory programming courses are taught all wrong.
Write 5 lines. Write 20 lines. Write 100 lines. Of useless and pointless code.
What should be done is: Take this 1000 line programme. Add on 5 lines. Add on 20 lines. Add on 100 lines. Beacuse that would require being able to read code, too. Being able to understand what is already there is frequently more then half the battle. Saying "What the fuck does this mean?" a few dozen times is the only way to get to write comments. Being a sysadmin, rather then a full time programmer, this took me litteraly years to learn. And it was usualy "What the fuck were you doing here, brain? Dammit, one of these days were going to have to start commenting our code."
About 6 months ago, I read through a project request on one of these ebay-for-coders sites. Language optional; 1 comment per 5 LOC, but if using Perl, 1 comment per 2 LOC.. With requrements like that you are only asking to get BS comments like "Print X to the console".