Hmmm. Where does it say that? [cornell.edu] I don't read this anywhere...
You mean word for word, including the use of all caps? Nowhere. But if you mean semantically identical, then why the fsck don't you read your own fscking link!
Notwithstanding the provisions of section 106, it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program provided: (1) that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner, or...
It seems clear to me, as an English major, that this is equivalent to " you DO NOT NEED A LICENCE TO INSTALL IT ON A SINGLE COMPUTER".
You might be better off coming to an arangement with the authors of the JAR software
Short response: If you need to come to an arangement with the author, then his software isn't Free. Duh!
Long response: Avoid GPLd libraries like the plague. If the library isn't under the LGPL/BSD/MIT/MPL/Proprietary, then you must assume that the author does not want you to *USE* the library. If you were sued, you would of course win in court, because the terms of the GPL are quite clear. But you don't want to be sued to begin with. So avoid the software. Most people who use the GPL don't understand what it means. They assume that derivation means whatever they want it to mean, and not what copyright law specifically defines it to be. The risk of the author being one of these types is too great to risk your financial well being over.
Hmmm, if the software is taxed, then it must have been sold. Which means the USCC applies. Whoo hoo! Now I can return Windows as defective software and get my money back!
The average IT person is much more a luser than a guru. Most think that getting their MCSE after five tries makes them superior to everyone else. They are script kiddies with certificates. There are exceptions, as with everything. A know a few of the exceptions. They agree with me.
I mean did everyone whinge like this when the 5.25 drives dissappeard?
Not really, because 3.5 drives were a replacement for 5.25 drives. The only people who complained where those who wanted to punch holes in 3.5 disks to make them double sided.
Mine cost me $89. And that was on sale. Before a year and a half ago, I never even had a CDR. Compare that to a $10 floppy drive.
Oh wait, you're talking about the media... Hmmm, I still have 3.5 floppies that are ten years old and still work. On the other hand, I have bootable CDs that won't boot on my laptop.
USB fobs sound promising. But they don't work out of the box today without configuration under Linux and FreeBSD.
Re:Honest comparison between Gnome and KDE?
on
Gnome 2.2 Released
·
· Score: 1
and took some fiddling to get working via src
Doesn't take any fiddling at all. The ports files typically are there just to make sure you have the right dependencies installed and set the right configure arguments.
I don't use floppies often, but when I do, I really need them. It's how I install FreeBSD, and how lots of people install *NIX systems. You burn one or two floppies then install via ftp. Does Dell really expect us to burn two floppy's worth of data onto a CDR? Will I be able to write those floppy images to a USB "pen" and boot from it?
Floppies are a standard for removable read/write media. You can't get rid of them until there is a new standard to replace them. USB "pen" drives are not the standard. If Dell is going to fully support all these drives in BIOS so that they work with zero configuration under Linux/BSD/NIX then I'll accept it. Otherwise I want a floppy drive. They cost $5 wholesale.
p.s. How do you get one of these USB drives working under Windows? You insert the floppy that came with the drive and install a new driver.
Re:Honest comparison between Gnome and KDE?
on
Gnome 2.2 Released
·
· Score: 1
gnome seems to be more portable.
In what way? What platforms does Gnome run on that KDE does not?
I haven't used Gnome much, but I do know that KDE runs on Linux (all varieties), FreeBSD, NetBSD, OpenBSD, Solaris, AIX, HPUX, IRIX, Cygwin (sortof), and every other *NIX.
If I were to change the location of the Send button in Outlook, he'd never figure out how to send an e-mail
We all know that "you can't teach an old dog new tricks." But why oh why is everyone insisting that you teach new dogs old tricks!
I know people who can't use a TV remote. Maybe we should abandon the idea of TV remotes. After all, TV remotes will never succeed until they have the same clunky dials of your Dad's 50's era Magnavox.
A) *NIX man pages are supposed to be references, not tutorials. As such, they are superb. Well, at least the FreeBSD man pages are superb, sometimes the Linux man pages seem to be lacking finish.
B) All of the XFree86 documentation is installed as man pages. Very useful. But I still crack open the hardcopy X series from O'Reilly, most of which are merely printed copies of the man pages.
C) Books are printed on paper, which comes from trees, which is a renewable resource. In addition, the trees used for paper are grown on farms. It's much less destructive to the environment than generating the electricity used to display ephemeral information on your computer monitor.
D) No one is requiring you to buy these books. If you don't want them, you don't have to buy them.
An generalized freebsd-developers list would easily match those volumes. The reason the lists don't have the high volumes now is because they are dozens of lists (68), each with specific charters. Remove those charters, since this would be an "open" list without restrictions, and you end up with only a handful of lists with the same volume. Remove the moderation (again, because this is an "open" list) and you gain all the offtopic posts and flame wars as well.
if you're working on, say, the sound drivers, there's no reason why you need to read every single message on the framebuffer subsystem
Those types of posts are already available on other FreeBSD lists (there are 68 of them). Through all the development related lists into one, and you'll have to filter through all the non-relevant stuff. Either you filter it automatically, with the guarantee that useful info will get thrown away, or do you scan manually through the threads, knowing that thread topics mutate wildly from their subject lines.
Thank you for providing, in a single sentence, the best reason to use Linux rather than FreeBSD.
My respect for the FreeBSD development process just went up yet another notch. Open Source projects should not be soap operas where everyone gets to learn the dirty little secrets about everyone else. I'm glad I don't get to see that dirty underwear. I'm glad that the reasons for Matt's loss of his commit bit was kept private....writing code behind closed doors and releasing periodic snapshots for the dirty masses to consume.
Every commit is instantly accessible to the public. Every hour you can, if you wish, update your system direct from the public CVS server. And you get your choice of all three development branches.
Having a "private developer list" is certainly "behind closed doors".
Have you seen the volume of traffic on the open FreeBSD lists? The only way to communicate between developers in that environment is to have a closed list. I can easily imagine a thousand posts a day to that list. No developer can wade through that and still get some coding in.
It's not censorship if you do it to yourself. Geez!
It's not censorship if I choose to rent "The Matrix" instead of "Vampires Vixens From Venus". It is censorship if the government does not allow the video store to carry the latter, or for me to choose it.
Filtering on DVD players is not even close to censorship.
I'm a FreeBSD user, and a huge FreeBSD fan. But if you want the most "general purpose" BSD, then look at NetBSD. (But try FreeBSD and OpenBSD as well).
This is just something else Apple will steal from the BSD'ers.
There once has a fabulous apple tree. No matter how many apples one would take from it, there were just as many as before! When this was heard by the villagers they all rushed to the apple tree and took apples. But no matter how many they took, there were just as many apples as before. But some of them came and took apples and locked them within a chest, so that none could steal them. And they laughed at the other villagers, saying, "Look, they do not protect their apples. Surely a thief will come and steal them."
if this software had been written by an individual, rather than a corporation, the FBI would already be looking for the culprit.
Do you have some evidence that this is their modus operandi, or are you just making stuff up to justify your personal beliefs?
What is seen in the FBI's radar? Murder, kidnapping, terrorism, cracking, etc. Corporations aren't usually in their radar because, frankly, corporations do not usually engage in those types of behaviors. But corporations are frequently in other department's radars, like those of the SEC, Commerce, etc.
Unfortunately for this theory, Debian simply agreed that they'd made another mistake by accepting those packages, removed them, and that was the end of that.
Except that when it was pointed out that some KDE based software was "legal", had the appropriate disclaimers, or didn't use the GPL, Debian still refused to accept them.
Slashdot Mirror
You mean word for word, including the use of all caps? Nowhere. But if you mean semantically identical, then why the fsck don't you read your own fscking link!
It seems clear to me, as an English major, that this is equivalent to " you DO NOT NEED A LICENCE TO INSTALL IT ON A SINGLE COMPUTER".
You might be better off coming to an arangement with the authors of the JAR software
Short response: If you need to come to an arangement with the author, then his software isn't Free. Duh!
Long response: Avoid GPLd libraries like the plague. If the library isn't under the LGPL/BSD/MIT/MPL/Proprietary, then you must assume that the author does not want you to *USE* the library. If you were sued, you would of course win in court, because the terms of the GPL are quite clear. But you don't want to be sued to begin with. So avoid the software. Most people who use the GPL don't understand what it means. They assume that derivation means whatever they want it to mean, and not what copyright law specifically defines it to be. The risk of the author being one of these types is too great to risk your financial well being over.
"Wait, aren't we supposed to hate the MPAA and be boycotting movies?"
So, how many Slashdot readers who hate the MPAA went to see TTT? How many of them saw it more than once?
Hmmm, if the software is taxed, then it must have been sold. Which means the USCC applies. Whoo hoo! Now I can return Windows as defective software and get my money back!
May I suggest for your first homebrew, my homebrew recipe calculator. Included is a brewing primer for your newbies.
It should read "Guru" and "Luser".
Hardly.
The average IT person is much more a luser than a guru. Most think that getting their MCSE after five tries makes them superior to everyone else. They are script kiddies with certificates. There are exceptions, as with everything. A know a few of the exceptions. They agree with me.
I mean did everyone whinge like this when the 5.25 drives dissappeard?
Not really, because 3.5 drives were a replacement for 5.25 drives. The only people who complained where those who wanted to punch holes in 3.5 disks to make them double sided.
one that I do not know.
Here's one that I do know: floppies. They just work. Under all operating systems. Old or new. Period.
Considering that a cdr costs around 15 cents
Mine cost me $89. And that was on sale. Before a year and a half ago, I never even had a CDR. Compare that to a $10 floppy drive.
Oh wait, you're talking about the media... Hmmm, I still have 3.5 floppies that are ten years old and still work. On the other hand, I have bootable CDs that won't boot on my laptop.
USB fobs sound promising. But they don't work out of the box today without configuration under Linux and FreeBSD.
and took some fiddling to get working via src
Doesn't take any fiddling at all. The ports files typically are there just to make sure you have the right dependencies installed and set the right configure arguments.
I don't use floppies often, but when I do, I really need them. It's how I install FreeBSD, and how lots of people install *NIX systems. You burn one or two floppies then install via ftp. Does Dell really expect us to burn two floppy's worth of data onto a CDR? Will I be able to write those floppy images to a USB "pen" and boot from it?
Floppies are a standard for removable read/write media. You can't get rid of them until there is a new standard to replace them. USB "pen" drives are not the standard. If Dell is going to fully support all these drives in BIOS so that they work with zero configuration under Linux/BSD/NIX then I'll accept it. Otherwise I want a floppy drive. They cost $5 wholesale.
p.s. How do you get one of these USB drives working under Windows? You insert the floppy that came with the drive and install a new driver.
gnome seems to be more portable.
In what way? What platforms does Gnome run on that KDE does not?
I haven't used Gnome much, but I do know that KDE runs on Linux (all varieties), FreeBSD, NetBSD, OpenBSD, Solaris, AIX, HPUX, IRIX, Cygwin (sortof), and every other *NIX.
If I were to change the location of the Send button in Outlook, he'd never figure out how to send an e-mail
We all know that "you can't teach an old dog new tricks." But why oh why is everyone insisting that you teach new dogs old tricks!
I know people who can't use a TV remote. Maybe we should abandon the idea of TV remotes. After all, TV remotes will never succeed until they have the same clunky dials of your Dad's 50's era Magnavox.
A) *NIX man pages are supposed to be references, not tutorials. As such, they are superb. Well, at least the FreeBSD man pages are superb, sometimes the Linux man pages seem to be lacking finish.
B) All of the XFree86 documentation is installed as man pages. Very useful. But I still crack open the hardcopy X series from O'Reilly, most of which are merely printed copies of the man pages.
C) Books are printed on paper, which comes from trees, which is a renewable resource. In addition, the trees used for paper are grown on farms. It's much less destructive to the environment than generating the electricity used to display ephemeral information on your computer monitor.
D) No one is requiring you to buy these books. If you don't want them, you don't have to buy them.
And yes, GNOME is bigger
In a way, yes. Gnome users have bigger egos. Gnome has bigger proprietary companies backing it. Gnome has a bigger political agenda.
I'm not knocking the Gnome developers, I'm knocking the twisted religion that's grown up around it.
Current list totals for the week (2.5 days):
freebsd-current: 280
freebsd-stable: 62
freebsd-questions: 425
An generalized freebsd-developers list would easily match those volumes. The reason the lists don't have the high volumes now is because they are dozens of lists (68), each with specific charters. Remove those charters, since this would be an "open" list without restrictions, and you end up with only a handful of lists with the same volume. Remove the moderation (again, because this is an "open" list) and you gain all the offtopic posts and flame wars as well.
if you're working on, say, the sound drivers, there's no reason why you need to read every single message on the framebuffer subsystem
Those types of posts are already available on other FreeBSD lists (there are 68 of them). Through all the development related lists into one, and you'll have to filter through all the non-relevant stuff. Either you filter it automatically, with the guarantee that useful info will get thrown away, or do you scan manually through the threads, knowing that thread topics mutate wildly from their subject lines.
Thank you for providing, in a single sentence, the best reason to use Linux rather than FreeBSD.
...writing code behind closed doors and releasing periodic snapshots for the dirty masses to consume.
My respect for the FreeBSD development process just went up yet another notch. Open Source projects should not be soap operas where everyone gets to learn the dirty little secrets about everyone else. I'm glad I don't get to see that dirty underwear. I'm glad that the reasons for Matt's loss of his commit bit was kept private.
Every commit is instantly accessible to the public. Every hour you can, if you wish, update your system direct from the public CVS server. And you get your choice of all three development branches.
Having a "private developer list" is certainly "behind closed doors".
Have you seen the volume of traffic on the open FreeBSD lists? The only way to communicate between developers in that environment is to have a closed list. I can easily imagine a thousand posts a day to that list. No developer can wade through that and still get some coding in.
I do however find the whole "core team" thing to be a bit of an elitist thing
Then what do you want to call them? Directors of Distributed Development? The Warm and Fuzzy People Who Grant Commit Bits?
They're called the Core Team because they are the core team. Geez.
It's not censorship if you do it to yourself. Geez!
It's not censorship if I choose to rent "The Matrix" instead of "Vampires Vixens From Venus". It is censorship if the government does not allow the video store to carry the latter, or for me to choose it.
Filtering on DVD players is not even close to censorship.
I'm a FreeBSD user, and a huge FreeBSD fan. But if you want the most "general purpose" BSD, then look at NetBSD. (But try FreeBSD and OpenBSD as well).
if this software had been written by an individual, rather than a corporation, the FBI would already be looking for the culprit.
Do you have some evidence that this is their modus operandi, or are you just making stuff up to justify your personal beliefs?
What is seen in the FBI's radar? Murder, kidnapping, terrorism, cracking, etc. Corporations aren't usually in their radar because, frankly, corporations do not usually engage in those types of behaviors. But corporations are frequently in other department's radars, like those of the SEC, Commerce, etc.
Unfortunately for this theory, Debian simply agreed that they'd made another mistake by accepting those packages, removed them, and that was the end of that.
Except that when it was pointed out that some KDE based software was "legal", had the appropriate disclaimers, or didn't use the GPL, Debian still refused to accept them.
People who say KDE is too much like Windows...
...have never used KDE
...have never used Windows
...deliberately trolling nonsense
1)
2)
3)