As "final stabilization will be left up to the companies that provide Linux distributions." does this not introduce the risk that the final versions will begin to diverge and over time a RedHat OS, a SuSe OS etc will emerge?
Linux is an OS kernel. We already have a RedHat OS & a SuSe OS. This change will not influence whether the kernel that they use will diverge over time.
Will we have a VHS vs Betamax style battle in Linux?
The First Indian Uprising of 1857 The Indian Mutiny (also known as the Sepoy Mutiny) as known to the British or The First War Of Indian Independence as known to the Indians was a period of uprising in northern and central India against British rule in 1857-1858. It is also known as the Sepoy Rebellion, the Great Mutiny, and the Revolt of 1857. It is widely acknowledged to be the first-ever united rebellion against colonial rule in India.
Causes The most famous reason for this mutiny is the use of cow and pig fat in.557 calibre Pattern 1853 Enfield (P/53) rifle cartridges. Since soldiers had to break the cartridges with their teeth before they could load them into their rifles, this was offensive to Hindu and Muslim soldiers, who considered tasting beef and pork to be against their respective religious tenets. In February 1857 sepoys refused to use their new cartridges. The British claimed to have replaced the cartridges with new ones and tried to make sepoys make their own grease from beeswax and vegetable oils but the rumor persisted.
Mangal Pande and the march to Delhi In March 1857 Mangal Pande of the 34th Native Infantry attacked his British sergeant, wounded an adjutant. General Hearsay, who said Pande was in some kind of "religious frenzy" ordered a jemadar to arrest him but the jemadar refused. Mangal Pande then turned the gun against himself and used his foot to try to pull the trigger to shoot himself. He failed, was captured and then hanged on April 7 along with the jemadar. The whole regiment was dismissed as a collective punishment. Other sepoys felt this was too harsh.
On the 10th of May when the 11th and 20th cavalry assembled they broke rank and turned on their commanding officers. They then liberated the 3rd Regiment. The rebelling forces were then engaged by the remaining British forces in Meerut. Meerut had the largest percentage of British troops of every station in India 2,038 European troops versus 2,357 sepoys. The British side even had 12 field guns while the sepoys lacked an artillery. The British forces could have stopped the sepoys from marching on Delhi.
On the 11th of May they reached Delhi. They were joined by other Indians from the local bazaar. Here they attacked and captured the Red Fort (Lal Qila) which was the residence of Bahadur Shah Zafar. The sepoys demanded that he reclaim his throne. At first he was reluctant but eventually he agreed to the demands and became the leader of the rebellion.
About the same time in Jhansi, the army rebelled and killed the British Army Officers. This led to a left Rani Laxmibai, the queen of Jhansi, to defend herself and her kingdom. In 1858, when the British army once again marched towards Jhansi, the Rani assembled an army of 14,000 volunteers to fight the invaders. The war lasted 2 weeks but eventually the British won. The queen escaped on horseback to the fortress of Kalpi. Here she organized a few other kingdoms to rebel against the British. These rebel forces captured Gwalior from the British. The British placed a prize of Rs. 20,000 on the capture of Rani Laxmibai.
I think the answer is that it would offend religious Hindus (not all Indians), and they would probably not use cow protein in the final product.
Dude, what is your lawyer doing? The FBI might not be able to stop them by throwing them in jail, but you can recoup general damages + punitive damages - 30%, right?
If this is an otherwise legitimate competitor (they aren't about to flee the country), then you deal with this in civil court.
ASCAP and BMI In 1914 the American Society of Composers, Authors and Publishers (ASCAP) was established to protect recording artists from unsanctioned use of their material. ASCAP used a blanket licensing agreement to collect a pre-set annual fee from anyone using its members' material for any commercial purpose. The money was divided among ASCAP artists. As major players in the radio industry became more interested in broadcasting recorded work, ASCAP reinforced its control over distribution. Artists who were not ASCAP members had little hope of exposing their work to wide audiences.
During the recording boom of the late 30s and early 40s, ASCAP had doubled the fees they charged radio stations. In the midst of court battles and the dearth of music not protected by ASCAP, frustrated broadcasters formed their own blanket licensing system, Broadcast Music, Incorporated (BMI), in 1939. The BMI camp sought alternatives to ASCAP acts. In the process BMI would later become the dominant force in the discovery and marketing of a new sound that would breed a new culture.
The FSF, though the GNU project has without a douby produced a lot of code, and lots of others have transfered their IP to them. But GPL does not necessaraly lead to GNU/FSF.
Yes, the GPL does kindof lead to the FSF in one particular regard. If your version of the GPL says "You can release this under GPL 2.0 or any later version" then the FSF holds a special power to relicense your code via GPL 3.0 or GPL 4.0, which we trust to also be Free.
The dude's point is that a villain could bribe/blackmail the FSF's board, have them vote to approve a GPL 5.0 which reads "Must be licensed or distributed via Villains, LLC." or someshit. Then Villains, LLC could release proprietary copies of any GPLed software. It's not necessarily the weakest link, but it's a link. As far as I understand (not far), that link could be broken.
Well, when your only remaining profitable business plan is to steal, then a moral person would say "I have no business plan, and no hope for profitability. Fire sale."
I had actually never seen this point made before, even in another story.
Me neither, but it's not exactly groundbreaking: RMS believes that every single line of code on your computer should be Free Software, as a moral imperative, and he's explained why he feels that way.
Nope, its just more of the same old "the GPL is perfect and everything else sucks, please pay attention to me" crap from RMS. The PHP license is more free than the GPL, and he doesn't like that.
Uh, that's not what he says according to the quote I found. He's saying that the PHP license is acceptable for PHP projects. If he had a problem with PHP's level of free-ness, he'd say it was unnacceptable for any purposes.
RMS is unreasonable enough as it is. No need to exaggerate.
Re:How do open source projects change lisences?
on
PHP Not Moving To The GPL
·
· Score: 5, Informative
Many projects require that you turn over the copyright to your code when you submit it. Those projects do not need to contact submitters in order to change the license.
The copyright to ReiserFS, for example, is completely owned by the ReiserFS dude. He can ship it under whatever license he likes. One of those licenses is the GPL. If you receive it under the GPL, then you have all the rights guaranteed to you via the GPL, so you can *only* distribute it under the GPL. Because you don't own the copyright.
Linux, on the other hand, does not require submitters to turn over their copyright on their code submissions. If Linus wanted to release Linux under the BSD license, he would need permission from every single person that has their copyrighted code in Linux. He did this intentionally, as a guarantee that it would never happen.
The FSF does require copyright on all it's code, which means that if someone sued the billy-blue jeepers out of the FSF, in theory they could acquire the assets of the FSF, and release closed-source versions of Emacs or something. The FSF, however, has a greater standing should they ever go to court to enforce the GPL for one of their projects.
Of course, the kids at the FSF are pretty sharp. They may have some method of ensuring that their code will never fall into SCO's hands or something. Dunno.
Sometimes mods will mark something "redundant" when they feel that the point has been made a million other times and is perfectly well understood, even if the point hasn't been made on this particular story.
Is RMS' complaint that PHP's license is too open & BSD-like, or is his complaint that PHP's license is too closed and Sun-like?
If it's too BSD-like, then this is a completely meaningless debate. CEO dude is right, PHP's users won't care. If it's too Sun-like, then there's something to talk about.
PHP License, Version 3.0 This license is used by most of PHP4. It is a non-copyleft free software license which is incompatible with the GNU GPL. We recommend that you not use this license for anything except PHP add-ons.
That's still vague. What's the hiccup? It looks like RMS has no ideological problem with this license. Is there a new, worse license?
Neither WinFS nor Spotlight entail changes to NTFS & HFS+. WinFS and Spotlight are both databases housed on ordinary filesystems.
Both WinFS and Spotlight will be updated by the filesystem drivers. WinFS and Spotlight will have different features. The features promised for WinFS are more attractive (for developers), but Spotlight will be here & usable sooner.
What is wrong with having the option to have an automatically updated and searchable filesystem data on your machine or better your LAN?
You have missed his point.
There are several ways to implement the feature you describe. One is with a database-driven filesystem. One is with an ordinary filesystem that is adequately indexed. Apple looks to have implemented very good indexing of an ordinary filesystem.
Spotlight will give you all the features you describe, but it will not be a database-driven filesystem.
WinFS would be a database-driven filesystem, which may deliver significantly more powerful features to developers, but it will not be deployed until long, long after Spotlight. If ever.
I'd already read the article you link to. It is what I base my point on. There are additional metadata capabilities in Tiger, but they are not part of the fileystem. Your ID3 tags are not being stored in HFS+ metadata. Everyone who thinks that HFS+ will have user-extendable metadata or a database-driven filesystem will be disappointed. It is not a database filesystem. That's perfectly OK with me.
As to the claim that Apple is just doing all front-end stuff while MS is actually doing technology, I call baloney on that one.
You seem to misunderstand. I called it MS's "pie in the sky" technology for a reason. My analogy is a good one.
I agree that there are big differences, though: Spotlight is based on proven technology and will surely arrive in 2005, while WinFS is a huge gamble, will increase costs dramatically (both licensing and maintenance), and will also arrive no earlier than 2006, without actually being based on proven tech at all.
You say that as if you had made the point, rather than me.
Tiger, the new release of MacOS X, is due in 2005 with its brand new database filesystem Spotlight[7], modernised video services and many other features.
It's not a database filesystem. I wrote an entry in my journal on the subject, and I'd quote it here if/. weren't so laggy right now. But Spotlight is just indexing the same metadata that is in HFS+ under Jaguar, plus data that it pulls out of the file, not out of the filesystem. There is significant improvement in the mechanism and the interface, but it is not a "database filesystem."
Comparing WinFS and Spotlight is like comparing.NET and.Mac - Apple is delivering the features that end users will receive from MS's pie in the sky technology, without implementing the actual technology. (And Jobs actually compared WinFS to Spotlight in the keynote, just as he actually compared.NET to.Mac in the keynote that killed iTools.)
No, I'm not dissing Apple and I'm not dissing Microsoft. I'm just saying...
I'm talking about VS.NET & C#, which is comparable to Eclipse & Java. It does not have Edit & Continue because their C# compiler does not support the requisite functions.
VS/C++ and VS/VB are not comparable in the same way to Eclipse/Java.
I will continue to do so until someone makes an IDE on Linux that compares to Visual Studio (and no, Eclipse is not that IDE, especially for non-Java projects).
Well, I agree with you completely about non-Java projects. However, I promise you that the C#/VS.NET developers feel heat from Java/Eclipse. They feel that it compares well. Err, actually I haven't asked in a while, but about a year ago they seemed to feel that Eclipse was improving in leaps and bounds and starting to kick their asses. I think they're getting embarrassed about the lack of Edit & Continue.
(And this is completely unrelated to how the managers & marketting & strategy people might feel. They may feel zero heat. Iduno. But the developers want to be making the best possible product, so market share doesn't make them rest easy.)
As "final stabilization will be left up to the companies that provide Linux distributions." does this not introduce the risk that the final versions will begin to diverge and over time a RedHat OS, a SuSe OS etc will emerge?
Linux is an OS kernel. We already have a RedHat OS & a SuSe OS. This change will not influence whether the kernel that they use will diverge over time.
Will we have a VHS vs Betamax style battle in Linux?
If so, it will not be due to this change.
Any other questions?
Hrm. From that article it seems that the prohibition might not be against using cow products, but rather the act of consuming cow parts.
I guess I don't know how Hindus would feel about the beef drive.
Ask Mangal Pande how he felt:I think the answer is that it would offend religious Hindus (not all Indians), and they would probably not use cow protein in the final product.
Dude, what is your lawyer doing? The FBI might not be able to stop them by throwing them in jail, but you can recoup general damages + punitive damages - 30%, right?
If this is an otherwise legitimate competitor (they aren't about to flee the country), then you deal with this in civil court.
The FSF, though the GNU project has without a douby produced a lot of code, and lots of others have transfered their IP to them. But GPL does not necessaraly lead to GNU/FSF.
Yes, the GPL does kindof lead to the FSF in one particular regard. If your version of the GPL says "You can release this under GPL 2.0 or any later version" then the FSF holds a special power to relicense your code via GPL 3.0 or GPL 4.0, which we trust to also be Free.
The dude's point is that a villain could bribe/blackmail the FSF's board, have them vote to approve a GPL 5.0 which reads "Must be licensed or distributed via Villains, LLC." or someshit. Then Villains, LLC could release proprietary copies of any GPLed software. It's not necessarily the weakest link, but it's a link. As far as I understand (not far), that link could be broken.
Mod parent up interesting.
May or may not be what SCO is doing, but it's still interesting.
Mod parent up.
Mod parent up.
I'm just waiting for Darl to claim that he's written several operas.
Well, when your only remaining profitable business plan is to steal, then a moral person would say "I have no business plan, and no hope for profitability. Fire sale."
An immoral person might go ahead and steal.
Actually, I'm in favor of ironic moderation. That was pretty funny.
I had actually never seen this point made before, even in another story.
Me neither, but it's not exactly groundbreaking: RMS believes that every single line of code on your computer should be Free Software, as a moral imperative, and he's explained why he feels that way.
RMS is unreasonable enough as it is. No need to exaggerate.
Many projects require that you turn over the copyright to your code when you submit it. Those projects do not need to contact submitters in order to change the license.
The copyright to ReiserFS, for example, is completely owned by the ReiserFS dude. He can ship it under whatever license he likes. One of those licenses is the GPL. If you receive it under the GPL, then you have all the rights guaranteed to you via the GPL, so you can *only* distribute it under the GPL. Because you don't own the copyright.
Linux, on the other hand, does not require submitters to turn over their copyright on their code submissions. If Linus wanted to release Linux under the BSD license, he would need permission from every single person that has their copyrighted code in Linux. He did this intentionally, as a guarantee that it would never happen.
The FSF does require copyright on all it's code, which means that if someone sued the billy-blue jeepers out of the FSF, in theory they could acquire the assets of the FSF, and release closed-source versions of Emacs or something. The FSF, however, has a greater standing should they ever go to court to enforce the GPL for one of their projects.
Of course, the kids at the FSF are pretty sharp. They may have some method of ensuring that their code will never fall into SCO's hands or something. Dunno.
Sometimes mods will mark something "redundant" when they feel that the point has been made a million other times and is perfectly well understood, even if the point hasn't been made on this particular story.
It's better than an "overrated" mod, isn't it?
If it's too BSD-like, then this is a completely meaningless debate. CEO dude is right, PHP's users won't care. If it's too Sun-like, then there's something to talk about.
Oh. Here's what RMS says:That's still vague. What's the hiccup? It looks like RMS has no ideological problem with this license. Is there a new, worse license?
Then my comparison is full of crap. Redo:
Neither WinFS nor Spotlight entail changes to NTFS & HFS+. WinFS and Spotlight are both databases housed on ordinary filesystems.
Both WinFS and Spotlight will be updated by the filesystem drivers. WinFS and Spotlight will have different features. The features promised for WinFS are more attractive (for developers), but Spotlight will be here & usable sooner.
What is wrong with having the option to have an automatically updated and searchable filesystem data on your machine or better your LAN?
You have missed his point.
There are several ways to implement the feature you describe. One is with a database-driven filesystem. One is with an ordinary filesystem that is adequately indexed. Apple looks to have implemented very good indexing of an ordinary filesystem.
Spotlight will give you all the features you describe, but it will not be a database-driven filesystem.
WinFS would be a database-driven filesystem, which may deliver significantly more powerful features to developers, but it will not be deployed until long, long after Spotlight. If ever.
Comparing WinFS and Spotlight is like comparing
No, I'm not dissing Apple and I'm not dissing Microsoft. I'm just saying...
I'm talking about VS.NET & C#, which is comparable to Eclipse & Java. It does not have Edit & Continue because their C# compiler does not support the requisite functions.
VS/C++ and VS/VB are not comparable in the same way to Eclipse/Java.
I will continue to do so until someone makes an IDE on Linux that compares to Visual Studio (and no, Eclipse is not that IDE, especially for non-Java projects).
Well, I agree with you completely about non-Java projects. However, I promise you that the C#/VS.NET developers feel heat from Java/Eclipse. They feel that it compares well. Err, actually I haven't asked in a while, but about a year ago they seemed to feel that Eclipse was improving in leaps and bounds and starting to kick their asses. I think they're getting embarrassed about the lack of Edit & Continue.
(And this is completely unrelated to how the managers & marketting & strategy people might feel. They may feel zero heat. Iduno. But the developers want to be making the best possible product, so market share doesn't make them rest easy.)
(which are mammals btw)
They're some of our closest non-primate relatives, also having descended from tree shrews.
And it looks like it has a slightly nicer screen - the LCD looks almost flush with the front bezel.
Good one.
Sure, I just don't understand why anyone would go out of their way to listen to it. You know, whatever floats your boat.