Search Results: "ag"

9 June 2008

Igor Genibel: Premi re s ance

Lev t t pour tre frais et dispo pour la premi re s ance, je me suis pr par rapidement. La nuit a t assez courte, couch vers minuit pour finaliser le support de cours. Enfin, il est pr t. J'ai juste quelques ajustements y apporter et il partira pour l'impression. Mieux vaut tard que jamais ;) J' tais donc pr t 7h30 pour un petit d jeuner ma foi agr able au bord de la piscine et accompagn de Tisserin et de la superbe Grue Couronn e quelques dizaines de centim tres de moi ;) Un petit tour au coin wifi internet pour envoyer 2 ou 3 mails et me voil attendre. Tout compte fait, j'ai d attendre jusqu' 10h30 pour que l'on vienne me chercher. La salle n' tait pas disponible, les petits tracas administratifs de derni re minute. Une fois sur place l'ENA (Ecole Nationale de l'Administration) je me suis lanc pr senter le syst me 25 personnes. Mais impossible de faire fonctionner loe r troprojecteur mis ma disposition. Pb de configuration Xorg voir ce soir. Donc j'ai projet mes transparent fait avec MagicPoint g n r s en HTML sur une machine sous Windows. Apr s une br ve introduction nous voil partis dans le vif du sujet. Les stagiaires taient tout ou e et donc je n'ai pas m nag les informations dispens es. Repas 14h frugal pour ma part, je n'avais pas trop faim. Poulet en sauve, crudit s, riz, pommes de terre. Me voil reparti 15h pour la deuxi me partie de la journ e. J'ai demand aux stagiaires de se pr senter... Bon, il va falloir que je fasse les bases des syst mes Unix pour tout le monde sans exception. Seance fini vers 18h o je suis rentr l'h tel, seul. Donc au programme de la soir e, remplir mon billet quotidien, r cuper la conf Xorg me permettant d'utiliser le r troprojecteur, manger et ensuite rododo ;)

Neil Williams: reportbug-ng - unfit for purpose? Absolutely.

Bastian, I had cause to reinstall this machine and the one thing that I decided not to do was install reportbug-ng. I've tried it, I've found problems with it that are clearly documented already in the existing bug reports (so I haven't added a me-too) and I cannot understand why there is such opposition (without any cohesive counter-argument that I have seen) to reportbug-ng handling the bug scripts carefully designed by maintainers (like me). Please, just do it - this could have been resolved months ago if this bug had been fixed when initially raised. Your opposition to this functionality makes no sense to me. This isn't something that one person in the Release Team has decided, this is something that irritates your fellow developers and the
actions of the Release Team merely reflect the opinions of others of your peers
.

Emdebian uses bug scripts and also needs various bug scripting tools but all I'm going to do is script around reportbug - explicitly because the maintainer scripts must be handled by any sane bug reporting tool. This is not optional. As far as I am concerned, reportbug-ng is unfit for purpose and has been so since this whole issue was raised.

If you are going to complain about decisions appearing arbitrary, maybe the lack of bug script support in reportbug-ng should be explained in a cohesive, logical and persuasive defence. Merely stating that it is not what reportbug-ng will support is completely unacceptable IMNSHO.

If the bug scripts are never to be supported, I would recommend accepting the decision of the Release Team and moving on to a different package because reportbug-ng will never be an acceptable bug reporting tool whilst this functionality is ignored.

If reportbug-ng was to be released in Lenny it would make my life a log harder because I need the information retrieved using the bug scripts in the package. These are not arbitrary, the scripts are carefully written by your fellow developers to get more useful information in the initial bug post - this is particularly important when some bug submitters can take significant amounts of time to respond to a "moreinfo" request. (I would even consider conflicting with reportbug-ng to prevent such chaos.)

Why does reportbug-ng assert that it knows better than I what information I require in a bug report against my own upstream or Debian code? Clearly, that is nonsense.

Why must reportbug-ng users be subjected to inevitable requests for more information or recommendations to use a sane bug reporting tool? Please just fix it, it really is the only sane option.

David Welton: Startups: government help and hindrance

Aaron Swartz writes about what government might do to encourage entrepreneurship: http://www.aaronsw.com/weblog/prostartup As an American who has lived in Europe for a while, I've seen both sides of the coin (or pond, as it were), and feel qualified to add a few things to the conversation, even if many of these points merit a discussion of their own. And here are some thoughts of my own: I think it's best to focus on the startup "curve", and costs associated with various points on it: when people are just getting started, keep state-imposed costs low. If someone makes a lot of money, worry about taxing it then. This is quite different than what has previously been the norm in many places in Europe, which have policies akin to slaughtering the goose before it lays any eggs, let alone golden ones. Italy is a particularly bad example, but it's the place I know best, and not too far off what happens elsewhere in terms of policy: fixed, sunk, startup costs are in the order of 10,000 Euro, which for most people is a lot of money. This creates a bias towards people who already have a lot of money, and away from random people who happen to have good ideas and a strong desire to execute on them. This is something that the US more or less gets right: it cost me $55 in state fees to start DedaSys LLC as a limited liability company (even throwing in money for lawyers and the like, you're still far under the thousands it costs in many European countries). Incidentally, it looks like Germany may be on the right track, if you look at the "Mini-GmbH" mentioned in the article. It's progress, if nothing else. Beyond that, there is a lot more red tape in Europe, and that, I think, rather than a bit higher taxes for companies that are profitable, is the thing that, outside of culture, probably weighs most heavily on European startups. Culture, however, is also a very key factor, and not something that will change soon or easily. In Italy, there's a lot of pressure to land a permanent job, from which you can basically never be fired. The idea of striking out on your own is probably simply not on most people's radar screens. I think culture is what means that Europe produces tons of great open source software, for example, but relatively fewer startups (if you're just counting open source startups though, Europe does ok). Perhaps this is slowly changing, but it will take a while, and without some policy changes, the incentives won't even materialize. Returning to things that government can do, something critical that many people don't get is that government funded startups are usually big failures (see the French "Google competitor") and a big waste of money that would probably simply be better to spend in lowering taxes, improving education, or other "level playing field" initiatives, rather than having government employees attempting to "pick winners". This is a common problem in Europe, but also in many areas of the US that want to replicate Silicon Valley's success. Going back to the US, which was Aaron's original point of focus, beyond health care, what could the US improve? At the moment, immigration seems to be the big problem: people from all over the world want to go to the US to work and start companies, but look at what kinds of hoops someone (who is coming to spend money and create jobs!) has to jump through to do so: http://www.techcrunch.com/2008/05/02/coming-to-america-getting-visas-to-do-business-in-silicon-valley/ Embarrassing and shameful. In conclusion, I think the common theme is that the government can't really do much to actively promote startups, but can certainly hinder them by setting too high a bar in terms of bureaucracy and fixed costs. Lowering those fixed costs for new companies, be it through at least basic health care for everyone, or lower taxes and less paperwork should be what governments aim for. Given the right conditions and incentives, bright, hard workers will do the rest.

Matthew Garrett

Things in your computer that you do not have the source code for:Anyone think of anything I've missed?

Things people have suggested:
More suggestions:

Matthew Garrett

Linux consumes less power than Windows on servers. What's interesting is that this is running on the current set of enterprise distributions, so it's missing functionality like the tickless kernel and cpuidle. Within the next year or so we should be seeing the Linux figures drop by significant margins. As companies start becoming interested in either reducing their energy costs or cramming more hardware into the same machine rooms, power efficiency becomes an important factor to consider when you're choosing the OS you're going to be running for the next 5 years. Linux is the right choice now, and that's going to be even more obvious in the near future.

Christian Perrier: [life] Running pace

Dirk often blogs about running and generally posts his running paces as minutes/mile. Well, we're both geeks, so numerical challenges are logical for us..:) I follow my own 'performance' (or lack of) in terms of speed in kilometers per hour. Which makes the conversion fairly hard. Just to confirm that we live on different planets, this week, I tried to get a rough idea and then calculated my usual pace (for distances ranging from 15km to 25km, as well as short distances such as 5km): The challenge I give myself currently is not really running faster (I apparently reached a level which I can't easily break), but more running longer. My current estimate is that 30-35km could be achievable (I only need to find enough time for this) while a marathon is still out of question. Frankly, I couldn't even imagine this when I (re)started running, less than 1 year ago. Anyway, for people going to Debconf, I plan to gather the Debian runners and share the pleasure of running together during the conference. I'll probably open an "event" for this in Pentabarf. Of course, the point there will be sharing the pleasure, not performance. So, even if you are a very occasionnal runner, you're welcome.

Pierre Habouzit: reportbug-ng

Dear Bastian let's fix your blog post.
Philipp thinks, the fact that rng is not using the information in /usr/share/bug renders rng unfit for release and upgraded the corresponding bugreport from wishlist to serious. Moreover: since I dared to downgrade the report back to wishlist he decided to remove rng from testing and block it until the bug is fixed.
s/Philipp/the Release Team/g. And yes, we believe that reportbug-ng goes against the Maintainers wishes, and doesn't help users that don't know how to report a bug (and which are rng audience unless I'm mistaken).
I don t want to heat the debate about this bug again, but Philipp s decision seems arbitrary for me and I wonder if the same standard is applied to every other Debian package.
It's not, it was discussed in the Release Team and was not Philipp on his own alone. And yes, the same standards of quality is wanted for every package in Debian.
I mean, rng has no release critical defects.
That's you claiming that, there have been really constructive remarks in both bug that we upgraded, and that I think explain wisely why the current reportbug-ng behaviour doesn't makes it a suitable reportbug tool right now. I think for example that Sam's and Michael Biebl contributions in both bugs are good explanations of what is wrong and why.
It just does not use the aforementioned scripts as additional information in bugreports does this really render the software unfit for release ?
Yes it does. Again, people that use rng are I think, less experienced users, who need guidance through the bug reporting process. The kind of users that often send annoying bug reports. Instead of lowering the annoyance factor, you aggravate it. In the end, rng makes the frustration higher, and totally fails to meet its primary goals: making bug reporting nicer, simpler, and more efficient for the Reporter and the Maintainer. While it's probably nicer for the reporter, you totally fail on the other part of the contract. And if you don't care about the Maintainer, then well, reportbug-ng is just a spam machine to them, and your careless attitude toward them is unfit for release for sure.

Stefano Zacchiroli: debian weather is back

What's the weather like in Debian? One of the cool things developed during EDOS (now Mancoosi) has been edos-debcheck. Using it it is possible to check (incredibly quickly) whether some package in a given distribution cannot be installed according to its dependencies. When there are such packages it usually means that the distro is buggy s it is shipping uninstallable packages (there are some corner cases, but they are rare). In fact, edos-debcheck has been run daily (as a service maintained by Ralf) on Debian's main suites and some derivatives for years now. The resulting list of uninstallable packages is linked from http://edos.debian.net and is being used by the QA team; I've no idea if it is being used by the Release Managers too, but it probably should be. A cool toy built on top of edos-debcheck was the Debian weather (part of a more generic service called Anla, I'll blog about it sooner or later ...). Debian weather basically used to present the status of a given Debian-based distro in term of how many uninstallable packages were shipped using the weather metaphor: the fewer the uninstallable packages, the better the weather. I wrote "used to" because Anla was stopped about 1 year ago, and is being re-engineered these days. In the meantime it was a pity not to have the Debian weather (as Enrico pointed out with me), so I spent some time to resurrect it on top of edos-debcheck daily runs: Debian weather is back, enjoy!

Aurelien Jarno: IPsec, MTU & NAT

Dear lazyweb, I encounter MTU problems with an IPsec setup and NAT. Here is a simplified version of my setup: remote host --- internet ---> (eth0) gateway (eth1) --- LAN As you may have guess, the gateway has only one public IP address and thus the hosts on the LAN are connected to the internet through NAT. The connection between the remote host and the gateway is secured using IPsec (kame tools), and this works as expected as long, as the connection is done between the remote host and the gateway. The problems arise when I try to make a connection between the remote host and one host from the LAN. Due to the use of IPsec, the MTU is reduced by 44 bytes, however “ICMP need to frag” packets are not emitted by the gateway, so the connection just hangs. I have tried various solution from the web (setting MTU on the various interfaces, clamping MSS with iptables, defining advmss with ip route, etc.), and the only one which actually works is reducing the MTU on the LAN hosts. Not very useable given that they are a lot of hosts on the LAN. Note that when IPsec is disabled, if I lower the MTU of eth0, the “ICMP need to frag” packets are correctly emitted, and the connection just works. Suggestions?

Lucas Nussbaum: Text normalizer, anyone?

When I write text documents (using LaTeX or Docbook), I like to wrap lines, as it makes them easier to edit (less things moving on the screen), and allow to have easy-to-read diffs. However, I always hesitate before rewrapping paragraphs (using vim’s gqap): this mean that I will add noise to my git history. So I only do that from time to time, making “rewrapping-only commits”. But that sucks, since in the meantime, I sometimes make a lot of changes, and my lines grow long again. Of course, I could rewrap my paragraphs before each commit, but if I simply add a word to a paragraph, it might cause all the lines to be rewrapped. So I what I would need is some kind of “text normalizer” that will: I’ve looked at plasTeX: I could use it to parse a LaTeX document, and export it as LaTeX. But then it would be a LaTeX-only solution. Does anyone have a better solution?

Bastian Venthur: Lenny won t ship rng

Philipp thinks, the fact that rng is not using the information in /usr/share/bug renders rng “unfit for release” and upgraded the corresponding bugreport from wishlist to serious. Moreover: since I dared to downgrade the report back to wishlist he decided to remove rng from testing and block it until the bug is fixed. I don’t want to heat the debate about this bug again, but Philipp’s decision seems arbitrary for me and I wonder if the same standard is applied to every other Debian package. I mean, rng has no release critical defects. It just does not use the aforementioned scripts as additional information in bugreports — does this really render the software “unfit for release”? For example: In Etch we shipped a famous email client with a known bug which lead reproducibly to loss of emails on IMAP accounts, just because removing the program, or one of it’s components was not possible in the remaining time.

MJ Ray: Fixing things the wrong way

For some reason (maybe related to upgrading openssl recently), my Jabber client became unstable. Instead of fixing it the right way, I simply upgraded to Emacs 22.2 (which also got me the emacsclient --eval option mentioned on this blog previously). It still wouldn't make SSL connections at first, but a quick application of [jabber.el] Anybody using emacs-jabber with Emacs 22.2? fixed it. That's the wrong way to fix that bug, but it's not quite as wrong as misusing computers to try to fix copyright infringement. MediaDefender denial-of-service attacked a TV production company, as described in Inside the Attack that Crippled Revision3 on May 29th, 2008 at 07:49 am by Jim Louderback in Polemics MediaDefender or MediaDestroyer? That's the wrong way to fix that bug, but it's not quite as wrong as making treaties mostly in secret, under NDAs to try to evade local copyright law-makers. The US government, the European Commission, Japan, Switzerland, Australia and a handful of other countries are meeting in a secret negotiation on a new treaty
"that undermines civil rights and privacy, and which many say will change the substantive rights the public has to use copyrighted works or inventions."
Read more at Act On ACTA and then contact your law-making representatives.

David Pashley: Compiled Regexes in Spamassassin 3.2

Spamassassin 3.2, which is available in Gutsy and Lenny, comes with a new feature to increase performance by compiling its regular expressions using re2c. It's very quick to enable. First, you need to install the required packages:
apt-get install re2c libc6-dev gcc make
Next, edit /etc/spamassassin/v320.pre and uncomment the line that says:
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
Next pre-compile the regular expressions using sa-compile:
femme:/etc/logcheck# sa-compile
[18741] info: generic: base extraction starting. this can take a while...
[18741] info: generic: extracting from rules of type body_0
100% [===========================] 3293.83 rules/sec 00m00s DONE
100% [===========================] 650.12 bases/sec 00m01s DONE
[18741] info: body_0: 647 base strings extracted in 2 seconds
[snip compiler output]
make install
Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /var/lib/spamassassin/compiled/3.002004/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so
Installing /tmp/.spamassassin18741hDrlUQtmp/ignored/man/man3/Mail::SpamAssassin::CompiledRegexps::body_0.3pm
Writing /var/lib/spamassassin/compiled/3.002004/auto/Mail/SpamAssassin/CompiledRegexps/body_0/.packlist
Appending installation info to /var/lib/spamassassin/compiled/3.002004/perllocal.pod
cp /tmp/.spamassassin18741hDrlUQtmp/bases_body_0.pl /var/lib/spamassassin/compiled/3.002004/bases_body_0.pl
cd /
rm -rf /tmp/.spamassassin18741hDrlUQtmp
Finally, restart spamassassin, and you should find it runs faster. You will need to run sa-compile every time you update your rules, or they won't take effect. If you get the following warning:
Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC
you forgot to run sa-compile; re-run it and the error should go away.
Read Comments (0)

Y Giridhar Appaji Nag: It had to be a UFO

I just got back from Indiana Jones and the Kingdom of the Crystal Skull, a movie in which Steven Spielberg takes his obsession with the extra terrestrial to the next level.

Please watch it if you feel that times goes too fast, the two hours that you are watching the movie will seem like two years.

And it had to be a UFO in the end :)

Update: I should have kept the spoiler under lj-cut, but now that I think of it, that wouldn't help people aggregating the posts. I suppose I will avoid posting spoilers.

Andrew Pollock: [life] Tour de Cure ride report

Sarah and I did the 50km route of Tour de Cure today. Many thanks to those who sponsored us. It was looking a bit dubious for me making the $150 minimum for a while. Sarah raised $170. We couldn't have asked for better weather, really. It was clear, not too hot, a light breeze. The 50km route was very doable. All of the hills involved were rolling, so it wasn't too much of a slog. This was the first major bit of exercise that Sarah's done since her heart surgery, just over 5 months ago now. She held up well, but was totally exhausted afterwards. Some of the uphills were a bit tough on her. I'm totally out of shape as well, and was expecting it to be much harder as a result, but I was pleasantly surprised at just how doable the ride was. That said, we both had a decent nap this afternoon after a dip in the pool. Apparently the 75km route had some gruelling hills in it, so I think we'll stick to the 50km one if we do it again next year.

8 June 2008

Manoj Srivastava: Manoj: Using org-mode with Ikiwiki

Using org mode to write ikiwiki posts I have been much taken by org-mode in Emacs recently. Firstly, this has allowed me to actually effectively implement the tenets of Getting things done , which is amazing by itself. I always used to start with great enthusiasm, which rarely lasted longer than a week. Until org-mode. Then this is so amazingly flexible. It has better handling of tables and even a spreadsheet mode than anything I have used and it has a pretty decent HTML export function. I practically live in org-mode on work days now. I strongly recommend org-mode, from things like agendas, TODO lists, calendars, appointments, articles, and now Ikiwiki posts. I rarely ever use markdown, apart from blogging using Ikiwiki and thus, since I blog so infrequently, I rarely ever remember all the syntax. On the other hand, org-mode syntax is now at my finger tips so I decided it was time to write a Ikiwiki plugin so I can now write my blog posts using syntax I can actually remember. It is still rough around the edges firstly, this requires emacs23 (or, on Debian, there is the unofficial emacs-snapshot package), secondly, it uses hueristic hacks to prune away the bits of the stand alone HTML page that org-mode creates; all I can say is that it currently works for me, as you can see from this post. How git this is for mainlne inclusion is another matter. The code is here: org.pm. It can be dropped in to the Ikiwiki plug-in directory, and that s all you need. With this, Ikiwiki pre-process things in the input file, and then passes it to emacs to htmlize it.

Andrew Pollock: [life] And we're back

We actually got home last Sunday, but I've been too jetlagged, and then too busy with work to really have a chance to write anything... We got back in at around 2pm, but our bags fell victim to Heathrow's Terminal 5, and didn't arrive until around 11pm. I think I lasted until about 8pm, when I had to crash. Poor Sarah had to stay up until 11pm when they finally got around to delivering our suitcases. The week in Zurich was wonderful. The Zurich office is everything the photos make it out to be, and then some. One weird thing: apparently there's some Swiss regulation about how much you're allowed to cool a building in relation to the outdoor ambient temperature, so there's no air conditioning in the office. Instead, you can open the windows. Unfortunately, there's a fairly busy set of train tracks right beside the office, so it can get a tad noisy... It was a pretty warm week, I think around 30°C. I certainly prefer being colder rather than hotter when indoors, so found the lack of decent cooling to be a shame, given the rest of the building's features. That said, it was pretty amazing sweltering away in Zurich, and then looking up and seeing snow on the mountains. It was surprising how much of a temperature difference there was. On the last evening in Zurich, we went on a reconnoitre to try and find the river that we could hear (and see on the map) behind our apartment. We eventually found some street access to it, and it was another world back there. It was fairly thickly wooded, and the sunlight was heavily filtered through the trees, so it was cool and shady. The river was fairly fast flowing over some rocks in parts, which is what was making it so audible. The whole setting was absolutely beautiful. There were a couple of paths, and the whole thing felt like something out of a fairy tail. We think we stumbled onto a fox, but we're not sure. It's a shame we only discovered the place on the last day, as I'd have liked to have explored it further. I really liked Zurich. It was nice and flat, and had an excellent tram service. Monday Night Skate made me wish I'd packed my roller blades. We were wandering around on Monday night, and it felt like the entire city had donned skates and were going out. Apparently the authorities really get behind it, and close roads, and the police go along behind the pack and reopen the roads behind them and pick up the stragglers. Great way to encourage an active lifestyle. We've got all of our photos up now from the Europe trip, and they're here. This brings the total countries I've visited up to 10, excluding Hong Kong and Macau. I don't like selecting China when I generate this map, as I've never been to mainland China. Countries I've visited as of June 2008

Jeff Bailey: Recruiters; Technology ups and downs

Dear Recruiters,

While I appreciate being contacted with interesting opportunities (at the moment I'm not looking. It's a lovely cross between being happy in my current job and hoping for a particularly uneventful 12 months on the home front), emailing me from noreply@saic.com is just going to make me mock you. It's at moments like these that I with I could channel Matthew Garrett. When I try, I just sound like Overfiend from the good old days ;)

The family went up to the City today with some friends of ours and I had the most amazing thing: I walked into an Apple store, and the greater at the front solved my iPhone problem. The phone decided a week or so ago that there was always a headset plugged in. The greeter pulled up a clever tool that looks like an 1/8th inch to 1/4inch adapter with tiny holes milled in it for blowing air in. Seems they have this problem often. Being with 3 kids and two families, I couldn't reliably book a time to see someone at the Genius Bar, but he just blasted it out and it worked wonderfully.

Of course, I came home to plug it in and have discovered that the cord to connect to the charger appears to have corroded and won't charge the phone now. So, AppleEmployees++, AppleHardware--. I now will make the distinction.

Next technology FixIt: Convince my Bluetooth headset and Bluetooth stereo to go into pairing mode again. Both seem to have decided they won't do this anymore.

Russell Coker: Record Oil Prices

MarketWatch reports that oil prices had the biggest daily gain on record, going up $11 in one day. They claim that this is due to an impending Israeli attack on Iran and a weak US economy. $150 per barrel is the price that they predict for the 4th of July. That’s an interesting choice of date, I wonder whether they will be talking about “independence from Arabian oil”… The New York Times has an interesting article on fuel prices [1]. Apparently sales of SUVs are dropping significantly. The US senate is now debating a cap on carbon-dioxide production. The NY Times article suggests that if the new “carbon taxes” could be combined with tax cuts in other areas. If implemented correctly it would allow people who want to save money to reduce their overall tax payments by reducing fuel use. Also as increasing prices will decrease demand (thus decreasing the price at import time) it would to some degree mean transferring some revenue from the governments of the middle east to the US government. The article also states that the Ford F series of “pickup trucks” was the most popular line of vehicles in the US for more than 20 years! But last month they were beaten by the Toyota Corolla and Camry and the Honda Civic and Accord. Now Ford needs to put more effort into their medium to large cars. With the hybrid Camry apparently already on sale in the US (their web site refuses to provide any information to me because I don’t have Flash installed so I can’t check) and rumored to be released soon in other countries Ford needs to put some significant amounts of effort into developing fuel efficient vehicles. According to a story in the Herald Sun (published on the 23rd of April), survey results show that 1/3 of Victorians would cease using their car to get to work if the petrol price reached $1.75/L [2]. Now the Herald Sun has run a prediction (by the assistant treasurer and the NRMA) that $1.75/L will be reached next week (an increase of just over 10 cents a liter) [3]. The good news is that there will be less pollution in Australia in the near future (even if $1.75 is not reached I am certain that the price will increase enough to encourage some people to use public transport). The bad news is that our public transport is inadequate at the moment and there will be significant levels of overcrowding.

Robert McQueen: Xen virtual interfaces with more than one IP

I’ve got a load of boxes running Debian etch with Xen 3.0.3 with routed networking (rather than bridged, so I can do iptables and reverse path filtering etc in dom0). Since upgrading from Xen 2.x many moons ago, I’ve not known how to configure one virtual interface to have more than one IP. In the meantime, I’ve ended up doing nonsense like providing a VM with two interfaces just to give it two IPs. However, this interacts really badly with reverse path filtering unless you do a bunch of source-routing rocket science in the domU to send out through the right vif. So, I looked at the vif-route script and it seems to support iterating through a space-separated list of IPs, but I was totally unable to find any documentation or mailing list posts explaining how to format the IPs within the formerly-Python key/value Xen domain config file syntax. After a while playing with the parser and various levels of quoting, I found that actually, the correct amount of quoting is none at all, and also uncovered a bug in another script which prevents it from working correctly. In the hope that this might help others using Google and trying to achieve the same as me, here is my recipe for configuring Xen vif devices to have multiple IPs (note that I think this might be specific to Xen 3.0.x, as I believe 3.2.x introduces config files in the S-expression format which is what xenstore uses internally):
  1. Configure your VM using this surprisingly obvious, but somewhat dubious syntax (including a second argument just to prove that yes, it really does work like that):

    vif=['ip=1.2.3.4 5.6.7.8, mac=00:16:3e:01:23:45']

    When parsed into SXP by xm create, this sets the ip value correctly as a space separated list as the scripts expect:

    (device (vif (ip '1.2.3.4 5.6.7.8') (mac 00:16:3e:01:23:45)))
  2. Fix the bug in /etc/xen/scripts/vif-common.sh:

    --- /etc/xen/scripts/vif-common.sh~ 2008-06-09 01:14:23.065065119 +0100
    +++ /etc/xen/scripts/vif-common.sh 2008-06-09 01:11:06.599986274 +0100
    @@ -103,7 +103,7 @@
    if [ "$ip" != "" ]
    then
    local addr
    - for addr in “$ip”
    + for addr in $ip
    do
    frob_iptable -s “$addr”
    done
  3. Set up multi-homed or aliased interfaces as normal in the domU (depending if you’re a ip or an ifconfig kinda guy).
  4. Profit!

Next.

Previous.