Slashdot Mirror

mrgrumpy contributes this review of a book which, despite the interesting subject matter, he says comes with some forgiveable but hard-to-ignore shortcomings. Emergence still sounds like an interesting read and broad introduction to the theories and subject matter at hand, but read on for more of his take on the book. Emergence - The connected lives of ants, brains, cities and software author Steve Johnson pages 288 publisher Penguin rating 6 reviewer Jim Richards ISBN 0-713-99400-2 summary Seeing order and patterns in apparent chaos.

This book covers the theory of emergence, which states that within a system of what seems to be anarchy, there are underlying rules that govern the pattern of behaviour and bring order out of chaos.

This books serves as an introduction to the field of emergence. It is something that is already happening around us, but we usually cannot see. The reason for this is that you need to look at a higher level then the individual organism. Ants can not see the society as a whole that they are members of. Just as we humans may have an understanding of the local community we are in and of ourselves, we need to step outside (or above) the city to understand how it functions. A city, like an ant colony does not have rules from the top as such, but rules that each occupant obeys, and it is these rules that give order to the chaos and make the resultant community behave like an organism as a whole.

I really wanted to like this book. But the level of information within it will make me put in into the light, popular fiction section of my bookshelf. One of the aspects of the book that really wanted me to give a good review is that the author makes a good introduction to the theory behind the comments system of Slashdot, the way people are chosen to rate comments and how good comments filter to the top. As such, I would have liked a review of the editorial process on Kuro5hin as well, since the two systems as fairly similar. In fact, I think the Kuro5hin system is better, because long time readers will see that the stories have moved away from an open source/linux focus to more cultural aspects, thus reflecting the change and growth of the community. But the idea of a Daily Me portal, that serves information that would suit us is explored heavily.

As I read the book though, an uneasiness came upon me, just as I do when reading books on neo-Darwinism. There is no mention of where these rules as such come from except through evolutionary survival or initial chance. If anything, the author implies that we are in a universe that had the initial conditions set, and left running. So we'd evolve or grow into who or what we are.

The idea that a God figure could be there, tweaking the parameters as the model runs, or even setting the initial conditions works against his ideas. This view is however explored in the chapter Control Artist, where the author comments on the development of software models, notably computer games. Games such as SimCity are discussed where the rules are set, but as a player we get to choose what gets built, what gets destroyed. Although here we are playing the Mayor of the City, the notion is the same; we control the macro level and not the micro level. But at the micro level, the software developer who built the game in the first place controls each inhabitant. Nothing really, is left to chance. Given the exact same initial conditions and same set of instructions the computer will create the same environment.

So, like most popular science books currently available it will educate you, entertain you and keep you occupied while reading it or totally bore you. But it is not a book of philosophy to base life on, which thankfully, the author has not tried to provide. It is very well researched, and the author seems on top of current trends and ideas. His writing style jumps around quite a bit, and some of the connections between topics might seem a little far fetched but it is an entertaining read as an introduction to the field of emergence theory.

Pet peeve 1: Notes. The notes section at the end is fairly extensive. But there are no foot notes in the book. The notes are indexed by page and quote. So as a reader you have to constantly check the notes section to see if there is a note or reference for the page you are reading.

Pet peeve 2: There was (for me) a glaring technical error on page 120.

"Ironically, it is precisely this feedback that the Web lacks, because HTML-based links are one-directional. You can point to ten other sites from your home page, but there's no way for those pages to know that you're pointing to them, short of you taking the time to fire off an e-mail to their respective webmasters."

You can see who is visiting your site, unless they are using an anonymizer proxy, or other system to hide your headers. The HTTP-REFERER header gives you exactly this information.

You can purchase Emergence at Fatbrain. Want to see your own review here? Read the book review guidelines first, then use the web submissions form.

Frabcus asks: "I founded an Open Source project TortoiseCVS, a Windows Explorer shell extension for using CVS, but now I'm looking to hand on project management to someone else. When I started out, I had an itch to scratch. We started using CVS at work and I didn't like the interface for WinCVS, so I made a better one. Now it's a year and a half later and TortoiseCVS does everything that I want it to, so I'd like to move on to other things and let someone else take it on. There have been over 20,000 downloads, so I have quite a large user base, but not many people are active in supplying patches. Do you guys have experience of handing on an Open Source project? How did you find someone who has similar goals that will fit in with the existing code?" The thing to do is to start asking around in development circles. The best starting place, of course, is among the existing user-base. For those of you who have transferred Open Source projects, how did you go about finding your successor?

Another well timed submission on this same subject, mrgrumpy follows up with this query: "Quite some time ago (around 1997-1998) I built a Java based adventure game called World. Developed with Java1.1 (and at the time it was fairly leading edge, it now looks a bit tired), you run around, collect treasure and kill things. As with all my great projects (hey, I won a Sparc5 for this), I had always intended to finish it, but never did. Now I want to give it away to a good home where developers will continue to work on the code and bring my ideas to completion.

Every now and then I sit down and have a look at the code but I don't really have the energy left to complete it (most of my energy was soaked up with my Masters degree). Other projects have taken over now, and I'm planning to go overseas for 12-18 months, so I know I won't get back to it for a very, very long time in any serious way.

I am happy to give the code away if a team of developers want to continue developing it. I can act as a grandfather figure to the project to give guidance and wisdom, and to clarify what my vision was, and what the code does. I'd prefer it to be GPL'd or a similar license that won't shut the code up.

There was another project similar to this one called White Orb, which seems to have gone the way of the dodo, a shame because it had a lot of potential, so I don't want to release this one and have it gather dust. I could set the project up somewhere like SourceForge, but as I said I'd rather just hand it all over to someone else and just look after it.

If you're interested, you could email me, or just leave a comment below. I want to pick either a team, or an individual who I can be confident in that they'll get the project up and running."

So here are two projects looking for good homes. What's the best way of giving up control of an Open Source project (with the potential of varying degrees of continued project development by the original maintainer) in the hopes of it continuing on in good health?

Frabcus asks: "I founded an Open Source project TortoiseCVS, a Windows Explorer shell extension for using CVS, but now I'm looking to hand on project management to someone else. When I started out, I had an itch to scratch. We started using CVS at work and I didn't like the interface for WinCVS, so I made a better one. Now it's a year and a half later and TortoiseCVS does everything that I want it to, so I'd like to move on to other things and let someone else take it on. There have been over 20,000 downloads, so I have quite a large user base, but not many people are active in supplying patches. Do you guys have experience of handing on an Open Source project? How did you find someone who has similar goals that will fit in with the existing code?" The thing to do is to start asking around in development circles. The best starting place, of course, is among the existing user-base. For those of you who have transferred Open Source projects, how did you go about finding your successor?

Another well timed submission on this same subject, mrgrumpy follows up with this query: "Quite some time ago (around 1997-1998) I built a Java based adventure game called World. Developed with Java1.1 (and at the time it was fairly leading edge, it now looks a bit tired), you run around, collect treasure and kill things. As with all my great projects (hey, I won a Sparc5 for this), I had always intended to finish it, but never did. Now I want to give it away to a good home where developers will continue to work on the code and bring my ideas to completion.

Every now and then I sit down and have a look at the code but I don't really have the energy left to complete it (most of my energy was soaked up with my Masters degree). Other projects have taken over now, and I'm planning to go overseas for 12-18 months, so I know I won't get back to it for a very, very long time in any serious way.

I am happy to give the code away if a team of developers want to continue developing it. I can act as a grandfather figure to the project to give guidance and wisdom, and to clarify what my vision was, and what the code does. I'd prefer it to be GPL'd or a similar license that won't shut the code up.

There was another project similar to this one called White Orb, which seems to have gone the way of the dodo, a shame because it had a lot of potential, so I don't want to release this one and have it gather dust. I could set the project up somewhere like SourceForge, but as I said I'd rather just hand it all over to someone else and just look after it.

If you're interested, you could email me, or just leave a comment below. I want to pick either a team, or an individual who I can be confident in that they'll get the project up and running."

So here are two projects looking for good homes. What's the best way of giving up control of an Open Source project (with the potential of varying degrees of continued project development by the original maintainer) in the hopes of it continuing on in good health?

Frabcus asks: "I founded an Open Source project TortoiseCVS, a Windows Explorer shell extension for using CVS, but now I'm looking to hand on project management to someone else. When I started out, I had an itch to scratch. We started using CVS at work and I didn't like the interface for WinCVS, so I made a better one. Now it's a year and a half later and TortoiseCVS does everything that I want it to, so I'd like to move on to other things and let someone else take it on. There have been over 20,000 downloads, so I have quite a large user base, but not many people are active in supplying patches. Do you guys have experience of handing on an Open Source project? How did you find someone who has similar goals that will fit in with the existing code?" The thing to do is to start asking around in development circles. The best starting place, of course, is among the existing user-base. For those of you who have transferred Open Source projects, how did you go about finding your successor?

Another well timed submission on this same subject, mrgrumpy follows up with this query: "Quite some time ago (around 1997-1998) I built a Java based adventure game called World. Developed with Java1.1 (and at the time it was fairly leading edge, it now looks a bit tired), you run around, collect treasure and kill things. As with all my great projects (hey, I won a Sparc5 for this), I had always intended to finish it, but never did. Now I want to give it away to a good home where developers will continue to work on the code and bring my ideas to completion.

Every now and then I sit down and have a look at the code but I don't really have the energy left to complete it (most of my energy was soaked up with my Masters degree). Other projects have taken over now, and I'm planning to go overseas for 12-18 months, so I know I won't get back to it for a very, very long time in any serious way.

I am happy to give the code away if a team of developers want to continue developing it. I can act as a grandfather figure to the project to give guidance and wisdom, and to clarify what my vision was, and what the code does. I'd prefer it to be GPL'd or a similar license that won't shut the code up.

There was another project similar to this one called White Orb, which seems to have gone the way of the dodo, a shame because it had a lot of potential, so I don't want to release this one and have it gather dust. I could set the project up somewhere like SourceForge, but as I said I'd rather just hand it all over to someone else and just look after it.

If you're interested, you could email me, or just leave a comment below. I want to pick either a team, or an individual who I can be confident in that they'll get the project up and running."

So here are two projects looking for good homes. What's the best way of giving up control of an Open Source project (with the potential of varying degrees of continued project development by the original maintainer) in the hopes of it continuing on in good health?

mrgrumpy asks: "I run Debian (unstable, woody) kernel 2.2.14 with everything dangerously up to date, and I also run a Solaris7 (Sparc not Intel). I've had NFS working (not with autofs, just mount and share) between the two boxes fine for a few weeks since I set them up. I recently applied a patch cluster from SunSolve to the Sun box, and lo and behold, NFS stopped working. In the patch list there were quite a few NFS fixes with the kernel patch 106541-10. I have the home directories, and a development directory from the Sun box (which serves NIS, NFS, and just about everything) mounted on the Linux box. Most of the time nothing goes wrong. But, when I run the distributed.net client on the Linux box, which needs to read and write files that are mounted across from the Sun box, it locks up and I get messages such as 'Apr 17 14:20:31 boink kernel: nfs: task 1473 can't get a request slot...' in the logs." Can anyone figure out what's going wrong here? (Read more)

"My machines are: boink (GNU/Linux 2.2.14 kernel), and splat (Solaris7 [Sparc]). If I run snoop on the Sun box I get:

root@splat$ snoop splat and boink rpc nfs
boink.home.cyber4.org -> splat.home.cyber4.org NFS C LOOKUP2 FH=009B_lJAQ.boink
splat.home.cyber4.org -> boink.home.cyber4.org NFS R LOOKUP2 OK FH=9668
boink.home.cyber4.org -> splat.home.cyber4.org NFS C LOOKUP2 FH=009B root.lock
splat.home.cyber4.org -> boink.home.cyber4.org NFS R LOOKUP2 OK FH=9E2D
boink.home.cyber4.org -> splat.home.cyber4.org NFS C REMOVE2 FH=009B_lJAQ.boink
splat.home.cyber4.org -> boink.home.cyber4.org NFS R REMOVE2 OK
boink.home.cyber4.org -> splat.home.cyber4.org NFS C LOOKUP2 FH=009B root.lock
splat.home.cyber4.org -> boink.home.cyber4.org NFS R LOOKUP2 OK FH=9E2D
boink.home.cyber4.org -> splat.home.cyber4.org NFS C WRITE2 FH=79D9 at0 for 4096 (retransmit)
boink.home.cyber4.org -> splat.home.cyber4.org NFS C CREATE2 FH=009B_yGAQ.boink
splat.home.cyber4.org -> boink.home.cyber4.org NFS R CREATE2 OK FH=AA9B
boink.home.cyber4.org -> splat.home.cyber4.org NFS C WRITE2 FH=AA9B at0 for 1

all throughout the logs. I had read that locking for nfs on Linux is not great, and I am using knfsd with NFS compiled in the kernel

Usually the errors cascade down a spiral of death until I reboot the Linux box. in.lockd on Linux doesn't have a debug mode (Solaris does, restart it with -d3) and I don't seem to be able to find any other way of debugging it."

So at this point, grumpy either needs a solution method or a way to debug in.lockd. Are there any methods that may prove useful in attempting to recover from an NFS "spiral of death"?