Search Results: "cas"

18 June 2006

David Welton: Java Conference Milano

Ciao everyone... My talk on Hecl has been accepted for the Italian Java Conference in Milan! http://it.sun.com/eventi/jc06/programma/milano_more.html If you're going to be there, let me know... it's always fun to see people I haven't had the occasion to see in person for a while. Unfortunately, I won't be going to ApacheCon Europe in Dublin, which seems like it will be a fun event. Note comments broken due to Typo being...abandoned?

Daniel Burrows: Unsubscribing from most Debian lists.

After six (seven?) years of being almost continuously subscribed, I have decided to finally remove myself from most Debian mailing lists. While I don't intend to actually unsubscribe, I even doubt I will continue reading -private. No, strike that. I especially doubt I will continue reading debian-private.


This is not a decision that I wanted to make or took lightly, but two ongoing problems, combined with my own lack of free time, have convinced me that it is the best route:


(a) Virtually all the traffic on the lists is useless. I don't think this was the case when I subscribed, but it certainly is now. The few interesting technical or procedural tidbits that I can find are buried under (and within) piles of messages that are useless flames, off-topic discussions, kooky threads, or mails that combine two or more of the above.


(b) The tone and content of the lists is increasingly hostile, personal, and aggressive. Based on what I see on the lists, Debian is not a friendly project these days. I'm sad to say it, but being able to block the rest of the Project (except bug reports, of course :) ) out will not only increase the time I have for Debian, it will increase my motivation to work on it. A lot.



The straw that broke the camel's back here was that after finally getting my Internet access back a couple weeks ago, I decided to catch up on Debian list mail this weekend. After spending a significant fraction of my free time just wading through the sludge and reading the most useful and interesting-looking of the mail that people had spewed onto the lists, I realized that I would have been far better off doing something more useful, enjoyable, and productive with my time ... like, say, picking lint out of my carpet by hand, or committing Postal Service regulations to memory.


I'm still of two minds about the whole issue: while I blamed the lists above, there are plenty of major contributors to Debian who have full-time jobs and still manage to not just read all the garbage on the lists, but actually reply to a lot of it. So I can't help feeling this is partly due to my own inadequacy or advancing decrepitude (I turn 26 in just a few months; isn't that about when your brain atrophies? ;-) ) -- but regardless, I think that I personally can't justify the "expense" of staying on the lists in terms of the benefits I get from doing so.

Christine Spang: Graduation: Many Pictures, Few Words [dialup warning]

Friday - The Party Good food. Good Food Good times. (Though, I have to admit it was considerably more interesting when it got dark and the torches were lit and we tried to avoid melting the beach ball.) Playing volleyball Helpfully labelled drinks. Helpful labels! Saturday - The Graduation Good music. Brian Maxsween, singing Good speeches. (<plug> yes, this is me </plug>) Christine Spang, speaking Saturday - After We Are Graduated In which I pose with the superintendant. Me with Dr. Rudolph Rubeis, West Genesee Superintendant In which I pose with my brother outside in the blinding sunshine and blazing heat, while thinking about the cool water that happens to be behind us. Blinded outside In which I pose with my parents and brother in a moderately more forgiving environment at home. The Parental Units In which I pose with my brother and grandparents, who could probably stand in for an alternate Matrix cast, and kick your [posterior]. At least in this picture. The Matrix In which my cousin Mark discovers that my stole is kinda fun. Peekaboo! In which a good friend of mine gives me a freaking awesome shirt. This Blows I will now proceed to summarily disappear off the face of the ‘net from sometime tomorrow until late Monday or so, in which I Move To Cambridge.

Steve Kemp: What we re dealing with here is a total lack of respect for the law

Right it is 23:43 and I’m just back from a dodgy metal night - picture the winners of the Eurovision song contest but with a lesser budget. Normally this would be described upon my real blog which contains adult language, and a mixture of random trivia, sadism, and geekyness in more detail than is displayed here. (You might think this is a hard mix, but I’ll tell you it isn’t suprising if you’ve ever programmed Gtk 2.x in raw C ;) ) Anyway the reason I went to the gig in the first place was that last year one of my partners was a bass-player, and she was often playing gigs in different locations. Unfortunately for the duration of our relationship I managed to never actually hear her play. Not deliberately - it was just the way things worked out. We kinda tailed off seeing each other because I was sleepy and she lived in a different city. Actually this is a common theme with me. I once lived with a concert chello player and for the entire 2.5. years of our relationship I managed to never hear her play, or practise (and we lived together!). Again not deliberate, it was just the way things worked out. (Even now I don’t think she’s ever heard me play the guitar.) Later I had a relationship with a Swedish dentist and for the duration of our relationship I refused to let her look inside my mouth [mostly ;) ]. It was only after we’d ceased being .. close .. that I let her extract some wisdom teeth of mine. Of course she was Swedish, living abroad, and all her friends were Swedish too - so I had a lot of Swedish “friends” around that time. Maybe one day I’ll even meet a genuine blonde Swede. (I can say “hello”, “goodbye”, “I love you”, “marry me”, and “you’re cute” in Swedish!) (I’m not a slut; I just know what I like.) Anyway .. enough side-tracking. The only reason this is coming up at all is because I think context is important when writing about people that aren’t known - I hate seeing people in blogs write about “J”, or “C”, with no hint of the nature of the relationship, or why we should know/care about their actions - people are important, and if you’re going to bring them up you should explain who they are, and why they are relavent. The fact that I’ve drunk 5 bottles of cider now is also helping extend this entry If it helps I almost promise not to mention these people again. So, to recap, I’m at this metal gig, and damn they were a fantastic band. Miranda (the woman I was “with”, previosuly if not recently) was a total camera-slut, and she was technically extremely competant. I guess I shouldn’t have been suprised but I was. So, why do I mention any of this? Well I was standing outside before the band started as it is illegal to smoke in public enclosed places in Scotland (since Marche this year) and this obviously rules out smoking in a pub in the basement bar. (The bar was unstaffed since the bands playing tonight were “too loud”. Sucky having to walk upstairs to find beer.) So .. stood outside, totally under-dressed for the occasion. Almost everybody else in the (very sweaty) basement bar was dressed in monochrome and I had shiny white shoes and colourful t-shirt. Still I was one of the tattoo’d + pierced people so all was good. “Excuse me, you look like Steve Kemp”. For the first time ever somebody recognised me from my planet debian hackergotchie. Neat huh? And now it is 23:58 and I’m going to listen to some nice Rammstein and go sleep. Tomorrow I must do some Debian work, and tidy a friends flat - since they just moved out and want their deposit back. In the future I will try to keep the entries here more on-topic, unless people actually care about this kind of entry …

17 June 2006

Enrico Zini: DB-ALLe released!

DB-ALLe has been released! After more than a year of (paid) work, DB-ALLe has been released!
DB-All.e is a fast, temporary, on-disk database where meteorological data can be stored, searched, retrieved and updated. To make computation easier, data is stored as physical data, that is, as measures of a variable in a specific point of space and time, rather than as a sequence of report.
These are the main characteristics of DB-ALLe:
  • it is temporary, to be used for a limited time and then be deleted.
  • does not need backup, since it only contains replicated or derived data.
  • write access is enabled for its users.
  • it is fast for both read and for write access.
  • it is based on physical principles, that is, the data it contains are defined in terms of omogeneous and consistent physical data. For example, it is impossible for two incompatible values to exist in the same point in space and time.
  • it can manage fixed station and moving stations such as airplanes or ships.
  • it can manage both observational and forecast data.
  • it can manage data along all three dimensions in space, such as data from soundings and airplanes.
  • it can work based on physical parameters or on report types.
DB-ALLe has been written by me on behalf of ARPA-SIM a public agency which realises that being funded with public money also means letting the public access the result of what they do:
Copyright (C) 2005,2006 ARPA-SIM <urpsim@smr.arpa.emr.it> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License
Oh, and they make an outstanding weather forecast, the best you can find for my region. It's so good that people even started to trust them! :)

Edd Dumbill: In search of agile infrastructure for web applications

Many advances have been made in agile software development. Frameworks such as Ruby on Rails embody agile principles by making software easy to write, easy to test, and above all, easy to change.If only we could say the same for the infrastructure on which we develop and deploy web applications. Not every application can be a Rails one, especially where it's been up and running for years. The systems we deploy on often rely on configuration files scattered all over the filesystem, and can be complex results of years of change.By extension, the systems we develop on often don't exactly mirror where we deploy. If we're lucky and careful, then we have a staging server which mirrors the live environment, but that's not too much of an advantage. Among other things, we need ways to evolve and refactor the live environment, and have our development environments easily track that.I'd like to call such an environment "agile infrastructure". Infrastructure that doesn't hamper developers, and allows live configurations to change and evolve. Infrastructure that allows new things to be tried with minimum cost, and can provide the best information possible to help future planning.Tools enable techniques, of course. It's a lot easier to be agile if you're programming in Rails rather than plain old PHP. So what are the tools enabling agile infrastructure?
Techniques I've found usefulWhile there's a long way to go, I'd like to describe some of the techniques I've been using to help create a flexible environment for developing a sizeable PHP/MySQL application.Operating systemAn operating system must be easy to bring into a known state with minimum interference. For this, I've found Ubuntu or Debian to be an ideal choice. Two of the main reasons include the constancy of stable releases and the fact that it's rare you need to stray outside the distribution's servers to get the software you need.DeploymentDeploying an application shouldn't break the cleanliness of your OS build. I prefer to package deployed applications into .deb files. This enables me to build on several advantages of the package management system:Source controlThe case for source control, thankfully, doesn't need making these days. Yet not every source control system is created equal. Developers shouldn't be constrained by source control, it should be cheap and easy to try new ideas and merge these in later.Not only cheap branching, but also easy merging, is required to keep development agile while still retaining the benefits of source control. Many people flock to Subversion these days, predominantly because it fixes some of CVS' more egregious misfeatures. However, merging can still be pretty difficult in Subversion.I prefer to use a system allowing easy merging, such as svk or bazaar. Because so many of us use laptops these days, disconnected operation is also a huge boon. Bazaar-NG offers both repository-oriented and completely decentralized operation, giving the best of both worlds. It also wins the competition for least setup overhead.VirtualizationPreviously a high-powered technology, cheap virtualization is now with us. Many identical virtual machines can be quickly created to enable testing and experimentation. Deployment to virtual machines can enable hardware independence for applications, reducing another big headache.Large organisations have it within their reach to bring new hardware online easily, and have invested much in management systems for it. Virtualization brings this in reach of small and one-man development teams.Desktop-based virtualizationSystems such as VMWare and Parallels untether developers from their desks. I use the OS X desktop daily for its productivity software, but an Ubuntu virtual machine for a large proportion of development work. A simple keypress lets me flick between the two. The advantages of multiple desktops to hand for web development are well known. (In fact, thanks to WINE and IES4Linux I can run Internet Explorer cheaply too from the same virtual machine).
Xen virtualizationAfter the initial novelty wears off, one of the most tedious tasks in the world is bringing new machines online. Combined with the tendency development environments have to get crufty as new ideas and tools are tried out, this makes for increasing disparity between the development and deployment environments.Wouldn't it be nice just to take a clean machine off the shelf, check out the source, and pick up again? Using Xen for Linux, this cheap virtualization is possible.Sadly, Xen isn't yet a packaged part of Ubuntu, but getting it up and running on Ubuntu Dapper isn't too hard. Warning: here's where things get pretty deep. Skip this bit if you're not interested in the nitty-gritty.I followed these steps:Getting over the DNS mountainIf you want it to be easy to bring new virtual machines up and down, you need to adopt a different approach to managing your DNS. You need to know how to predictably connect to a virtual machine. Yet it's going to get very boring and error prone to manage the IP address space manually in your DNS, or even to map the MAC addresses of your virtual machines in your DHCP configuration.
Help is at hand in the form of mDNS (also known as Rendezvous / Bonjour / ZeroConf). In the host machine, and in each virtual machine, I ensured the avahi-daemon and avahi-utils packages were installed, providing mDNS services. (You should also check that mdns is present in the hosts entry of /etc/nsswitch.conf).What all this does is allow the machines (virtual or otherwise) on the network to resolve names using mDNS. So if I create 3 VMs, alpha, beta and gamma, I can access these right away using the hostnames alpha.local, beta.local and gamma.local.Hey presto! Easily make machines appear and disappear without any need for sysadmin involvement. All the extra steps to add avahi installation can be easily scripted with xen-tools, to reduce the number of commands needed to birth a new machine to one.With this ease of creating new machines, it's much more straightforward to experiment with server topology and conduct experiments on server environments.ConclusionAgile development is necessarily constrained by the infrastructure on which it is conducted. The infrastructure itself is constrained by the tools and platforms of choice.By appropriate tool choice we can reduce the commitment and overhead of infrastructure. This enables developers to get on with the job they do best, and makes experimentation and evolution of infrastructure much simpler.When programming, it's dangerous to fall in love with your code, as the best solution may often involve throwing half of it away. The same hazard exists with infrastructure, with bizarre and awkward effects propagating back into code and operations. Get yourself a low commitment, agile environment, and you'll be able to keep up with the pace. 

Wouter Verhelst: It's life, Jim, but not as we know it.

...or so Spock said. Apparrently. Yesterday, for some reason, I was reading something on Wikipedia. Don't ask me what I started with, I don't remember; however, my journey through Wikipedia eventually got me to the Rare Earth hypothesis, the Principle of Mediocrity, and other related things. Both are subjects relating to whether or not there would be life on other planets. The latter claims that this is, in fact, quite likely; the Principle of Mediocrity basically says that "Earth is a relatively ordinary planet orbiting a relatively ordinary star in a relatively ordinary galaxy which is one of countless others in a giant universe, possibly within an infinite multiverse". This is supported by a number of astronomical findings. The contrast to that, the Rare Earth hypothesis, claims that Earth is, in fact, not a very ordinary planet. That to be able to reach a point where complex multicellular can have evolved—such as on Earth—such a high number of variables have to have the exact right value, with in many cases such low margins for errors, that while possible, the likelihood that life would exist on other planets is very low. They were both interesting reads. However, there is one thing to which I did not find an answer: Why does it have to be Earth-like life? As I understand the theory of our origins, life began on the Planet Earth in a relatively stable body of unclean water—known as the "Oersoep" in Dutch, though I couldn't find the English term for that—on which the sun shone; that sunshine made the elements of the "oersoep" react with eachother so that it eventually formed single-cell life, which then evolved into multi-cellular life, and so on. Even today, the sun still shines on Earth, and almost all energy in use on Earth can in some way or another be attributed to something that once received sunlight; I suspect the only exception to that is nuclear energy. As I understand the Rare Earth hypothesis and the Principle of Mediocrity, both seem to assume the basic premise that the only way in which life could evolve is the way in which it evolved on Earth; that is, you need direct sunlight so that you can have some chemical reactions. You cannot have too much ultraviolet, gamma, or x-ray radiation, because that would kill life. You cannot have too many impacts of extraplanetarian bodies, such as comets or asteroids, because these impacts and the resulting fallout would destroy life. I did not find any argument for that assertion, however; and what I don't see is why it would be necessary. We could define the "oersoep" as some sort of a "stable chaos": a bunch of chemical elements and a varying external influence (sunlight) means that you have a brewing and reacting bunch of matter, where the composition of the matter is constantly changing; however, at the same time, when viewed over a large amount of time, not much did in fact change. The varying external influences have a regular and stable rhythm; the sun appears in the morning and disappears in the evening. The sun shines longer in summer than it does in winter. While it is not the same all the time, there is predictability. If a number of chemical elements react with eachother in a certain way on one day, then they will react the same way again the next day. If this happens for years on end, you may have a series of reactions that is more or less reproducible, where the final result of all the chemical reactions turns out to be the original starting point again. At least almost so. Such a series of chemical reactions could be called "life", especially if it occurs within a small group of chemicals that sticks together, like a cell. While a body of unclean water with regular sunshine certainly is one way to get to a series of repetitive chemical reactions, I fail to see why it would have to be the only possible way. If there were a planet composed mainly of Helium (rather than Hydrogen and Carbon, as on Earth) but also containing a bunch of other elements (so that they can react with eachother) with a star that sends out lots of gamma radiation and an atmosphere which blocks sunlight (I don't know whether Helium can do that, but let's assume it can), then I do not see why it would not be possible for life to evolve on such a planet which would be based on Helium rather than Carbon and Water, and which would require gamma radiation to survive but would die when brought into prolonged contact with light, just like we will die when brought into prolonged contact with gamma radiation. Another example could be a planet where every year a comet of approximately the same composition impacts on the same place on the planet's surface. Such an impact would regularly stir up the chemical elements on this planet, and could provide the needed energy to produce the chemical reactions required to sustain life. If any life were to evolve on this planet, not only would it be able to survive such constant extraplanetary impacts, it would also require these impacts to continue in order to survive. I haven't been able to find any information on that. It would seem that either I'm missing something very basic, or that nobody has thought of this before—and I would find that highly unlikely. So, anyone who's been thinking longer than me about this subject (that is to say, just a few hours) who could enlighten me? Of course, one answer could be to say that God created all life, and that the evolution theory is only a theory, which is not grounded in any reality. But make a comment to that effect on my blog, and I will moderate it away. After having a good-hearted laugh at it.

Martin F. Krafft: Parsing arguments in a shell script

Since shell is a rather unpredictable programming language, which seems not to allow manipulation of variables in parent processes, parsing arguments has always been a bit cumbersome. For instance, check out lines 74 through 123 of /usr/bin/deb-reversion (package devscripts) for the way I used to do things, which involves a sort of state machine to handle options taking arguments. Just last night, I came up with another means, and while it felt like an incredible hack at the time, I am starting to like it. This method can be combined with getopt, I just use it to parse guessnet test lines in /etc/network/interfaces right now:
eval $(while [ -n "$ 1:- " ]; do
    case "$1" in
      mac) echo MACADDR="'$2'"; shift;;
      essid) echo ESSID="'$2'"; shift;;
      ie) echo IE="'$2'"; shift;;
      *)
        echo "$ME: E: invalid argument: $1" >&2
        exit 1;;
    esac
    shift
  done   exit $?)   exit $?
When this is done, any (or none) of the three variables MACADDR, ESSID, and IE are defined in the shell script's environment. If an argument is required, I can do checks following the loop, or use getopt to parse $@ before looping over its components. Of course, the last line really does make it look like a hack, but it works and it's flexible... If I now look at /usr/share/guessnet/test/test-wireless, I wonder how Thomas Hood managed to get things working, specifically because he sets variables inside a while loop, and then uses them outside of the loop -- exactly the sort of construct that drove me nuts previously. Maybe it has to do with my religious use of set -u, maybe not. In any case, I am simply not willing to investigate.

14 June 2006

Ren&eacute; van Bevern: Breaking the Lisp reader: Call Templates

There are a lot of things to do in the case that a lecture turns out to be not very interesting: playing Jump'N'Bump with fellow listensers or ... spontaneously getting the desire for currying in Common Lisp. Because such a lecutre is not only a minute short and an implementation of things similar to currying is not very difficult and has been done already, I turned out with something different, that I now name call templates. The idea is very much the same as with currying: leave out arguments in a function call and you get back a function that consumes the missing arguments and eventually returns a result if all arguments have been given and a function otherwise. With call templates you can not only leave away arguments at the end of a function call (like currying works in i.e. Haskell) but also in the middle. This makes nice shortcuts for constructs like: (remove-if (lambda (x) (< x 2)) ...). You can write place holders in your function calls. You can use call templates like currying (note that I introduced a -syntax to ease the usage):
(setf (fdefinition add5)  + 5 )
(add5 80) → 85
And basically, the placeholder thing works such that list 'a ?2 'b ?1 'c 'd yields the following function:
(lambda (x y z &rest; args)
  (apply #'list 'a x y 'b z 'c 'd args))
Here are some examples for their usage:
(remove-if  > 10  '(8 9 10 11 12)) → (10 11 12)
(mapcar  / ?1 2  '(2 4 6 8 10)) → (1 2 3 4 5)
( list "a" ?2 "b" ?1 "c"  1 2 3 4) → ("a" 1 2 "b" 3 "c" 4)
 + 3  2  → equivalent to add5 above
The code that implements the new syntax for call templates is not very long and can be found here.

Wouter Verhelst: Ubuntu Main and Debian Developers.

One of my packages, the Linux kernel's userland support tools for the Network Block Device was chosen by Ubuntu developers to be part of their 'main'. For those not very comfortable with Ubuntu: the "main" part is their idea of "this is what we support". Everything in main is free software and supported; things that are still free software but are not supported yet, are moved to their "universe" instead. Most Debian packages live in Ubuntu's "universe"; only the desktop environments that they support and their dependencies are part of Ubuntu's "main" section. Occasionally, I was told that the nbd source packages were moved to main because ltsp declares a Depends: relationship on them, and it was decided that the ltsp packages should be part of main. Personally, I don't use Ubuntu (though I've installed it a few times in the past, being the curious software geek that I am). As such, I don't really follow their development very closely, being more focused on Debian unstable instead. This would normally not be a problem, except that I do care that my packages are in a good state when they are released by someone, whether that someone is Debian, Ubuntu, or anyone else. What triggers this post is the fact that Ubuntu has shipped Dapper with nbd 1:2.8.3-1, with a context of this changelog entry:
nbd (1:2.8.3-2) unstable; urgency=low
  * Steal patch from CVS for nbd-server.c to make children exit when they
    finish serving, rather than having them loop over "Help, I can't accept()
    anymore!". Closes: #350357.
 
 -- Wouter Verhelst <wouter@debian.org>  Tue, 31 Jan 2006 11:17:25 +0100
#350357 is a bug of severity important, and rightly so. From the bug report:
Jan 28 14:42:58 caradoc last message repeated 1190456 times
Jan 28 14:43:59 caradoc last message repeated 2478818 times
An infinite loop producing an error message, a bug which triggers when a client disconnects. Have two clients connect, then disconnect, and you have a syslog being filled up with spurious error messages, filling your entire disk in a few hours or days. It may be too late to update dapper now; however, had I been asked after #350357 was filed whether it would be a good idea to ship with this specific version of nbd, I would have said "no", and this horribly buggy version of nbd wouldn't be in a released version of Ubuntu. And since #350357 was filed a few days before the above log entry, in January, I cannot believe that it would've been too late. Of course, if anyone from Ubuntu is reading this and can tell me that yes, it is still possible to update nbd in Dapper, then by all means, please do so. Oh, and don't forget to update edgy while you're at it :-) That being said, I'm hoping something can be done to avoid this kind of SNAFUs from occurring again. Ubuntu could talk to me for those packages they care about, which (according to their policy and the status of nbd in their distribution) includes nbd. As it is, Ubuntu is just a large institution that happens to redistribute parts of Debian. I'm getting more feedback from the guy doin the 'nbd-server' port in FreeBSD than I'm getting from Ubuntu—and that FreeBSD guy only once or twice sent me an email...

Andreas Barth: How to get xorg-x11 (6.9) out from testing

Basically, this seems an easy task. A few days ago, britney already considered itself happy enough to allow xorg-x11 out, but traded that in for uninstallability of gnome-desktop-environment - which was of course a non-option, as that would break most etch installs. To keep gnome-desktop-environment installable, totem needs to be installable, and for that, totem-gstreamer and totem-xine needs to stop depending on xlibs. This is an easy rebuild, except that xine-lib in sid was RC-buggy. After an maintainer upload fixed that, everything seemed settled. Until we noticed that xine-lib cannot be build, as the new gstreamer0.10 version in sid prevented any builds on buildds because it couldn't work as build-dependency if there was no home directory. This was solved by an fast maintainer reaction after this feature was marked as being in the way. Unfortunatly, at the same time as gstreamer0.10, also gst-plugins-base0.10 was uploaded to sid. That shouldn't make any difference, except that the new totem builds also depend on the new version of gst-plugins-base0.10. As gst-plugins-base0.10 is working, that is not an issue. However, gst-plugins-base0.10 also depends on liboil. And in unstable, there is a very technical interessting RC bug #368991. So, the next task is to resolve that bug report - any help is welcome. Let's see what is next. Update: In none of the cases, I was complaining about the maintainers. I know that some of the bug reports are really difficult, but e.g. looking at the most recent bug report, the maintainer seems about to fix it locally in this lib (though one might want to argue that gcc should be able to get it out by itself). My intention was to show how long sometimes a rather simple thing could get. In the beginning, all was a "simply rebuild" - now we have a rather large block of packages clueing together.

Gunnar Wolf: On the current Oaxtepec weather

Turns out my blog is becoming some sort of metereologic forecast for Oaxtepec... Would you say it's because Debconf is getting dangerously near?
Replying to H01ger's question on IRC: It is raining. More than usual for this time of year. It's a good thing, though. Why?
10 days ago, I was bitterly complaining April was the hot season in Mexico. Rains usually start in mid- to late- May - But this year, they came a bit early, and this week we have had low to medium intensity rains almost every evening.
Now, how is the rainy season in this part of Mexico? Unless it is extremely rainy (we get a couple of such days in August/September), most of the day will be sunny, and at around 16:00 it will start getting cloudy. Rain usually starts between 18:00 and 20:00. If everything's fine, then it will be gone by 22:00 - it might go on a bit longer, but usually it does not.
So don't worry, a bit of rain will not spoil your sunny days in Oaxtepec. It will make the heath much more bearable.
Or at least, I hope so ;-)

Gunnar Wolf: Hot

Ok, the time has come: Now I work with my 20" fan on. Lucky me, my office has no windows, it's in the middle of the building - A bit cold in the Winter, but that's OK with me... But the people with real windows have been sweating for some weeks already. Well, design details of a 50 year old building which cannot be moved :)
Anyway... For people coming to Debconf: Be prepared for hot weather. April-May is Central Mexico's hottest season. For Mexico City, it means we have reached 30 Celsius, and will probably reach them again a couple of times (this week's forecast says we will be under 28, which is good news)... But for the Oaxtepec region (the closest cities are Cuautla and Yautepec) we are reaching 33-35 Celsius every day.
By May, we will have the first scheduled rains (although this has been a rainy Spring, but still, it's formally the dry season), so I hope it will not be _that_ bad... But be prepared to sweat.

Gunnar Wolf: I just love this place...

Today, Nadezhda and I went with jyr and Tigre to get some more details ready for Debconf 6 at Oaxtepec. Among lots of work, we met with Gnaro to talk about connectivity issues. A nice, productive day all in all - If you care to check, I uploaded today's (raw, no descriptions yet) pictures together with today's information at the bottom of my Oaxtepec gallery - Yes, it's a whole bunch of photos, and my connection is quite mediocre (512/128 ADSL line), but there it is :)
But the reason I am writing is that Nadezhda and I decided to drive back to Mexico down a smaller road that goes from Oaxtepec to Xochimilco, through Milpa Alta, in the high and rural area of Mexico's capital. We didn't know if this would end up being a good idea or a terrible one, as anything can happen in our rural roads. Being straight pragmatic, it was very good - We made a bit over 90 minutes end-to-end, and we saved around 130 pesos (10 euros) of toll roads. But the real win was to have some beautiful landscape session.
Sadly, we are at the beginning of the fire season (read: the hot season, where a spark often arises in the tall grass and forest fires break. All of the Cuautla and Oaxtepec region, as well as all the way up Tlayacapan and until Tlalnepantla had thick smoke which took some of the beauty off the beautiful small ridge that finishes at the Tepozteco - here are some simple samples. After that, we crossed an area of fields of nopales - yes, you will get to taste them... But in my case, I enjoyed seeing some nopales fresh cut (first link), some others with the leaves ready to be harvested (second)... And just the shape of the mountains. And then, although somewhat clouded, our beautiful volcanos. I don't know what Popocat petl and Iztacc huatl have that they make me drool. Every time we have clear skies in the city, I look for them. They are probably the greatest symbol of all of Central Mexico - And although today they look sadly a bit greyish, I still had the change to see the glaciars that were lost due to the global warming in the last 10 years. And after some time travelling with my dear volcanos on the right, we reached one of my favorite spots on this planet.
This little road is even better during May/June-October/November, during the rainy season, the way I had met it a very long time ago... The brownish colors are all green, as south of Mexico City towards Morelos, it is very fertile ground. Still, even after five hours of being home, I'm still wholly satisfied at the beauty I could half-look at while driving.

Gunnar Wolf: Frustration comes on ISO/OSI layer 2 (or: On one of the ways 3Com sucks)

Over one month ago, I truly hoped an evasive network misbehavior issue was solved. In the institute, we had a strange situation which caused a (seemingly random) stack of switches to go out to lunch and leave one of the floors without network access until it decided to restore itself (usually power-cycling it was not enough). The equipment, ten 4200 SuperStack switches, is new, we got it ~September, so I expected 3Com to give me at least some support on the issue. The behavior was apparently random, and I could not track it down, only (thanks to the very nice Cacti) prove it existed.
December 5 was terrible. The whole building's network refused to work. Switches were able to reply to my pings for no more than a minute after booting before they got flooded with "Spanning Tree CTRL MAC PAUSE: Quanta 65535" (according to another great tool, the Ethereal protocol analyzer).
I had been bugging the support people at 3Com for at least three weeks before this incident, they kept promising they would come soon to help us track the cause of the ellusive problem - We threatened to send the switches back and pursue reimbursement through whatever means we could (we had much better stability and performance with our old 10Mbps hubs, so my boss insisted on replacing them), so we got them to come. The answer they gave me? Upgrade your firmware to version 2.50 (not available at their website, of course) and disable spanning tree functionality at the switches.
I have to admit the big problem immediately ceased. This is not to say I was pleased with the response time or with the switches' software quality, but at least we could work.
Happily, ~7 weeks passed by with no major outages (although with a few small ones).
Yesterday, we got back the complete chaotic conditions. This time, though, I was able to get a good and useful tcpdump snapshot, passed it through Ethereal, and actually got something interesting (available to whoever requests it to me if it sounds interesting). In short: Something happens that confuses a switch (I guess it's a faulty NIC), and makes it request to all of the neighbouring switches (via spanning tree protocol - Yes, it's disabled, but still) for their complete ARP tables. But somehow, this noise or whatever keeps confusing it, so the spanning tree requests start repeating every two seconds for slightly over one minute. Then, the same switch which requested this information gets tired of too many ARP tables being thrown at it, and sends out a storm of packets (one each 0.04 seconds) asking every other switch _not_ to send updates anymore. This is broadcasted to all of each of the switches' ports, and the network dies.
My grudge against 3Com is: How come this frigging noise (at least that's what I assume it to be) on one of the ports kill all of the network? If a switch is supposed to be smart, would it be too much for it just to disable the misbehaving port?
Anyway... One and a half days went down the drain trying to find the cause for the problem, sending the report to the 3Com guy (who is very nice in person, yes, but that's by far not enough!), running up and down the stairs to reset different switches, lock down on the source of distress... And as my 3Com contact was busy with another client (who presumably had not yet given them money), I never got a call back from them.
All my good intentions to spend a nice quiet time coding for three projects we currently need to have ready soon (one of them is in production and many of you have used, my dear Comas conference management system, but requires heavy tinkering to be able to extend it) were stuck at that: Good intentions.
I seem to have locked down the problem in one of three computers (that is, network seems stable again once I disconnected them). I insist it must be a faulty NIC. My boss bets it's an ber-contaminated Windows machine. My boss' boss insists we should get the switches double-grounded just to be sure that's not the reason for failure. I am tired, bad mooded, and -again- bored you to death with a too-long blog entry.
Blame it all on 3Com.

13 June 2006

Bartosz Fe&#324;ski: Debian GNU/kFreeBSD

When I bought notebook I had to find out some use for previous box. It was great opportunity to test etch installer (and my Polish translation at the same time) so I did it several times using miscellaneous settings. Eventually it was time to find out some real use for this box. I decided to try out some non-Linux port of Debian. The most stable and actively developed seemed to be kFreeBSD.
I installed it about month ago. I must admit it works great despite some initial stability problems related to buggy mount, quickly workarounded with help from people from #gnu-kbsd channel. (thanks!)
I use it mainly as a backup machine and small www server, but since it handles it without a hitch I'm probably going to make it also print and Samba server.
I was sceptical to GNU userland used with non-Linux kernels, but admittedly we're getting closer and closer to the day when switching between kernels would be piece of cake ;)
(fenio@kfbsd)~#uptime
 15:36:57 up 21 days,  6:23,  1 user,  load average: 0.23, 0.08, 0.04
(fenio@kfbsd)~#
As you can see it works. It lays in one of my wardrobe, without the case and unplugged from any external devices. I couldn't remove graphic card due to some weird BIOS limits, so it has some PCI card worth less than the beer I'm drinking now ;)
Here's its photo. Sorry for quality, but I don't have any camera around, so it's made with my cellphone.
bsd
If someone wondered if non-Linux Debian ports are worth try, then I have to say YES, THEY ARE!
Using this opportunity I would like to thank everyone involved in their development. Keep up the good work!
Now it's time to give a try to Debian GNU/Hurd... have to start gathering the hardware for that ;)

Biella Coleman: The AAA does not support open access

As soon as summer hits, my muse takes an extended vacation and I only write sparingly and occasionally (and somewhat painfully without the muse). But as soon as I read and heard from a number of places, notably Savage Minds that the American Anthropological Association is lobbying against open access, I decided to work against my disinclination to write to say a few words. Rex at Savage Minds, as well as others have already covered thoroughly and thoughtfully, the basic issues as well as why it is incredibly problematic for the AAA not to endorse what is an otherwise powerful and positive Federal initiative that would require final mauscripts based on federally funded research to be accessible to the public after 6 months. So I wont be redundant here and will keep this short, but I would like to say that in an era in which government roll-backs (and in nearly every quarter of life) are simply commonplace and causing a fair deal of social problems, any initiative in which there is a push to make scholarship, *based on federal funds*, public and accessible, seems imperative to support, not squash. Many anthropologists, as probably many scholars, I imagine,like to think that some of their work has some public import and as such, we should do everything possible to make the work as accessible as possible, which will also give access to the communities and people we work with. They mention the supposed threat open access will have to peer review. First I don’t think that arguement stands up and more important, if peer review is simply a self-referential exercise, in which it can’t happen in a context of openness and accessiblity, what good is peer review?? Given the recent AnthrSource Initiative, as well as the general open/populist/ liberal/downright radical political inclinations among anthropologists, and the fact that the discipline in the last 25 years has been somewhat obsessed with the question of ethics, I was quite shocked at this move. But apparently (and thankfully) there were very few people at the AAAs behind the decision, which is somewhat comforting. What I hope now ensues is the formation and expression of a very strong response among the members of the AAA asking for a response from our elected board and an eventual rethinking of this stance.

Jonathan McDowell: Ooooh. It's all pretty.

I had a rant about Firefox today on #debian-uk. Mainly the fact it seems to like to guzzle memory and bring my system to a crawl when it feels unloved. Which is every time it loads an animated image as far as I can tell. Matthew suggested Epiphany so I thought I'd give it a try. Seems ok, but looked a bit blocky, like GTK apps do for me. Not shiny and curvy like people who run a GNOME desktop (I run the excellent evilwm). So I had a poke around. And the magic is to run aptitude install gtk-theme-switch gtk2-engines and then switch2 and pick a theme and marvel as your GTK apps become sexier. Of course you probably all knew this. I'm impressed with how it's affected GNUCash, liferea and workrave as well (yes, yes, that's the whole point of theming, but I'm a simple creature who mostly runs xterms). Time will tell if Epiphany actually sucks less than Firefox. And there's still the leaking bucket that is liferea (253MB? Eh? And that's with the optimise for memory option enabled).

12 June 2006

Martin F. Krafft: Norwegian Wood

During my travels in Southeast Asia, I had several chats with a fellow traveller from Portugal, who also seemed to enjoy Haruki Murakami, and other works by modern Japanese authors. She was surprised to hear I did not like Norwegian Wood, which was her first Murakami, and brimmed over with enthusiasm about discussing Murakami (who's been my favourite author for about a year now), I promised to reread the book to find out just why I didn't like it. Here's what I came up with:
Norwegian Wood was the one of Murakami's novels that I didn't like at all, wish I had never read, and by which I felt "cheated" and let down by what may well be my favourite author for the time being -- well, maybe Dance Dance Dance is also one of those. It was previously impossible for me to determine exactly why I felt so bad about the book, which made this reread a little more challenging -- and rather interesting in the end. Norwegian Wood was my third Murakami novel, after I had read the Wild Sheep Chase and After the Quake. Up front those reasons that I think made me dislike the book the first time around: the story line of Norwegian Wood is absolutely boring and way too autobiographical, and the ending is painfully artificial. In fact, half way through the book, the story takes a turn (I cannot pinpoint the exact moment), around which I often put down the book in refusal, annoyed and disappointed. If I say that the story line is boring, I mean that it's a boring foundation, but as with all stories, it's in the author's hands to make it into an exciting novel. Murakami fails in this novel, in my opinion (he claims he set out to achieve something else, that this book was a challenge to him). Anyway, I do remember from my first reading that I really liked the tension and potential in the character interplay Murakami describes in the first half of the book, and I anticipated a deadlock between them, which would have to be solved by Watanabe (the main character) in a lose-lose type of resolution. However, what happens is that everything sort of resolves itself, dragging the characters along. It never touches once on paradoxical or supernatural elements as found in most other Murakami novels, which is a shame. Furthermore, it's a love story, and one with too many romantic and melancholic moments for my taste. Upon rereading (having gone through another four Murakami books in the mean time), I noticed a number of other things that disturbed me, or otherwise came in perpendicular to my taste: Toru Watanabe, the main character, aged around 20, goes through a great deal of effort to make sure the world knows he's just ordinary. Yet, the way he swings life is just a little too good for the ordinary. Throughout the book, you get the impression that he's not very happy or satisfied with his life, yet if you look at the days he fills, you'll tend to see them as complete. This turns Watanabe into a grouchy pessimist, and that mood transferred to me as the reader. On a side note: one thing I definitely like about Murakami's main characters (at least those I have met) is their self-sufficiency: the whole world could vanish and still they'd continue doing what they always did. In some ways, I have found myself in those characters, but more often I find myself looking up to them and wishing I could be like that. Watanabe is, however, just too much of a polished character (and with that I don't mean polished to be good, just polished), and one that seems to do everything right when it comes to the moral level. Sure, he asks himself about moral issues here or there, but my feeling was always that Murakami put those monologues in for completeness, not for character. I find it hard to imagine a boy between the ages of 17 and 21 (which is the years the book covers) with traits like Watanabe, and such integrity: he's never dishonest or even plagued by the possibility, and he appears to be consciously doing everything he does. He ends up in bed (or close by) with one of several girls he devours on a number of occasions, but each time stays in absolute control, not allowing himself to "do it", or accepting whatever excuse comes =66rom the girl. I don't mean to say that this by itself is unlike a boy at his age, but I guess what I am really lacking is a reflection on his thoughts, or at least some insight, which Murakami withholds each time. It would have added a lot of tension to those moments, made them even a bit erotic (which despite all the sex and sexual references, I found none of the book to be). Finally, there is almost no character development in the novel. Even though the time span of the novel spans a very important time in the development of a boy, he does not change much, nor does his perception of the characters around him (the book is told in the first person). In the end, despite a serious lack of motivation to read on throughout most of the text, I think I did learn to appreciate it after all. On the one hand, Murakami hides many little gems of thoughts in the conversations with Midori, the girl ready to shake up Toru's life, which often have Zen-character ("I wonder what ants do on rainy days"), and it did take me a reread to notice those -- and I smiled every time I did. On the other hand, the reread did allow me to get a closer look at the relationships between the characters, and how Murakami explores them, mostly with parallels referencing the past. He remains in my eyes as one of the most imaginative writers of modern literature, and while it strikes me as easier to be imaginative in an imaginary story, the challenge is all the more as you move into real life, and in this case: real life as tangible as it gets because of the elements of love.
I am still looking forward to my next novel, which will either be Murakami's Wind-Up Bird Chronicle (which is said to be his best), a book recommended to me by the aforementioned traveller (Lizard by Banana Yoshimoto), or one suggested today by my physiotherapist, but I fail to recall the name at this moment and shall have to wait until I receive my next treatment on Wednesday.

Robert Pickel: some updates

What I did this week:

I wrote code that contains many "bashisms" but runs, this is the code that detects boot paramaters from the user for a few boot options. I would like to combine the boot params into on parser that sorts through all the user entered boot options instead of looping through them xxxxx times during the execution of casper-bottom scripts.

I had a rough time testing the changes I made to casper-ng, so I started to work on a tool that will be used to easily unpack, pack, and modify images created by live-package.
This did divert my attention for a while, but not too long.
  • Its called live-helper and can be found in the subversion repo.

Worked on documentation, explaining the theory of operation behind casper-ng.

  • I am currently in the process of finishing up the casper-ng documentation, you should be able to grab this in a few hours using subversion.

Cleared things up Marco, he will work on the initramfs hooks and I work on the casper-bottom scripts. I finished up removing some code that modifies the root files system at boot time and moved it to postinstall. However, I did go a little nuts with this, and was asked by Marco to keep this to a min.

  • I will work on casper-bottom scripts, he will work on the mkinitramfs hook (image detection and so on)

My plans for this week:

  • Adjusting casper-ng documentation after a peer review by the debian-live group - this will be ongoing for the rest of SoC.
  • Experiment with some hardware detection, creating some images and testing on as many machines as possible (I am limited to mostly i386) - plan on using discover
  • I think it will be possible to use yaboot to boot debian-live on ppc & ppc64 unfortunatly the only box I can test on right now is an experimental blade server that IBM donated to a research project I work on at school (not ideal)... I have to find some people who are willing to test ISOs for me or a good emulator.
  • Start examining the scripts executed once casper hands everything over to init on the rootfs - I get some weird errors somtimes, prob because there are some saved setting from the box that created the iso. Modules that are installed at boot time etc.
*POST AS MUCH AS POSSIBLE: my mentor is starting to freak out because I did a poor job of keeping him posted on my work.

Next.

Previous.