The king will call the prisoners in any order he pleases, and he can call and recall each prisoner as many times as he wants, as many times in a row as he wants. The only rule the king has to obey is that eventually he has to call every prisoner in an arbitrary number of times. So maybe he will call the first prisoner in a million times before ever calling in the second prisoner twice, we just don't know. But eventually we may be certain that each prisoner will be called in ten times, or twenty times, or any number you choose.
Say the king needs to call each prisoner at least ten times. What is to stop him from calling prisoner #1 ten times, and never again, then prisoner #2 ten times, and never again, etc.? If the king does this, then prisoner #1 is never able to send more than 1 signal. Or the king can start off by calling the counter ten times, and never call him again. In this case, the counter will never be able to receive any signals.
The question should probably say instead something like: "with n_i being the number of times prisoner #i is called, n_i/n_j approaches a non-zero constant as time approaches infinity, for all pairs i and j."
Uh, the article is talking about AbiWord's license making it possible for them to collaborate with external, separate projects such as link-grammar, gtkmathview, etc. It is saying that OpenOffice.Org's license requirements prevent it from collaborating with link-grammar, gtkmathview, etc. It is not talking about the lack of collaboration between AbiWord and OpenOffice.Org.
The FSF also requires you to assign your copyright to them if you contribute to some of their projects (such as emacs -- I know; I've contributed to emacs). And you have to sign a document saying that your work is your own, and that you have the right to assign copyright to them (i.e. your employer has no claim over the code). This is to make sure that any code that goes in is legit, or at least that if they get sued for copying someone's code, they can point to the document and say that it wasn't their fault.
Of course, the free software community trusts the FSF a lot more than than they trust Sun.
Creative Commons has been working with debian-legal on making the appropriate licenses DFSG free. I don't know how much progress has been made, but there is something being done. So as long as the icons are licensed under CC-SA 2.0 "or later", things should work out eventually. Although I think it would be good for them to dual-license under both CC-SA and GPL.
While not a donations page per se, you can visit their support page: http://www.namesys.com/support.html where they accept credit card payments for technical support. I'm sure that they wouldn't mind if you dropped some money in there and told them that it's a donation rather than a support request.
Since Reiser4 is not in mainline kernel yet, you need to compile your own kernel (either use the -mm branch, or download the patches from the Namesys web page, or wait for Reiser4 to be added to mainline). Of course, this also means that you need to do a little bit of swapping in order to use it as your root filesystem, since no distribution offers it by default.
I don't know about the GP poster, but I use Debian, which includes the Reiser4 utilities.
Sure, ReiserFS is a full blown filesystem, and WinFS is not a filesystem, however the functionality of WinFS is included in ReiserFS.
To be more precise, the functionality of WinFS is included in what ReiserFS will be able to do when it is completed. As of right now, Reiser4 is just a normal storage system with no capabilities above the other filesystems that are included in Linux (ext3, JFS, XFS, etc.) In a few years, we will have what is currently referred to as Reiser6, which will have the extended semantics that has been in planning for over 10 years. But it is not there yet.
GPFS has a different focus, but XFS seems to be aimed at solving similar problems as ReiserFS (scalability, high performance, journaling).
Actually, no. The ultimate goal of ReiserFS is the semantic enhancements described in this paper:
http://www.namesys.com/whitepaper.html All the other stuff is just prerequisites.
The problem isn't that Microsoft is using a microkernel (which they aren't, BTW -- at least not the last I heard). It's that WinFS is a separate library that sits on top of the storage layer. This means that programs must use a completely different API to access WinFS, rather than just using normal filesystem calls.
You also seem to be mixing up the issue of microkernels and monolithic kernels. Apple's OS X uses a microkernel, but the operating system is still monolitic, so all the important stuff is still part of a single big process; the microkernel is basically just an abstraction layer. Hurd is a microkernel but uses multiple servers, so all the subsystems are separate.
Many people (including myself) have been using Reiser4 for quite a while now without any problems. The developers have stopped being able to find bugs, as far as I've heard, although the occasional bug does pop up on the mailing list (and is fixed rather promptly by the developers). When Reiser4 gets included into the mainline kernel and the number of users increases by an order of magnitude, it will be likely that some new bugs will be found. I might not trust million-dollar, mission-critical data on it just yet, but for personal use, it seems to be stable enough.
Eventually, Reiser4 will allow storing metadata in plain old files, so that no special tools will have to be used. It will also allow queries done straight through the filesystem. In the interview, Hans says that that functionality is about 3-5 years away when fully implemented, but it will be implemented gradually, so some functionality will be available earlier.
Even with the radio frequency technology, however, the vehicle will still have to stop. If a person's identifying data produce no red flags, they will get just a cursory check at the border rather than lengthy questioning.
New terrorist plan:
1. find a car with a known-good RFID tag and steal it.
2. sneak into the U.S., avoiding being questioned.
3. ???
4. **Kaboom!**
Where did you get 26.4% from? They looked at 49 studies. 45 of them reported that intervention was effective. Of those 45, 7 were subsequently contradicted, and 7 were found to report stronger effects. So that's 14 that are "inaccurate or overblown". 14/45 (which follows the percentages given in the abstract) is 31% (which is pretty close to 1/3). If you want to do 14/49 (the total number of studies they looked at), that gives you 28.6%.
close the windows, get out of the car, then get back in the car and open the windows again.
You don't "roll up" windows in Windows(R). You can do it in some X window managers, but that doesn't do anything to solve any problems (other than lack of screen real estate).
DjVu actually allows you to embed the text into the document, along with where it appears in the bitmap, so you can do searching, select text, etc.
That said, I like DjVu, and I use it some times, but it isn't a complete PDF replacement. DjVu is still a bitmap format. PDF can be bitmap or vector, so you can print out a document in 3000000 dpi, or 30 dpi, without loss of quality (as much as "quality" can be used to describe "30 dpi"), and without using a huge file.
Having never set off an alarm before, my life's goal was to set off an alarm walking into a store (not on purpose). I finally accomplished that last December. I walked into one store, carrying merchandise I had purchased from another store, and it set off the alarm. I looked up at the cashiers, and unfortunately, nobody even looked up, so I couldn't gloat.
When I left the store, though, I set off the alarm again, and this time someone came to me. I just told her that I had set off the alarm when I came in, waved my bag from the other store through the detector to set it off, and she let me go.
Anyone who writes software licensed under the GPL should read the section at the bottom entitled "How to Apply These Terms to Your New Programs". It tells you exactly what you need to do.
And even though he may have cut checks for 20K, he's paid much less. Many people who have received checks from Knuth have them framed, and won't cash them in.
I should add, though, that RSA keys have never been claimed to be of a certain bit-strength. It's always been contingent on "what's the best factoring algorithm at this time?" The strength of RSA keys is based only on the belief that factoring is NP-hard.
On the other hand, SHA-1 was supposed to give 80 bits worth of collision resistance. Now it seems like it only gives 69 bits.
Slashdot Mirror
The question should probably say instead something like: "with n_i being the number of times prisoner #i is called, n_i/n_j approaches a non-zero constant as time approaches infinity, for all pairs i and j."
Uh, the article is talking about AbiWord's license making it possible for them to collaborate with external, separate projects such as link-grammar, gtkmathview, etc. It is saying that OpenOffice.Org's license requirements prevent it from collaborating with link-grammar, gtkmathview, etc. It is not talking about the lack of collaboration between AbiWord and OpenOffice.Org.
The FSF also requires you to assign your copyright to them if you contribute to some of their projects (such as emacs -- I know; I've contributed to emacs). And you have to sign a document saying that your work is your own, and that you have the right to assign copyright to them (i.e. your employer has no claim over the code). This is to make sure that any code that goes in is legit, or at least that if they get sued for copying someone's code, they can point to the document and say that it wasn't their fault.
Of course, the free software community trusts the FSF a lot more than than they trust Sun.
Creative Commons has been working with debian-legal on making the appropriate licenses DFSG free. I don't know how much progress has been made, but there is something being done. So as long as the icons are licensed under CC-SA 2.0 "or later", things should work out eventually. Although I think it would be good for them to dual-license under both CC-SA and GPL.
While not a donations page per se, you can visit their support page: http://www.namesys.com/support.html where they accept credit card payments for technical support. I'm sure that they wouldn't mind if you dropped some money in there and told them that it's a donation rather than a support request.
Resizing is not yet supported (but will be when the repacker is released), and neither are xattr.
I don't know about the GP poster, but I use Debian, which includes the Reiser4 utilities.
You also seem to be mixing up the issue of microkernels and monolithic kernels. Apple's OS X uses a microkernel, but the operating system is still monolitic, so all the important stuff is still part of a single big process; the microkernel is basically just an abstraction layer. Hurd is a microkernel but uses multiple servers, so all the subsystems are separate.
And /. is not one monolitic entity either.
Many people (including myself) have been using Reiser4 for quite a while now without any problems. The developers have stopped being able to find bugs, as far as I've heard, although the occasional bug does pop up on the mailing list (and is fixed rather promptly by the developers). When Reiser4 gets included into the mainline kernel and the number of users increases by an order of magnitude, it will be likely that some new bugs will be found. I might not trust million-dollar, mission-critical data on it just yet, but for personal use, it seems to be stable enough.
Eventually, Reiser4 will allow storing metadata in plain old files, so that no special tools will have to be used. It will also allow queries done straight through the filesystem. In the interview, Hans says that that functionality is about 3-5 years away when fully implemented, but it will be implemented gradually, so some functionality will be available earlier.
Just have to sneak across the border before the theft is reported. If you're in a border town, that shouldn't be too hard.
1. find a car with a known-good RFID tag and steal it.
2. sneak into the U.S., avoiding being questioned.
3. ???
4. **Kaboom!**
Where did you get 26.4% from? They looked at 49 studies. 45 of them reported that intervention was effective. Of those 45, 7 were subsequently contradicted, and 7 were found to report stronger effects. So that's 14 that are "inaccurate or overblown". 14/45 (which follows the percentages given in the abstract) is 31% (which is pretty close to 1/3). If you want to do 14/49 (the total number of studies they looked at), that gives you 28.6%.
How about a stack of punch cards? A really big stack...
You don't "roll up" windows in Windows(R). You can do it in some X window managers, but that doesn't do anything to solve any problems (other than lack of screen real estate).
Uh, that was a trademark dispute. The DMCA is only related to copyright.
DjVu actually allows you to embed the text into the document, along with where it appears in the bitmap, so you can do searching, select text, etc.
That said, I like DjVu, and I use it some times, but it isn't a complete PDF replacement. DjVu is still a bitmap format. PDF can be bitmap or vector, so you can print out a document in 3000000 dpi, or 30 dpi, without loss of quality (as much as "quality" can be used to describe "30 dpi"), and without using a huge file.
When I left the store, though, I set off the alarm again, and this time someone came to me. I just told her that I had set off the alarm when I came in, waved my bag from the other store through the detector to set it off, and she let me go.
Anyone who writes software licensed under the GPL should read the section at the bottom entitled "How to Apply These Terms to Your New Programs". It tells you exactly what you need to do.
And even though he may have cut checks for 20K, he's paid much less. Many people who have received checks from Knuth have them framed, and won't cash them in.
I should add, though, that RSA keys have never been claimed to be of a certain bit-strength. It's always been contingent on "what's the best factoring algorithm at this time?" The strength of RSA keys is based only on the belief that factoring is NP-hard.
On the other hand, SHA-1 was supposed to give 80 bits worth of collision resistance. Now it seems like it only gives 69 bits.
Yes, you are right. I will blame a brain hiccup.