this time I don't think the problem it's the RIAA. iTunes does not make any money Apple earns money from selling the hardware (iPod e c.) So they can never let to play their songs withouth their buying anything else from them
this remind me of a country that has been bombed and invaded on the base it had all the equipment to be an imminent threath. Sadly it was not true. Sadly this is not a joke.
In an election with 4 candidates there would be 4 transparent tubes, each coated with an opaque wrapper. Voters would insert a coin-shaped plastic token into the cylinder representing their favourite candidate, and when the votes need to be counted the opaque wrapper would be removed to simply show which candidate had won. It's obvious, completely transparent and recounts are unnecessary because the winner should be obvious to all.
the main problem would be to line 100 milions voters
If you really want to get paranoid about something, get paranoid about money, which passes from hand, to hand, to hand. Your own desk doesn't really rank that high on the risk list, seeing as how its population is largely an extension of your own.
btw if anybody wants to get rid of his money, I can help
100. The contribution of the Journaling File System ("JFS") was done in a series of "drops" of AIX code identified as "reference files" inside Linux. The first such drop occurred on or about February 2000, with multiple additions and significant follow-up work by IBM since that time to adapt AIX/JFS for enterprise use inside Linux. These drops of reference files do not necessarily become part of the source code in the Linux kernel, but rather are public displays of the Protected Materials so that anyone has access to them and can use them to construct similar file in Linux. The first drop contains (a) a partially functioning port, or transfer, of JFS from AIX to Linux; (b) a set of reference directories (named ref/) which contain the AIX reference version of AIX/JFS; (c) AIX/JFS-related utility files used to maintain and upkeep AIX/JFS; and (d) a set of directories (named directory ref_utils/) which contain the AIX reference version of utilities. Copies of AIX/JFS files into Linux are shown in Table A, below. Table A compares a 1999 version of AIX and shows the following similarities, demonstrating copying of code, structures and/or sequences.
These transfers of AIX/JFS to Linux are in violation of the IBM Related Agreements, and are an improper use of AIX for adaptation to a general operating system.
101. IBM has also improperly transferred a UNIX/AIX-based enterprise volume management system ("AIX/EVMS") to Linux. Again, this was done by IBM to transfer enterprise-class capabilities from AIX to Linux, and was a violation of the IBM Related Agreements and IBM's promise not to adapt AIX as a general operating system for a non-IBM company. The purpose of AIX/EVMS is to allow the management of disk storage in terms of logical 'volumes' in a large enterprise environment. Tools with this level of sophistication and performance were entirely unavailable and unknown to the open source development community prior to IBM's improper transfer to Linux. The actual transfer "patch" by IBM can be found at http://www.sourceforge.net/project/showfiles.php?g roup_id=25076&package_id=17436. The first code drop of AIX/EVMS by IBM was v0.0.1, which occurred on 03/21/2001. The first major release of AIX/EVMS by Linux was v1.0.0, in Linux 2.4, which occurred on 03/27/2003. The latest Linux release version of AIX/EVMS is v2.2.1, which occurred on 12/20/2003. The following table, Table B, identifies the AIX/EVMA "patches" of source code improperly transferred by IBM to the Linux 2.4 version.
Table B
AIX MERCED/9922A_43NIA Line #s EVMS 1.0.0 patches to Linux 2.4.x Line #s kernel/sys/IA64/bootrecord.h 64-170 include/linux/evms/evms_aix.h 157-263 usr/include/liblvm.h 234-250 include/linux/evms/evms_aix.h 311-327 usr/include/liblvm.h 252-272 289-307 include/linux/evms/evms_aix.h 329-349 usr/include/liblvm.h 316-363 include/linux/evms/evms_aix.h 352-400 usr/include/lvmrec.h 24-92 include/linux/evms/evms_aix.h 266-294 usr/include/lvm.h 26-35 include/linux/evms/evms_aix.h 6-11 kernel/sys/hd_psn.h 32 include/linux/
Invisible machines are just that, invisible. The machines can be machines to kill. If they are not detected, they can accomplish their goal.
We already have a plague of programmers gone bad who devise spamming techniques to get paid.
I can already see Darl blaming OSS community after discovering a bunch on nano-killers looking after him
cbs censoring political adv
on
Superbowling
·
· Score: -1, Redundant
it seems cbs is deciding who can talk to US peoples, censoring dissenting voices.
more infos on cbs censoring superbowl adv at moveon.org
Linus Torvalds: SCO Is "Just Too Wrong" The originator of the Linux OS has sharp words for SCO's "cornered rat" claims of intellectual-property infringement
If anyone knows what's in Linux, it's Linus Torvalds. He did the first work on the open-source operating system while a student at the University of Helsinki, and he managed the often chaotic process of building it with other programmers. Now, SCO Group (SCOX ), a small Utah software company, claims Linux is trampling on intellectual property rights it inherited from Novell (NOVL ), which got them from AT&T (T ). In an e-mail interview with BusinessWeek Correspondent Jim Kerstetter, Torvalds explains why he thinks SCO is wrong. The following are edited excerpts from that interview:
Q: SCO claims that old Unix files it says it owns are now in Linux. Can you explain to me why you think that's wrong? A: [A number of files SCO claims to own] were written from scratch for Linux.... SCO also doesn't hold any copyrights to the BSD code [software developed at the University of California at Berkeley that SCO says contained copyrighted material that was passed on to Linux], nor is it actually in [SCO's version of Unix]. So SCO is wrong.
Also, SCO has apparently several times mentioned how copyright notices have been removed. Just for the record: Original Unix doesn't have any copyright notices to remove. They were added after a lawsuit [between the Berkeley developers and AT&T, which was settled]. So SCO would be wrong again.
So basically SCO's arguments are just too wrong to even discuss rationally. SCO doesn't own the copyright on the files they are talking about -- the University of California at Berkeley does. But even if they did, the Linux files weren't even copied in the first place. And even if they had been copied, no copyright notices would have been removed, since they didn't exist in the original. There are literally several levels of SCO being wrong. And even if we were to live in that alternate universe where SCO would be right, they'd still be wrong.
Q: In fact, I saw in a recent interview that you chided yourself for the quality of some of those files. Why so? A: Hey, for some of the files they claim copyright ownership on I went back 12 years in the archives to see their original form, and the fact is, I was a young guy at university in '91, and I [made] mistakes that I simply wouldn't [make] anymore, and that are clear signs of beginner [programming].
And those mistakes show how the code wasn't copied -- it's a bit like how map makers used to introduce small errors in maps on purpose, so that if somebody copied them but claimed to have made their own, the original map maker could point to the error and say, "Well, how did you have exactly the same error, too?"
Except I can definitely state that I didn't make those mistakes on purpose. As a young student at the University of Helsinki, I definitely didn't have the kind of forethought required to foresee a company claiming my code as theirs 12 years later. If I had those kinds of powers, I'd never have gone into programming, I'd just play the stock market.
Q: Do you think that any copyright or patent-protected Unix code has actually found its way into Linux? A: Unlikely. There are now a number of people who have access to both Unix sources and Linux code, and literally written automated tools to find similarities. They found something like 30 lines from [Silicon Graphics, SGI ] that were dubious and that had been removed already. SGI wrote an open letter about their mistake. You can find it if you look for it.
As to patented algorithms, yes, there are a few examples of that -- IBM (IBM ) actually explicitly licensed some to Linux. That was a requirement on our side for even accepting the code in the first place. SCO doesn't own any patents, so they certainly can't be claiming ownership.
Q: If there is protected code in Linux, is there a solution? A: Oh, the solution to any patent/copyright dispute is licensing
Slashdot Mirror
this time I don't think the problem it's the RIAA.
iTunes does not make any money
Apple earns money from selling the hardware (iPod e c.)
So they can never let to play their songs withouth their buying anything else from them
this remind me of a country that has been bombed and invaded on the base it had all the equipment to be an imminent threath. Sadly it was not true. Sadly this is not a joke.
if you want to see the winner looking at the cilinders, you need to use the same 4 cilinders for the whole election ;)
In the voting arena, I would say that problems with inaccurate counts would be priority 2 (since nobody dies directly)
are you sure?
In an election with 4 candidates there would be 4 transparent tubes, each coated with an opaque wrapper. Voters would insert a coin-shaped plastic token into the cylinder representing their favourite candidate, and when the votes need to be counted the opaque wrapper would be removed to simply show which candidate had won. It's obvious, completely transparent and recounts are unnecessary because the winner should be obvious to all.
the main problem would be to line 100 milions voters
looking forward to see which of its customer this time SCO will kick to prove to the press that they have a case
Blue Sky of Death?
do they print a paper receipt?
What a great idea! I think I'll start up a business called "Microsoft 2" and start selling Linux distros through it...
actually somebody already did it
Not too many people find copyright law and open source law rulings terribly entertaining
are you kidding? just check how many peoples spend hours on browsing/commenting SCO vs the world soap opera
If you really want to get paranoid about something, get paranoid about money, which passes from hand, to hand, to hand. Your own desk doesn't really rank that high on the risk list, seeing as how its population is largely an extension of your own.
btw if anybody wants to get rid of his money, I can help
I guess you can't sue MS either.
why would you sue MS if your linux breaks?
mentions are often due to big/smart marketing staff/budget more than real merit
Linux and others OS project are weak in this respect (even if things are improving). at least weaker than most propietary software organization
100. The contribution of the Journaling File System ("JFS") was done in a series of "drops" of AIX code identified as "reference files" inside Linux. The first such drop occurred on or about February 2000, with multiple additions and significant follow-up work by IBM since that time to adapt AIX/JFS for enterprise use inside Linux. These drops of reference files do not necessarily become part of the source code in the Linux kernel, but rather are public displays of the Protected Materials so that anyone has access to them and can use them to construct similar file in Linux. The first drop contains (a) a partially functioning port, or transfer, of JFS from AIX to Linux; (b) a set of reference directories (named ref/) which contain the AIX reference version of AIX/JFS; (c) AIX/JFS-related utility files used to maintain and upkeep AIX/JFS; and (d) a set of directories (named directory ref_utils/) which contain the AIX reference version of utilities. Copies of AIX/JFS files into Linux are shown in Table A, below. Table A compares a 1999 version of AIX and shows the following similarities, demonstrating copying of code, structures and/or sequences.
Table A
AIX 9922A_43NIA File Line #s Linux 2.2.12 ref/File Line #s
usr/include/jsf/inode.h 16-37 include/linux/jfs/ref/jfs_inode.h 84-95,
126-138
kernel/sys/vnode.h 109-133 include/linux/jfs/ref/jfs_inode.h 96-122
usr/include/jsf/inode.h 39-40 include/linux/jfs/ref/jfs_inode.h 189-90
usr/include/jsf/inode.h 161-166 include/linux/jfs/ref/jfs_inode.h 414-421
usr/include/jsf/inode.h 172-180 include/linux/jfs/ref/jfs_inode.h 37-48
usr/include/jsf/inode.h 199-205 include/linux/jfs/ref/jfs_inode.h 52-59
usr/include/jsf/inode.h 62-66 include/linux/jfs/ref/jfs_inode.h 286-290
usr/include/jsf/inode.h 72-76 include/linux/jfs/ref/jfs_inode.h 295-302
usr/include/jsf/inode.h 83-158 include/linux/jfs/ref/jfs_inode.h 322-411
These transfers of AIX/JFS to Linux are in violation of the IBM Related Agreements, and are an improper use of AIX for adaptation to a general operating system.
101. IBM has also improperly transferred a UNIX/AIX-based enterprise volume management system ("AIX/EVMS") to Linux. Again, this was done by IBM to transfer enterprise-class capabilities from AIX to Linux, and was a violation of the IBM Related Agreements and IBM's promise not to adapt AIX as a general operating system for a non-IBM company. The purpose of AIX/EVMS is to allow the management of disk storage in terms of logical 'volumes' in a large enterprise environment. Tools with this level of sophistication and performance were entirely unavailable and unknown to the open source development community prior to IBM's improper transfer to Linux. The actual transfer "patch" by IBM can be found at http://www.sourceforge.net/project/showfiles.php?g roup_id=25076&package_id=17436. The first code drop of AIX/EVMS by IBM was v0.0.1, which occurred on 03/21/2001. The first major release of AIX/EVMS by Linux was v1.0.0, in Linux 2.4, which occurred on 03/27/2003. The latest Linux release version of AIX/EVMS is v2.2.1, which occurred on 12/20/2003. The following table, Table B, identifies the AIX/EVMA "patches" of source code improperly transferred by IBM to the Linux 2.4 version.
Table B
AIX MERCED/9922A_43NIA Line #s EVMS 1.0.0 patches to Linux 2.4.x Line #s
kernel/sys/IA64/bootrecord.h 64-170 include/linux/evms/evms_aix.h 157-263
usr/include/liblvm.h 234-250 include/linux/evms/evms_aix.h 311-327
usr/include/liblvm.h 252-272
289-307 include/linux/evms/evms_aix.h 329-349
usr/include/liblvm.h 316-363 include/linux/evms/evms_aix.h 352-400
usr/include/lvmrec.h 24-92 include/linux/evms/evms_aix.h 266-294
usr/include/lvm.h 26-35 include/linux/evms/evms_aix.h 6-11
kernel/sys/hd_psn.h 32 include/linux/
actually I were more worried of astronauts getting bacteria on Mars and contamining heart
Invisible machines are just that, invisible. The machines can be machines to kill. If they are not detected, they can accomplish their goal.
We already have a plague of programmers gone bad who devise spamming techniques to get paid.
I can already see Darl blaming OSS community after discovering a bunch on nano-killers looking after him
it seems cbs is deciding who can talk to US peoples, censoring dissenting voices.
more infos on cbs censoring superbowl adv at moveon.org
what a pity they still insist to make non-soda can convex
hours and hours lost to make them stand
if they just made them concave as well
here it is
next?
[bzzzzzz]
change the name to Lindos or LindOS
and in many countries pronunciation is quite the same that lindows
as previously discussed lindows brand name in english speaking countries is defendable, as windows being a common word is not.
of course this does not apply where english is not the main language, and windows then become a fully defendable brand.
M$ is just taking advantage of this (where it can)
to add mailto: support to Firebird just install mozex extension
Linus Torvalds: SCO Is "Just Too Wrong"
The originator of the Linux OS has sharp words for SCO's "cornered rat" claims of intellectual-property infringement
If anyone knows what's in Linux, it's Linus Torvalds. He did the first work on the open-source operating system while a student at the University of Helsinki, and he managed the often chaotic process of building it with other programmers. Now, SCO Group (SCOX ), a small Utah software company, claims Linux is trampling on intellectual property rights it inherited from Novell (NOVL ), which got them from AT&T (T ). In an e-mail interview with BusinessWeek Correspondent Jim Kerstetter, Torvalds explains why he thinks SCO is wrong. The following are edited excerpts from that interview:
Q: SCO claims that old Unix files it says it owns are now in Linux. Can you explain to me why you think that's wrong?
A: [A number of files SCO claims to own] were written from scratch for Linux.... SCO also doesn't hold any copyrights to the BSD code [software developed at the University of California at Berkeley that SCO says contained copyrighted material that was passed on to Linux], nor is it actually in [SCO's version of Unix]. So SCO is wrong.
Also, SCO has apparently several times mentioned how copyright notices have been removed. Just for the record: Original Unix doesn't have any copyright notices to remove. They were added after a lawsuit [between the Berkeley developers and AT&T, which was settled]. So SCO would be wrong again.
So basically SCO's arguments are just too wrong to even discuss rationally. SCO doesn't own the copyright on the files they are talking about -- the University of California at Berkeley does. But even if they did, the Linux files weren't even copied in the first place. And even if they had been copied, no copyright notices would have been removed, since they didn't exist in the original. There are literally several levels of SCO being wrong. And even if we were to live in that alternate universe where SCO would be right, they'd still be wrong.
Q: In fact, I saw in a recent interview that you chided yourself for the quality of some of those files. Why so?
A: Hey, for some of the files they claim copyright ownership on I went back 12 years in the archives to see their original form, and the fact is, I was a young guy at university in '91, and I [made] mistakes that I simply wouldn't [make] anymore, and that are clear signs of beginner [programming].
And those mistakes show how the code wasn't copied -- it's a bit like how map makers used to introduce small errors in maps on purpose, so that if somebody copied them but claimed to have made their own, the original map maker could point to the error and say, "Well, how did you have exactly the same error, too?"
Except I can definitely state that I didn't make those mistakes on purpose. As a young student at the University of Helsinki, I definitely didn't have the kind of forethought required to foresee a company claiming my code as theirs 12 years later. If I had those kinds of powers, I'd never have gone into programming, I'd just play the stock market.
Q: Do you think that any copyright or patent-protected Unix code has actually found its way into Linux?
A: Unlikely. There are now a number of people who have access to both Unix sources and Linux code, and literally written automated tools to find similarities. They found something like 30 lines from [Silicon Graphics, SGI ] that were dubious and that had been removed already. SGI wrote an open letter about their mistake. You can find it if you look for it.
As to patented algorithms, yes, there are a few examples of that -- IBM (IBM ) actually explicitly licensed some to Linux. That was a requirement on our side for even accepting the code in the first place. SCO doesn't own any patents, so they certainly can't be claiming ownership.
Q: If there is protected code in Linux, is there a solution?
A: Oh, the solution to any patent/copyright dispute is licensing
spirit is self-rebooting 60 times a day
what? they used a M$ OS for it? BSOD on Mars?
any UK citizen feeling it's worth sending a note to UK Competition Commission?
here the complaint procedure