IANAL, but I don't think this forbids anyone from setting up their own server because of the words "should not":
"Unless you have a written agreement with Google Fiber permitting you do so, you should not host any type of server using your Google Fiber connection"
(Emphasis by me). This sounds more like a "it would be nice if you don't" to me. Heck, even RFC 2119 agrees:
4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
I applied the patch to v2.6.30 from Linus' git tree at git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (commit 07a2039b8eb0af4ff464efd3dfd95de5c02648c6), and it compiled fine. Had to let patch(1) assume "-R" when it wanted to delete non-existant files, though. Worked for me:
linux-2.6$ ln -sv . linux-2.6.30-bfs
linux-2.6$ patch -p0 </tmp/2.6.30-sched-bfs-209.patch
patching file linux-2.6.30-bfs/Documentation/sysctl/kernel.txt
patching file linux-2.6.30-bfs/fs/pipe.c
patching file linux-2.6.30-bfs/include/linux/init_task.h
patching file linux-2.6.30-bfs/include/linux/sched.h
The next patch would delete the file linux-2.6.30-bfs.orig/kernel/sched.c,
which does not exist! Assume -R? [n] y
[...]
11 expanded comments in this thread, and nearly half of them link to evidence of prior art. WTF are these USPTO people doing at work? How about some investigation before granting the patent, or at least a simple Google search?
PLEASE NOTE: Microsoft Corporation (or based on where you live, one of its affiliates) licenses this supplement to you. You may use it with each validly licensed copy of Microsoft operating system products software (for which this supplement is applicable) (the ÃoesoftwareÃ). You may not use the supplement if you do not have a license for the software.
(Emphasis by me.) Addidionally, if this is GPL, as they say, they can't demand that you have a MS Windows license to use the software. When you've got a copy of it, you're free to use it as much as you want, with or without a MS Windows license.
"Vår daglige Beatles" (Our daily Beatles) was a daily radio program presenting all 212 recordings by The Beatles in chronological order, presented by Bård Ose and Finn Tokvam. Every presentation lasted about five minutes and contained interesting facts about the song -- what the inspiration for the song was, how it was recorded, some trivia about the period it was recorded, and so on. A very well-produced and informative work. The radio show started January 2007, and every Beatles song was played in its full length. It's believed this is the only time Revolution 9 was played in its entirety on Norwegian radio.
The last episode was aired 2007-12-13, and when christmas 2007 arrived, all 212 podcasts were put out for download at nrk.no as a christmas present for all Beatles fans, with the music removed. A real treasure, even though I had this cron job running every day to download each episode. Still, it was nice to get the complete collection.
This January NRK was planning to release every episode with the music. They got a deal with TONO (the Norwegian RIAA) and everything was OK, but it turned out that the agreement with IFPI and FONO only allowed publishing shows aired the last four weeks, and as mentioned, these programs were aired in 2007, so the podcasts had to be pulled.
I'd really like to give you an "Insightful" on this one, but I prefer to reward logged-in users with those few mod points I have. Please stop being an AC unless it's necessary.
Queen sucks! They are the worst band I've ever heard (tied with Rush and Avril Lavigne). Does anyone actully listen to them? And if so, why?!?
Well, they were declared "best British band" by listeners of BBC2 (20.000 votes total), and came on second place in another contest (600.000 votes total).
You may not like the music, but you're hardly in a position to say they suck.
I think that at least the basic interpreter should be taught to the new generations.
They don't feel confortable enough in less than 1 GB, what if they had just 4 KB?
Anyone remember Turbo Pascal 3.02? It had a pretty decent editor, compiler, overlay support and was able to create.COM files by copying parts of itself into the compiled file. And everything packed together in a single.COM file of 37 kilobytes. Impressing. Check out The Borland Museum and have a look for yourself.
They really knew how to create small and elegant code in those days. I'd like to have the assembly code for that, just for fun and inspiration.
So how will Apple react to this?
on
1200-Baud Archeology
·
· Score: 1, Flamebait
This is way cool. But we have seen lately how strict Apple behaves when unlocking iPhones, etc. Wouldn't it be ironic if Apple sues this guy for copyright infringement and pushing the DMCA instead of being thankful that he recovered this piece of history?
"But surely it can't be any good if they're just giving it away. After all, you don't get something for nothing."
"It can, because it's created by lots of intelligent, devoted people who don't get their reward in money, but by getting a good software product and respect in the community. Bugs and security holes are in many or most cases fixed sooner, because there isn't any money in waiting to the next free major version. Like the commercial product, it's still software development, they've just dropped the money part."
put Windows in a feak'n sandbox/VM where it really belongs and run any 'special needs' applications there instead of giving some Microsoft OEM the profits of tying Windows to the hardware.
4. USE WITH VIRTUALIZATION TECHNOLOGIES. You may not use the software installed on the licensed device within a virtual (or otherwise emulated) hardware system.
Congratulations. This comment (although is was modded Funny) is credited by Norbert Bollow as an inspiration for creating the openiso.org site, which is an attempt to become a truly open international standards organisation, an alternative to ISO. Interesting concept.
One method that would prevent tampering of previous written log data, is to use some kind of hash function, for example SHA1+MD5, to generate a signature of the current log chunk. When the next log chunk is to be written, the hash value of the previous chunk is stored in the current log chunk. This way the hash value of the previous chunk is used as salt when the current chunk is going to be calculated, making it impossible to change the log history unnoticed. Using only MD5 (or even SHA1) is probably not a good solution, as there has been some more or less successful attempts to forge the signature, but by combining SHA1 and MD5 along with file size, it should be reasonably impossible to fake old logs.
No expensive software necessary, it could easily be integrated into programs, or even a small bash/Perl/Python/whatever script could perform the task.
I once found the text strings stored in the BIOS of my 286. Not far from the standard "Keyboard error, press F1 to continue." message was "CPU not found. System halted."
I always wondered how they intended to display that message.
The BIOS programmer was probably slave of good programming practice -- always include a "This can not happen" section in conditionals.
PostgreSQL has done far more with far less capital.
Since you probably won't believe me, I invite you to compare the features of each. Visiting each project's web site is a good place to start. Once you see how much further ahead PostgreSQL is technologically than MySQL, consider how they managed to accomplish that with relatively little capital.
One of my criterias for "software healthiness" is how much the community is involved in the development and management of the source code. It is interesting to see that the source code for MySQL is stored in a BitKeeper repository instead of something more community-friendly like CVS or Subversion. A real turn-off for me, at least.
So, you would like an uncrackable DRM because you hate uncrackable DRM???
Maybe he has some belief in the consumer mass that they will value their rights and reject the product because of the tight DRM. I'm heavily disappointed about what I've seen so far. Seems as there'll always be a big enough mass of people who doesn't care, and then it gets popular enough to bother me.
If they want to revoke a player, they just don't include a copy of the disk key encrypted with that player's public key on future disks. So that player can play old disks, but they'll need to replace it to play new disks.
Oh, it's the MS Word method... "We need to make some money. Let's create a new format which the current version of the program can't read. All our current victi^H^H^H^H^H customers then have to buy a new version."
Slashdot Mirror
http://xkcd.com/768/
(Emphasis by me). This sounds more like a "it would be nice if you don't" to me. Heck, even RFC 2119 agrees:
Same kernel version as mentioned above.
I applied the patch to v2.6.30 from Linus' git tree at git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (commit 07a2039b8eb0af4ff464efd3dfd95de5c02648c6), and it compiled fine. Had to let patch(1) assume "-R" when it wanted to delete non-existant files, though. Worked for me:
11 expanded comments in this thread, and nearly half of them link to evidence of prior art. WTF are these USPTO people doing at work? How about some investigation before granting the patent, or at least a simple Google search?
Sigh. Utterly useless.
(Emphasis by me.) Addidionally, if this is GPL, as they say, they can't demand that you have a MS Windows license to use the software. When you've got a copy of it, you're free to use it as much as you want, with or without a MS Windows license.
"Vår daglige Beatles" (Our daily Beatles) was a daily radio program presenting all 212 recordings by The Beatles in chronological order, presented by Bård Ose and Finn Tokvam. Every presentation lasted about five minutes and contained interesting facts about the song -- what the inspiration for the song was, how it was recorded, some trivia about the period it was recorded, and so on. A very well-produced and informative work. The radio show started January 2007, and every Beatles song was played in its full length. It's believed this is the only time Revolution 9 was played in its entirety on Norwegian radio.
The last episode was aired 2007-12-13, and when christmas 2007 arrived, all 212 podcasts were put out for download at nrk.no as a christmas present for all Beatles fans, with the music removed. A real treasure, even though I had this cron job running every day to download each episode. Still, it was nice to get the complete collection.
This January NRK was planning to release every episode with the music. They got a deal with TONO (the Norwegian RIAA) and everything was OK, but it turned out that the agreement with IFPI and FONO only allowed publishing shows aired the last four weeks, and as mentioned, these programs were aired in 2007, so the podcasts had to be pulled.
And the error message also reads: "An E-Mail has been dispatched to our Technical Staff, whom you can also contact if the problem persists."
They're in for a surprise when opening their inbox tomorrow.
I'd really like to give you an "Insightful" on this one, but I prefer to reward logged-in users with those few mod points I have. Please stop being an AC unless it's necessary.
We've had this for years. It's called EXIF data and file comments. I doubt my sloppy handwriting adds value to the data.
Of course not, they have no thumbs.
Well, they were declared "best British band" by listeners of BBC2 (20.000 votes total), and came on second place in another contest (600.000 votes total).
You may not like the music, but you're hardly in a position to say they suck.
Anyone remember Turbo Pascal 3.02? It had a pretty decent editor, compiler, overlay support and was able to create .COM files by copying parts of itself into the compiled file. And everything packed together in a single .COM file of 37 kilobytes. Impressing. Check out The Borland Museum and have a look for yourself.
They really knew how to create small and elegant code in those days. I'd like to have the assembly code for that, just for fun and inspiration.
This is way cool. But we have seen lately how strict Apple behaves when unlocking iPhones, etc. Wouldn't it be ironic if Apple sues this guy for copyright infringement and pushing the DMCA instead of being thankful that he recovered this piece of history?
"It can, because it's created by lots of intelligent, devoted people who don't get their reward in money, but by getting a good software product and respect in the community. Bugs and security holes are in many or most cases fixed sooner, because there isn't any money in waiting to the next free major version. Like the commercial product, it's still software development, they've just dropped the money part."
Not allowed with Vista, according to the EULA:
Congratulations. This comment (although is was modded Funny) is credited by Norbert Bollow as an inspiration for creating the openiso.org site, which is an attempt to become a truly open international standards organisation, an alternative to ISO. Interesting concept.
One method that would prevent tampering of previous written log data, is to use some kind of hash function, for example SHA1+MD5, to generate a signature of the current log chunk. When the next log chunk is to be written, the hash value of the previous chunk is stored in the current log chunk. This way the hash value of the previous chunk is used as salt when the current chunk is going to be calculated, making it impossible to change the log history unnoticed. Using only MD5 (or even SHA1) is probably not a good solution, as there has been some more or less successful attempts to forge the signature, but by combining SHA1 and MD5 along with file size, it should be reasonably impossible to fake old logs.
No expensive software necessary, it could easily be integrated into programs, or even a small bash/Perl/Python/whatever script could perform the task.
The VIM Quick Reference Card is nice. Hang it on your wall.
The BIOS programmer was probably slave of good programming practice -- always include a "This can not happen" section in conditionals.
One of my criterias for "software healthiness" is how much the community is involved in the development and management of the source code. It is interesting to see that the source code for MySQL is stored in a BitKeeper repository instead of something more community-friendly like CVS or Subversion. A real turn-off for me, at least.
As a reference point, has anybody compared speed/flexibility against Qemu?
And for those that want more RMS stuff, I have stored some speeches (movies and sound recordings) at http://musthave.sunbase.org/Stallman/.
Maybe he has some belief in the consumer mass that they will value their rights and reject the product because of the tight DRM. I'm heavily disappointed about what I've seen so far. Seems as there'll always be a big enough mass of people who doesn't care, and then it gets popular enough to bother me.
Oh, it's the MS Word method... "We need to make some money. Let's create a new format which the current version of the program can't read. All our current victi^H^H^H^H^H customers then have to buy a new version."