 weren't sure where you were. This is the lightning talks for debconf 11. People submitted lightning talks via email and I offered to curate them. So they're five minutes each. At the end of five minutes I'm just cutting people off. I'm gonna give them a minute to set up. So that's basically it. Our first lightning talk is Vagrant Cascadian on DGKFBSDTSP. So DGKFBSDTSP, fairly pronounceable. You're probably wondering what it is. I'll get to that. And then I'll talk about some bugs that kind of came about as a consequence of exploring this idea. And then we'll talk about some of the bad consequences and we'll get into the future because it's not all hope is not lost and even more futuristic terrible ideas. So DGKFBSDTSP stands for Debian GNU K FreeBSD Terminal Server Project. I work on LTSP. It's a thing client implementation and for whatever reason I'm obsessed with porting it over to K FreeBSD. So Jim Quillin likes to point out what the L and LTSP stands for. So one of the important steps in doing a thing client system is getting network booting to work. So I looked around in the K FreeBSD codebase and looked at the kernel, found that there were some options to enable Boot P which is kind of like an older version of DHCP and I figured okay we we turn on some of these options and you know we've got NFS root and you know you do that on a Linux kernel and everything comes out right right. I mean you know you can boot to the network, you mount the root file system, you proceed from there. So the maintainers of the K FreeBSD image package seem to think that was a good idea as well. So they committed it to SVN included in the next upload and I figured I'd give it a try. So well some of these assumptions were wrong. So basically when you enabled those features it forces booting from the network and so we got a kernel uploaded into unstable and no matter what kind of medium you were trying to boot from no matter what boot arguments you passed to it it just tried to boot over the network and try and mount a NFS root file system. So indefinitely hangs looking for a DHCP reply no matter what you wanted to boot from. So that got reverted pretty quickly. All hope is not lost. Fairly recently Robert Milan commented on the bug and explained the process that sounds fairly painful by which you instead of compiling all of the network modules into the kernel you enable them as modules and you load them from grub. So you just load all of your network modules from the grub boot loader because K FreeBSD doesn't have any dynamic way of loading modules. So that sounds kind of painful. I've also looked at Debian installer has something that's kind of like an init ramfs for K FreeBSD. So maybe we could do that much like you do for a typical Linux system. You boot into the network you load your NITRD and then you load the modules you need and do everything in user space. Wouldn't that be elegant? So hopefully in not too much short order I'll be obsessing over this and trying to figure out ways to actually make it work. Future bad ideas. DGHTSP. It's a little bit shorter to pronounce but pretty weird. Again I'll be hassled by upstream repeatedly about what crazy things I've been doing. That's about it really. So yeah. Have a good one. Thank you Vagrant. That was under five minutes. So up next is DJ. Thank you. And this is... Let me just get the monitors hooked up. Sorry about that. Nope. No I cannot make it louder. That's the loudest that it gets. I'm sorry. I'm sorry. Okay? Okay. So space bar. Great. So I'm here for five minutes to talk to you about the Debian Swiss Knife. It's an idea that we had on the Debian.ch mailing list. We have already sorted out all details and now I'm very happy and proud to present the outcome of this project. So some facts we all use Debian and it usually runs on computers but hardware sometimes needs to be fixed. And the Swiss Knives they are small. They are useful as the model we will... I am about to show you is able to fix computers well somehow. And they fit in a pocket. So we have two models that we want to propose for selling. The first one is the Cybertool 29. It has 28 tools and you can load some Allen keys to unbreak or brick your computer. The cost is supposed to be something around 41 Swiss francs that is 70 kilometers and you will need to pay the shipping plus to that. One thing to note is that there is a minimum amount of 25 for us to be able to have the Debian branding on it. The other model is slightly bigger but this one is usually only to break your computer or cut down cheese or sausages. To open wire bottles. Thank you very much. It has a little less tools but it's bigger so 11 tools it weighs 100 grams. The price is 34 francs and which is about 59 kilometers and it has a minimum amount of 30 pieces to be ordered. So those are the two models. One thing to note is that the colors are only blue and or black. The red one is only the one you buy without the Debian branding. So you can also reverse the color. You can have the big one in black or blue or the small one in black or blue. I hope that's clear. About the prices so as I told you can buy them in black or blue. The models they are only these two that we are about to order and no else. You can also buy other Debian knives, Swiss knives but without the Debian branding if you want by yourself. Or if we organize the bid in the DEVCON 13 in Switzerland you will be able to buy multiple Swiss knives. The one thing to note is that the gift box is included and the more people buy knives it's less expensive for everyone. And so the prices that I showed are the maximum prices we expect to have but if more people buy we will lower the prices. And any profit goes to Debian through the Debian CH Association which is good. And if you want one just go on the wiki and register yourself on merchandise slash Swiss knives or mail info at Debian.ch and the delay in order to be able to buy those relatively soon is the end of focus. So please run. And that's all. Thank you very much. All right. Thank you. Next up is Lunar. We're going to give a minute to connect the video stream. So here we go. One two. So this talk is called Return to the Dead Island. Well the subject of this talk is should live Econest truly be in Maine? So it all started with Clementine. Clementine is a modern music player. It's basically a remix of what the old Amarok was like 1.4 before it started to get bloated and having many, many options. And one of my co-workers was wondering why Clementine wasn't in Debian and wanted to package it. So we started that process of doing so. Hey, Thomas. And so we had to, it had an embedded code copy. So we had to, he had to prepare a package for live Econest. And that got, I mean we got it packaged and in Debian, but still live Econest is a strange piece because the description of live Econest is a QT library for communication with the Econest platform. What the fuck is that? So the Econest is actually a web service that is advertised as making music smarter. And the bottom line of the website says the Econest knows more about music content and consumers than anyone. I mean what? This is a little bit scary. And actually, so live Econest got accepted into main, but actually the code is, yeah, it's free software. It is, it is GNU, GPL, fashion tool later. But what actually the code is about, it's about making HTTP requests to a specific website that is actually encoded in the source code. So using HTTP to the host that is fixed, developer.Econest.com. And it's only about making those REST requests to gather some data from this Econest platform. This is what people call the cloud these days. It's pretty dark cloud in my opinion. But, and that got me at some point, so we got into main, but I was a little bit, I don't know, not feeling really good about it because at some point I got, I got back to the policy, you know. And the policy says about the country, the country archive area that it contains supplemental packages internet to work with DBN distribution but which requires software outside of the distribution to resolve build or function. I mean the Econest platform is a software which actually is outside of DBN and if you don't, like, there is no way the LibEconest library is useful if you don't have that software available through HTTP requests. And one of the way I was thinking, okay, shouldn't LibEconest be in main? Should it be in main? Shouldn't be in country then? And so I was wondering, okay, what do you put in country? What should we put in main? What's the difference? And I got back to thinking about this desert island idea that we used, or some people have used to determine if the license was free or not according to the DFG. And I was wondering, okay, maybe we should ask ourselves the question like that. Can this software, if it's need to connect to a network service, can this service be run by some friends that would, like, be together in a closed network on an island with only a DBN mirror? In that case, Java would be, for example, in main, like any Java client, but LibEconest would be in country. And probably the MSN plug-in for telepathy would be in country too because we don't have a hand on the MSN servers. So, yeah, and if you take, like, the DEBCOMF 18 idea and if you were on a boat and we have no network, we have no Internet uplink, then what happens? So, yeah, you should actually ask yourself about that. Probably you might find something that could not actually function on a boat on a desert island. So my point, if we don't start to think a little bit more about that, then we are totally lost. Wow, that's it. Thank you, Lunar. Next up we have Keo, who is presenting how to turn a website into free software. Again, we'll give a minute for getting the monitor set up, which is always fun and games. You want 85 hertz if you can. There's a web page on the wiki that has a set of XR and R incantations that makes these monitors work correctly. It's effectively a shell script on the wiki. So you're running into the same problem that I run too and you really do need the full thing. Do you want to step off? We'll trade off to somebody else and I'll get you the right commands. Okay, next up, who, all right, Igor, are you ready? You just want SM? Yeah. All right. You have your microphone there. Hello. I'm actually going to present in my natural position, so that is sitting. I'm Igor Garlitsch from the Apache Software Foundation and I would like to shake the drum a little bit for my pet project, which is the Apache Traffic Server. Well, what is it? It's a proxy server, which can be used for forward and reverse proxying and it's better than squid. So if you don't like squid, please use traffic server. That's the short story. Long story is it's a very, very old piece of software and gone through very much incarnations. It belonged to a company called Intomi. It was bought by Yahoo and then it was sort of not quite dropped over the wall to Apache. It was actually a very long and painful process to get it open sourced because it had lots of patent issues, but now it's here and we're trying to make it better. It's written in C++ but that's okay. We're using it very responsibly and it has a clean C API which you can use to write plugins for it. So if you need a proxy server which is amazingly, amazingly fast to build your CDN or whatever, then by all means, use traffic server extended, visit the website, subscribe to our mailing lists, come and bug us in the channel. We're nice, friendly and receptive, helpful, but actually you don't need our help because our documentation is great and it's so intuitive to use. So please, please use it. Okay. Sorry. Yes, it actually is. We have a guy sitting in the channel and packaging it for us in Ubuntu already and he's very active and doing bug fixes sometimes and bug reports most of the time. So yes, it is packaged. Laish I think has sponsored him but he's not uploading it anymore because the guy became maintainer I think the other day. I think so, yeah. You're not up to date. Okay. So any other questions like what do I need a proxy server for? If not, then I'm actually done. So please just visit the website and use it. Because it speaks HTTP as opposed to Varnish. Okay. Thanks. Thank you, Igor. That's off and then back here. Okay. My talk is how to turn a website into free software with darkspy and virtualization. A bit of background. I run a site called Piperka.net. It has been in operation since 2005. And it's got a lot of custom code and all sorts of badly designed stuff but I'm trying to improve that. I'm not really talking about that here now. And I would like to get others involved with the website but it's a bit difficult. I used to do everything by just editing files in place, purl files and sorts and it's not really scalable and I don't want to give other accounts to do that on my server and if I packaged it and distributed a source then it would be difficult also. I can't expose users' data and I have used it as a private file store and all kinds of such things and I don't want to expose those items and it's difficult for anyone to set up a test system from that even for me and if somebody did something with it it would be hard for me to accept any patches and if I made any updates myself it would be hard to get others to get those so I needed to fix my workflow I set up a development server on my own computer virtualized and I'm using my fully automatic installation to set up users permissions and database and all the directories and sorts and once that's in place it's as easy to run file soft update to set up a test system and the second part of this was to use the darks distributed version control system to manage the changes I set up a trigger that copies all the files and restarts any services and with that I can just make a patch and send it to the test server and if it didn't work the first time I can modify it and do it again and do what I have it's just a dark pass to the production server so with that I can let others install the test system for themselves the first step is to set up a virtualized machine for themselves it's a bit involved but if you have done it once it's not that difficult anymore but they basically need a basic Debian system installed first and the second part is to get the source code which darks get copy the SSH key to the test server run a setup script it copies all the files to the test server and runs file on it and they can use the web server to connect to the web side so that's all it takes and I can accept patch easily with that and they would use the same workflow as I test things on the test server and send their patches to me and it's easy to do so it's easy to do so this is a presentation by Petter about fix my street fix my street there you are so I'm going to talk about what I've been able to release in Norway the last half year or so it's basically a British site and it's supported to Norway and it's a site giving the citizens the ability to help the government improve the public infrastructure fix my street this is the British site is a very simple site where anyone can go in and put in a postcode or name of the allocation to the local consoles how does it work? very simple you end up with reports like this I'm just showing one of the British reports you can see on the map where it is you will have some information about what it is and when it was reported to the console I don't really know any British names so I'll go to the Norwegian site instead put in a postcode you are presented with the map let's hope the wireless keeps working so the reason I'm showing it here is it's based on Debian it's been ported to Norwegian environment from the British environment and the major part of the porting effort was actually to rewrite the application to stop using British geo coordinates this means that it is no trivial to port to any country in the world I would expect it would take less than two days to get it up and running for any country if you have the geo data that is required to actually get this working here we have it it is showing the problem reported around the area where I put the postcode in it's showing if they are solved the green is solved, the red is not and hopefully the open street map will show up soon so it also makes it possible to see if you actually need to report the problem so the console doesn't have to get multiple reports from the same problem and you can save time of course so to get this working this is basically two services you need the map it service which is a web API to map coordinates and then you have the console and post codes to coordinates we have used open street map as our data source for the geo data basically the boundaries of the municipalities in Norway are not public information that sounds kind of strange but we need the geo coordinate not the drawings not a picture of a map we need a map of the boundaries and we have not been able to get it so far so we are using open street map estimates instead the map it service is feeded with data from open street map and you can look up a given coordinate this is 59 59.10 or comma 10 and you will get a very nice map and information about any console information covering that point and here you can see the national road authority the national shoreline administration city council of larvik road authorities of region south and the west pole local area and if you move forward to municipality will actually be able to see the area covered by that municipality similarly you can do the same for post codes one nice feature with open street map now with the fix my street is that it's able to export geo rss which can be visualized on google maps or any other mapping service and recently I've been adding an open 311 API to allow anyone to search more interestingly from the database you can get all the open problems in tronheim for example as xml or as a geo rss and show it on the map we can get given categories like the all the problems with water supply in norway you can get all the problems with holes in the road that kind of thing you can also get all closed reports and the target I had in mind for this API search API is journalists looking for problems in the local area but also councils can do it if they want to extract all the reports in a different specific category it's based on debian squeeze missing 12-pole modules I think in squeeze to get it running was pretty trivial to get up and running you need a post-gis database and a purchase server and catalyst for the latest version and it would be very nice to see it spreading all over the world that's five minutes, thank you we have you want this one? you can take I think it's fine now he can't stop me, that's very good it seems I can't really make an impression by using screen methods for presentations anymore I see it was four years now since I created screen methods for the last fourth last step conf this is not the topic of my talk I'm going to show you two things that I've been working on the last here and weeks before pixel-free screenshots first one is the HTML copy target for GNOME terminal and I'll just demonstrate what it means here I have a GNOME terminal actually it's not a GNOME terminal but it's a test binary for the VTE library which GNOME terminal uses in a command which has some colorful output I want to paste this onto my blog and losing all the colorful output is a bit sad so once this is in GNOME terminal I can copy this I can go to whatever program supports pasting HTML I can paste it and I get all the colors this also works for example with OpenOffice okay then that's the first thing next thing is the GTKVectorScreenshot program and I'll just show what it does here is a GTK program it has to be GTK3 for it to work I run takeVectorScreenshot I get this nice button, I click on the button I click on the application I can save this just one and I get a PDF file that I can open okay it looks interesting like a picture but if you pay attention we can zoom in and this is purely vector graphics and I can copy this is what I just copied out of the Unicode program and it also works with more complex applications, I was hoping that I could see myself here it seems that didn't work but still I can take a screenshot I can save the PDF file I can open it and there's the whole screen I can select not only the buttons up here but also the HTML text and it's again fully vectorized and yeah that's it the first one is still only available as a bug report with a patch, the other one is in Debian that was the last lightning talk and thanks for that! that was our lightning talks for the conference thank you everybody for coming we have one more, we have the final closing ceremony starting in about 25 minutes in this room thank you