PlanetMysql.ru – информация о СУБД MySQL

1. Law of Success 2.0 -- a blog of interviews with famous and/or interesting people, from Brad Feld to Uri Geller.
2. Pioneer One -- crowdsourced funding for TV show, perhaps a hint of the future. Pilot shot for $6,000 which was raised through KickStarter. Distributed via BitTorrent.
3. DrasticTools -- PHP/MySQL visualisation tools, including TreeMap, tag cloud, hierarchical bar chart, and animated list. (via TomC on Delicious)
4. GoogleCL -- command-line interface to Google services. At the moment the services are Picasa, Blogger, YouTube, Contacts, Docs, and Calendar.

Saw this interesting paper about highly concurrent programming methods and figured the word should be spread! It’s not new material but it’s a good read. See the full article here: http://www.usenix.org/events/hotos03/tech/full_papers/vonbehren/vonbehren_html/

“Highly concurrent applications such as Internet servers and transaction processing databases present a number of challenges to application designers. First, handling large numbers of concurrent tasks requires the use of scalable data structures. Second, these systems typically operate near maximum capacity, which creates resource contention and high sensitivity to scheduling decisions; overload must be handled with care to avoid thrashing. Finally, race conditions and subtle corner cases are common, which makes debugging and code maintenance difficult.

Threaded servers have historically failed to meet these challenges, leading many researchers to conclude that event-based programming is the best (or even only) way to achieve high performance in highly concurrent applications. “

LinuxTag is the most important place for Linux and open source software in Europe. Last year, LinuxTag had over ten thousand attendees, and over 300 speakers. This year, the 16th LinuxTag will be June 9-12, 2010 at the Berlin Fairgrounds in Germany.

LinuxTag seeks exciting and suitable proposals for presentations in the conference tracks. The Call for Papers ends today.

I am proud to be a member of the LinuxTag Program Committee. Although a lot of proposals have already been submitted, there are some topics missing that I’d personally like to see covered. So, if you’re up for a last minute submission, get your inspiration from the following list:

• Is/was the recent economic crisis an opportunity for Open Source?
• More real-life case studies on how OSS is being used in mission-critical scenarios.
• A European or global perspective on Open Source in Public Administration.
• How to make use of Amazon EC2 or Google AppEngine with Open Source apps?
• Technical tutorials for beginners, especially for building Web apps (e.g. PHP/Ruby/Java/etc. for beginners).
• High performance Web environments with Open Source tools
• Security in the Cloud
• What’s the status of some of the regional Linux distributions?

I can’t promise that your talk will be accepted if it covered one of the above topics. The review process is of course a joint effort of the whole Program Committee. Anyway, it’s definitely worth a try. Of course, any other topic I did not think of is also highly welcome.

Go here to submit your LinuxTag proposal.

This is going to be a really short post, but for someone it could save an hour of life.

So, you’ve nothing to do and you’ve decided to play around with IPv6 or maybe you’re happened to be an administrator of a web service that needs to support IPv6 connectivity and you need to make your nginx server work nicely with this protocol.

First thing you need to do is to enable IPv6 in nginx by recompiling it with --with-ipv6 configure option and reinstalling it. If you use some pre-built package, check if your nginx already has this key enabled by running nginx -V.

The results should have --with-ipv6 option in configure arguments:

After you’ve got your nginx binary with IPv6 support, you need to enable it by changing listen directives in your configuration file.

If your server binds to all interfaces/IPs, you already have listen 80 or something like that in your file. Those lines should be changed to make sure you tell your nginx to bind on both IPv4 and IPv6 addresses:

For situations when you do not want to listen on IPv4 interfaces, there is ipv6only=on parameter:

For configurations that need to bind to specific ip addresses you could use similar notation:

After changing your configs and testing them you need to restart (not reload) your nginx process and then check your system port bindings to make sure it works as expected:

This is it, now you can add AAAA records to your main domain name or just create a dedicated ipv6.yourcompany.com sub-domain and show it to your friends