Search Results: "xam"

26 June 2006

Alex de Landgraaf: Debian tag-suggestor online

Overnight I've ran 10+ million tag-evaluations for all the Debian packages, and stored them all in a MySQL database. Finally I can simply execute queries on the data from the AI tagger instead of doing one-by-one HTTP requests, it speeds up things enourmously (processing the data took about 12 hours on my dual-MP server and 1 GB of DB-storagespace). Erich warned me against making a rough prototype of the interface public, as the quality of the suggestions isn't very high yet, but here goes: the Debtags tag-suggestor. Don't expect it to work very well, and it might be offline as I hack around with it (I have some ideas that should hopefully weed out the bad suggestions), but please let me know if it crashes your browser or burns your cat. Btw, I used AjaxAC for the package selection bit, as they had a Google-Suggest example that was easily adapted for the package list. I'll play around with the interface some more this week, after that I'm hoping to put some effort in actually improving the AI results...

25 June 2006

Biella Coleman: Before another month passes, a little on Mexico

Last month I went to Mexico to attend Debconf6 and then I traveled with 4 geeks to Oaxaca. Here are a few photos from the trip, which was quite lovely, though I stalled writing anything about it here because I was thrown into a strom of sickness during my last week there and into my first week here. I have been to Mexico a few times before though usually in passing or in Baja, which is somewhat nice but desolate. This was the first time I had any sustained exposure to Mexico and it was quite nice. Some of my favorite things about the country and my visit are perhaps a little odd but they are what took me in and here are some of them… For example, during Debconf proper, I feel in love with the following reptile and very surprisingly, because, when it comes to animals, I usually like the soft and cuddly and not the scaly and spiny. But…. this lizard was…. special. Here is how I found him: We were eating at a restaurant after a visit to some ruins and there we found this little guy caged at the back of the restaurant. I was more than a little miffed that he was trapped (and by butting his head against the cage, he clearly was saying I WANT OUT) and so was about to pull a “PETA move” and just let him out. But I decided that was not such a good idea so instead I went over to the owners to ask why the little one was caged. In answer to my query, they promptly pulled him out and told me he first that he was a chameleon (which does not seem right to me) and was usually free to roam but when there are a lot of folks (as there were) they lock him up. He plopped the little one on my arm and alas, what I pleasantly found out was that a lizard can act an awful lot like a dog. He LOVED to be pet and basically had a look of all-out-pleasure when you stroked his back. And at times, with a particularily good stroke, he would even subtly smile and flutter his hind leg a little just like a doggie. Aside from a special dog-like reptile, there were many other things that I loved about Mexico. The food at the market was divine, divine, especially the corn smut a.k.a huitlacoche and all the salsas were better than you could imagine. It is tragic that every city does not have a local market with such divine food. The architecture of Oaxaca was especially stuning as was the whole city center. It reminded me of viejo San Juan in Puerto Rico but the buildings were a little lower (apparently because of earthquakes) and the environment was dryer and more expansive. Our hostel was courtyard style (as were many houses there) and I think the courtyard should be revived as the defacto style for housing as this is probably one of the most enticing and smart architectural styles ever (at least in warm places). While a home is suppsed to provide shelter to enclose, the courtyard brings some of the outside inside and some of the inside outside. While in Oaxaca we met some folks from espora, walked a lot in the city, met up with other Debian folks traveling about, and cleaned out Vagrant’s ear which was truly … well I won’t go into that. We also drove for a few hours up to the mountains for a few nice hikes. The town hoped we happy trip and I think we did. Mexico city, by a number of measures, is one of the largest in the world and I unfortunately only got to see the Zocalo area as well as the subway. The center was quite impressive and especially nice before a thunderous storm One night at the Zocalo we happened upon a free concert, the lineup including the Tijuana Nortec Collective. One of the most dynamite parts of Mexico City is its impressive and I mean impressive subway system. In a nutshell, the system is large, clean, efficient, cheap, and quiet (thanks to thick and black rubber tires). The trains come quickly, ferrying the millions of riders who pay 20 cents for a ride on a lovely bright orange train. Every time I rode it, without fail, a vendor entered the car, loaded with a backpack that doubled as a radio/stereo, who was selling pirated music. I appreciated the sample and bought one disc chock full of mp3s. Like most urban trains, the riders are silent and I have always wondered why this is so. When I go to PR, I ride the busses much more and there, as in the states on the busses, there seems to be more open flow of chatter. Perhaps it is because trains are quite comfortable and they lull already tired riders into a state of quite contemplation. Who knows. So these are some of the things that I liked about Mexico but perhaps the most exciting part about the country was the clear political heatwave passing through, just as it is with much of Latin America. In the zocalo of Mexico City there were various stands protesting the attacks in Atenco, as well as general protests against neoliberal policies. The city of Oaxca was also filled to the gills with protesting teachers, demanding a pay raise. Thousands of them were camped out all over the city center, which is apparently a year rite. Sadly, in the last week the police broke up the protest, violently…

24 June 2006

Arnaud Fontaine: SoC: design of wotomae

These days, i have worked a lot for the SoC in order to define the design of the web and mail interfaces, helped by Raphael Hertzog. Everything has been committed to the arch repository of the project. Now, i will post news about the progress of the SoC on my blog and on the soc-coordination mailing list. Web interface I have begun by the tree of the web interface. One of the feature of wotomae is to be editable by everybody. However, we must have an administrator's group for a tracker (for mass bug filling or the blacklist). I have worked with Raphael for writing mockups intended to give an outline of the web interface, and especially to detail the features of the most important pages. It is possible to define custom fields (upstream version...) where the datas are given using the mail interface by external scripts or by the user if it can be done easily. It is also possible to define visual preferences on custom fields. The implementation of the web interface will be written with Turbogears, which has interesting features, like : Finally, I chose ZODB. Because the accounts database has to be share with other interface, which won't necessary use python, a secure XML-RPC API will be written for accessing the accounts' datas. Mail interface The goal is to obtain a flexible interface, allowing to make some tasks easier. At the moment, these commandes have been defined (some examples are availabe on the wiki): Any comments about the design are obviously welcome.

23 June 2006

Uwe Hermann: Trac - web-based project management with wiki + bug-tracker + svn code browser

Trac screenshot I've started looking at Trac recently, a nice web-based project management tool written in Python. It integrates with existing Subversion repositories; for example, you can browse the code in your repositories with Trac (it'll be displayed syntax-highlighted), view diffs between revisions etc. etc. Additionally, you get a wiki (e.g. for project documentation), as well as a built-in bug-tracker a la Bugzilla, all integrated nicely into a single piece of software... It's Free Software, of course (the license changed from GPL to revised BSD somewhat recently)... A few words on the installation: So far I've set up ca. 7-8 Trac instances for various projects and I'm quite happy with it. While I was at it, I also created a tiny Trac article in the German Wikipedia. You can get tons of useful plugins and macros over at trac-hacks.org for additional functionality, e.g. DoxygenPlugin, GanttPlugin, DebianBtsMacro, and many more.

Erich Schubert: Life, Exams, Worldcup

Life: I'm having my final oral exams the next weeks. Starting on Tuesday with the exam on Databases, Index Structures (R-Trees, X-Trees, ...), Knowledge Discovery in Databases and Data Mining. 30 Minutes. Should be okay, though I have been doing way too little reading. This also implies that I'm missing most of the Worldcup fun. I watched the first game, and it's hard to not read about results. But I won't be going to soccer partys every day. I don't care much about watching sports, and I should spend my time studying for the exams.

Joey Hess: using a wiki for issue tracking

Does it make sense to use a wiki for issue tracking instead of using a standalone BTS? Martin Krafft suggested this might be a useful addition to ikiwiki. It seems to me that this would mostly be worthwhile if it took advantage of the free form, open nature of the wiki in useful ways. Reconciling that with some of the more structured needs of a BTS is an interesting challenge. Surveying a few examples of using a wiki as a BTS: There is a definite feeling about all of these of finding a vaguely nail-shaped bit and pounding on it with the wiki-hammer, but I'm unsure whether it's really a nail or just an obvious pointy bit sticking up out of the main problem of issue tracking. On the other hand, the same could probably be said about a BTS built using a relational database.

20 June 2006

Jurij Smakov

It’s really a pity that in the rush of the modern fast-paced world we hardly have time to slow down and notice little details which make the life so much more enjoyable. I, for example, totally missed the end of Prairial. It’s good to know though that the same way summer follows the spring, Prairial is followed by Messidor, which, I’m sure, is going to bring us even more wonderful moments.

Gintautas Miliauskas: Localization coordination for Debian #2

I sent a new revision of the suggested translation storage API to the mailing list, addressing all the shortcomings that have been pointed out. Hopefully it will not change much any more and I can start working on an implementation this week. My plan is to first produce a very simple pickle-based implementation of the API. This should be relatively quick to build and would highlight the weak points of the API. I think that this can be finished this week. After that (and possibly revisions to the API) comes the important part: writing a nice wrapper for the existing pofile class. This should not take too long either, another week at most (especially since my exams would already be over). When a .po-based implementation is in place, the fun starts. I'd then like to try to have another application that concurrently uses Pootle's backend storage (currently po-based). Another week of work.

19 June 2006

Lars Wirzenius: Debian: Packaging tutorial (again)

I gave my Debian packaging tutorial today. The Computer Science department of the University of Helsinki provided the space (a classroom with networking), for which I hereby offer grateful thanks. There were fourteen students, and everyone made a package out of my hello world program (especially written for this tutorial). The slides used my liwc package as an example, and during the talk I noticed a couple of problems, which promptly resulted in a bug report. Excellent! Nobody wanted to do a victory dance, people are too shy. I've now given this tutorial twice: once for three of my friends privately, and once for a larger group. It only covers the very basics of creating packages, and there's much more to learn. Some day I might do a second part, and cover things like maintainer scripts, advanced dependencies, debhelper, pbuilder, and piuparts (the last three were only briefly touched upon today). I might be willing to do the first part again, if there's enough interest. Not very soon, though, teaching is surprisingly exhausting and time-consuming. However, if you'd be interested, please do mail me (at liw@iki.fi).

18 June 2006

Alexander Schmehl: Damn, why did you splitted the package?

From time to time it's funny to run a scriptlett and play a bit with numbers. For example:
find /pub/debian/pool/main/ -name \*_i386.deb -or -name \*_all.deb -exec ls -s \; sort -nr
157696 /pub/debian/pool/main/f/fgfs-base/fgfs-base_0.9.10-1_all.deb
152284 /pub/debian/pool/main/v/vegastrike-data/vegastrike-data_0.4.3-2_all.deb
141144 /pub/debian/pool/main/o/openclipart/openclipart-png_0.18+dfsg-4_all.deb
89808 /pub/debian/pool/main/f/fgfs-base/fgfs-base_0.9.6-1_all.deb
86304 /pub/debian/pool/main/k/koffice/koffice-doc_1.5.1-1_all.deb
81892 /pub/debian/pool/main/l/llvm/llvm-doc_1.7-1_all.deb
78860 /pub/debian/pool/main/t/texlive-extra/texlive-latex-extra_2005-2_all.deb
67844 /pub/debian/pool/main/b/beneath-a-steel-sky/beneath-a-steel-sky_0.0372-2_all.deb
67764 /pub/debian/pool/main/b/beneath-a-steel-sky/beneath-a-steel-sky_0.0368-3_all.deb
62252 /pub/debian/pool/main/f/fillets-ng-data/fillets-ng-data_0.7.1-1_all.deb
61660 /pub/debian/pool/main/f/fillets-ng-data/fillets-ng-data_0.6.1-1_all.deb
58984 /pub/debian/pool/main/v/vegastrike-music/vegastrike-music_0.4.3-1_all.deb
56260 /pub/debian/pool/main/t/tetex-src/tetex-src_3.0-3_all.deb
Interesting, I always thought one of my packages would be on of the biggest, bit according to my find, planetpenguin-racer-extras is just on place 117! But now I sponsored an upload for an other member of the pkg-games group: nexuiz_2.0-1_i386.changes uploaded successfully. Sadly Bruno decided to splitt of the music of the -data package, so we won't take the crown, but will still get the fourth place, as soon as Ganneff let it the packages through new :) PS: Damn, they still didn't fixed the bug, that I allways get killed.

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! :)

Philipp Kern: Some more progress with reportbug

It is a daily fight with the oddities of PyGTK. It seems that there are severe issues in conjunction with the way I use the threading in Python. The patch is almost complete in terms of functionality. (Not everything is committed yet, because I will review all core changes again, to keep them both compact and sensible.) But there are issues with the GUI, like it not reacting after a program switch in conjunction with the GTK accessibility module. Scrolling the log window to the bottom does not work neither, even if I call the corresponding function scroll_to_mark in an idle handler (and thus in the main thread). Still those are minor, mainly cosmetic issues. It's just that the deadline is approaching. (Considering that I face the final examinations for my High School degree in a bit more than a week, I need to hurry up. I get my topics on Monday, so there is one week of preparation time for both a presentation and all content of one class.)

David Pashley: Invalid Characters in Encoding with JAVA

Imagine you've got some text you've been told is ASCII and you've told java that it's ASCII using:
Reader reader = new InputStreamReader(inputstream, "ASCII");
Imagine your surprise when it happily reads in non-ascii values, say UTF-8 or ISO8859-1, and converts them to a random character.
import java.io.*;
public class Example1  
   public static void main(String[] args)  
      try 
         FileInputStream is = new FileInputStream(args[0]);
         BufferedReader reader 
            = new BufferedReader(new InputStreamReader(is, args[1]));
         String line;
         while ((line = reader.readLine()) != null)  
            System.out.println(line);
          
        catch (Exception e)  
         System.out.println(e);
       
    
 
beebo david% java Example1 utf8file.txt ascii
I t rn ti n liz ti n
beebo david% java Example1 utf8file.txt utf8
I t rn ti n liz ti n
So, I hear you ask, how do you get Java to be strict about the conversion. Well, answer is to lookup a Charset object, ask it for a CharsetDecoder object and then set the onMalformedInput option to CodingErrorAction.REPORT. The resulting code is:
import java.io.*;
import java.nio.charset.*;
public class Example2  
   public static void main(String[] args)  
      try 
         FileInputStream is = new FileInputStream(args[0]);
         Charset charset = Charset.forName(args[1]);
         CharsetDecoder csd = charset.newDecoder();
         csd.onMalformedInput(CodingErrorAction.REPORT);
         BufferedReader reader 
            = new BufferedReader(new InputStreamReader(is, csd));
         String line;
         while ((line = reader.readLine()) != null)  
            System.out.println(line);
          
        catch (Exception e)  
         System.out.println(e);
       
    
 
This time when we run it,we get:
beebo david% java Example2 utf8file.txt ascii
java.nio.charset.MalformedInputException: Input length = 1
beebo david% java Example2 utf8file.txt utf8
I t rn ti n liz ti n
On a slightly related note, if anyone knows how to get Java to decode UTF32, VISCII, TCVN-5712, KOI8-U or KOI8-T, I would love to know.

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.

15 June 2006

Erich Schubert: Buzzwords of the DotCom 2.0 area

I've been preparing slides for a small presentation on "Buzzwords of the Dotcom 2.0 area". It's still a work in progress, so far I've only written some lines on Ajax and P2P, more to come on Web 2.0 and social networking. The presentation is not intended for a tech audience, and I've been trying hard to avoid too much previous knowledge and such. But I can't really explain the difference between authentication and authorization there... I'd really appreciate feedback (except: "add a diagram", thats too obvious), especially on other buzzwords I should cover. I also plan to add some judgements on the benefits of the usefulness of these "technologies" for businesses. For example the release of an API can make you very well known, but you might have a harder time earning money, actually...

Jonathan McDowell: Do GUI users never read stderr/stdout?

As previously mentioned I run evilwm as my window manager. The only way to spawn a new process in it is to hit Ctrl-Alt-Enter, which opens an xterm. So I have a single xterm that I use to launch whatever apps I need (I choose this. I'm aware of many options if I felt the need to point 'n drool to open apps.). I don't think application authors can do this much, judging by the amount of crap that gets output in this xterm. For example, today I installed evince (I normally use xpdf) to have a look. I launch it by typing evince, up pops the window, I go to the File menu and choose Close. What do I get output in my terminal? The following: (evince:4105): Gtk-CRITICAL **: gtk_tree_model_foreach: assertion GTK_IS_TREE_MODEL (model)' failed (evince:4105): Gtk-CRITICAL **: gtk_list_store_clear: assertion GTK_IS_LIST_STORE (list_store)' failed WTF? A 'critical' error for simply starting and exiting the app? It's not the only offender. liferea spews Unhandled property: 12 border-collapse messages, gajim defaults to calling aplay rather than aplay -q so you get a message every time it plays a sound. Does no one else care about this crud? Is it unreasonable if I file wishlist bugs every time I hit an app that does this? Should I just learn to live with it?

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.

13 June 2006

Gintautas Miliauskas: Localization coordination for Debian #1

I have been working on an integrated l10n infrastructure for Debian. Instead of starting from scratch, the Wordforge project was chosen to be used as the base. Currently Wordforge has a toolkit for various l10n operations as well as a web frontend Pootle that uses this toolkit. My job is to adapt these tools to Debian needs. I see three major areas of my future work in Wordforge: A (to me almost distressingly) large amount of discussions took place on the debian-i18n and Wordforge mailing lists on these topics and more as I dug into Wordforge to better understand the current situtation and plans of other developers. After the initial communication peak, now things are really starting to roll. Here's what we have now: I posted the sketch of the API to the Pootle mailing list. There was little opposition and mostly constructive remarks. Unless a disagreement pops up, I would expect the API design to be finished by next week. My longer term plans: One thing that is still keeping me down a is a couple of exams due in a week. After that I should have much more time to work on this project.

12 June 2006

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.

Antti-Juhani Kaijanaho: Health care, insurances and making economic sense

Originally posted as a comment in Finland for Thought. A system of health care paid by insurance (of whatever form) and provided by private hospitals looks attractive on the surface but isn t really a good system. Look at the economic dynamic of the system. The insurance (if comprehensive) will essentially pay for any operation that the physician at the scene deems necessary. Is it in the physician s interest to use that tab as efficiently as possible? No, in fact, it is the opposite: it is in their best interest to find as many reasons to bill as much as they can. This is a road to disaster. Of course, you can balance this system by introducing insurance investigators who examine bills and determine if they are legit. To do the job properly, they need to be qualified physicians, and they need to have access to all the data that the physician at the scene had. Essentially, these investigators would be doing the job all over again, except never seeing the patient. Result: the money you save from preventing fraudulent billing is spent in maintaining a paraller physician workforce. Why not let the investigators be the healers, and cut the private hospital out of it altogether? These physicians would have budgetary responsibility on what they spend, and thus they only do what they need to do. Oops. Looks like we just transformed the market-based health care system into a state-operated, socialized system.

Next.

Previous.