Search Results: "jan"

4 January 2006

Michael Janssen: Asking = good

I have noticed a new trend in my shopping habits lately: I will ask for help from a "sales associate" much faster than I did previously. This could be a product of the instant-gratification culture, but I really don't have much patience with floundering around a store trying to find what I need, especially if I have done all of my research earlier and show up at a store with just one thing in mind. I will go to great lengths to find a live person because even if I spend 3-5 minutes trying to find help, they will most likely be able to help me right away. That said, I won't just grab the first employee that I see in the store, I will actually make a reaosnable effort at finding the item first. After getting help, I can look at my handy palm pilot and see if there's anything else in the store that I need. I have noticed that Target is especially good at having random people walking around the store doing things that are quickly dropped in order to help a customer. In addition they have these nice little buttons sprinkled around the store that you can press and the entire floor staff gets paged notifying them that you have a question. I prefer this to the "pick up the phone" approach, although that is also available in some stores. The worst store by far for this strategy that I have come across is Home Depot. You sometimes have to walk a very long distance before you find anyone, and then when you do, they just point you back in the direction that you came from and said that someone over there can help you. If there was someone over there, I wouldn't be asking over here. I wonder if they just think I'm too stupid to read the HUGE SIGNS which state what is where in a Depot.

Josselin Mouette: OMFFSM

This is the best blonde joke ever.

Antti-Juhani Kaijanaho: Blonde joke

Despite all the political correctness of this day and age, blond jokes still crack me up. Here’s a good one. Remarkably, this one seems to translate to Finnish just fine. It’s not a new joke, so many of you have probably already heard it, but, still … :) Reminds me, actually, of the magnificient Zangelding.

3 January 2006

Matthew Garrett: 3 Jan 2006

Joey: While the public statements may seem oddly contradictory, you may be able to draw conclusions from the fact that I was recently contacted to help get the Ubuntu laptop support stuff into DCC...

Joey Hess: strange pairs of statements

According to Mark Shuttleworth:
The DCC distro doesn't use the Debian kernel, and it modifies key pieces of the infrastructure like the linking system and core system libraries. So it's not really Debian at heart.
According to the DCC 3.0 release notes:
5 [packages] are the LSB 3.0 compatibility environment, which adds LSB 3.0 compliance in such a way that the sarge glibc and pam packages don't need to be modified
It took me a long time to figure out how to read these two statements in a way that wasn't thuroughly contradictory. The DCC dropps in ld-lsb.so linker in for LSB binaries and uses that to make them link to some modified libraries somewhere outside the normal link paths, but that's more like the distro having two hearts (one of which is used only to circulate blood through the very limited set of available LSB binaries) than not being Debian at heart.
Mark again:
There is now discussion of modifying many, many more packages, for example to use the Ubuntu X.org packages rather than the Sarge XFree86 packages.
DCC again:
25 [packages] are a backport of X.org from etch.
So if they're using Debian's X.org already, why would they be planning to go to Ubuntu's?
Mark:
The DCC distro doesn't use the Debian kernel, and it modifies key pieces of the infrastructure like the linking system and core system libraries. So it's not really Debian at heart.
Mark again:
The DCC kernel and Ubuntu kernel will be very similar if not identical in future DCC releases, and I expect that collaboration will spread to other parts of the system such as X, ACPI etc.
If you think about it, this is in a sense the strangest pairing of statements of all...

Colin Watson: Single-stage installer

Hot on the heels of Joey's tale of getting rid of base-config (the second stage of the installer) in Debian, we've now pretty much got rid of it in Ubuntu Dapper too. The upshot of this is that rather than asking a bunch of questions, installing the base system, and rebooting to install everything else, we now just install everything in one go and reboot into a completed system. This does mean that, if your system doesn't boot, you don't get to find out about it for a bit longer. However, it has lots of advantages in terms of speed (the much-maligned archive-copier mostly goes away), reducing code duplication (base-config had a bunch of infrastructure of its own which was done better in the core installer anyway), comprehensibility, and killing off some annoying bugs like #13561 (duplicate mirror questions in netboot installs), #15213 (second stage hangs if you skip archive-copier in the first stage), and #19571 (kernel messages scribble over base-config's UI). To go with Joey's Debian timeline, the Ubuntu history looks a bit like this: Although it caused some friction, I'm glad that we did the first cuts of many of these things outside Debian and got to try things out before landing version-2-quality code in Debian. The end result is much nicer than the intermediate ones ever were.

Erich Schubert: Linux: two leaps ahead

I just read my logcheck email, and one box scared me:
Jan  1 00:59:59 dumbledore kernel: Clock: inserting leap second 23:59:60 UTC
Jan  2 00:59:59 dumbledore kernel: Clock: inserting leap second 23:59:60 UTC
It had two leap seconds. None today though... All the others, running the same software, had only one leap second, on 1.1.

2 January 2006

Erich Schubert: Debian SELinux mailinglists created.

I've added two SELinux on Debian mailing lists on Alioth: SELinux-user and SELinux-Announce. The first one is an open SELinux on Debian user mailing lists, the second will be used for announcements (mostly when something important changes, new stuff is added, something breaks etc.). Every SELinux on Debian user should probably subscribe to the second. Since there aren't that many user, I guess the -user mailinglist will be rather low-volume for some time, and needs love by those who are already running SELinux on their boxes. Current SELinux packages contain some breakages... updates are stuck in NEW right now, and I've written some extra notes to the mailing list: notice about SELinux changes. BTW: On the long run, Debian will likely drop it's current "strict" policy, and migrate to a serefpolicy-based Policy like Fedora already uses. Any volunteers to debconficate the setup process?

Junichi Uekawa: oprofile patch for MPC7447A.

I'll just drop here what I've done so far; it's probably already obsolete since 2.6.15 is going to be released, and somebody else is already working on an implementation.This was a quick hack to make it work enough on my system.patch against kernel 2.6.14patch against oprofile 0.9.1

Zak B. Elep: [REVU] for 2005

Now here’s the thing I’m supposed to write ;) It took me quite some time since I was too busy sleeping ;) Looking back at 2005:
  • February :
  • March :
  • April :
  • May :
  • June :
  • July :
  • August :
  • September :
  • October :
  • November :
  • December :
  • Things to I want to do this 2006: Things to look out for: Rock on, 2006!

    Andrew Pollock: [life/americania] On bootstrapping oneself in the US

    So I've been in the US for just over six weeks now, and I thought I'd reflect on the trials and tribulations of bootstrapping oneself in a foreign country. The Social Security Number is the primary key from hell I already had a fair idea of the importance of obtaining a Social Security Number (SSN). So much so, that after dumping our luggage at our temporary accommodation, the Social Security Administration office was the first place Michael and I went to, so we could lodge applications. We subsequently learned from another Australian who was about two weeks ahead of us, that you're apparently supposed to wait ten working days before lodging the application, to allow your immigration records to percolate through the bureaucracy that is the US Government. Our applications were duly accepted without any mention of waiting a bit, but we were sent away with a letter and a tracking number, saying that the SSA had to verify our existence with Immigration (this is despite the fact that we're standing in front of them with a passport with an I-94 stapled in it) and that it would take up to four weeks. So it's been six weeks, and still no sign of an SSN. Enquiries with the office are met with the same response - waiting on information back from Immigration. Apparently it can take up to three months. It's a real shame you can't start the application process when your visa is granted or something, as in order to apply, you need to quote your "alien registration number" (I still chuckle at how the US Government refers to me as an "alien" in all their paperwork), which is the number on your I-94, which you only get when you enter the country. So, whilst the SSN application remains pending, I cannot be paid, I cannot have my health insurance paperwork lodged by my employer, and whilst I'll be covered for health insurance retrospectively, I'm not technically covered right now, if I were to require medical treatment. Going back to how the SSN is the primary key of All Things... Next step is to open a bank account. We chose Citibank, because I've been told it's slightly easier to import money back into Australia with them. Fortunately we were able to open an account sans SSN, but it's called an "NRA account" (NRA standing for Non-resident Alien). We were told that we were only eligible for an ATM card until I had an SSN, yet they mailed me out a debit card about a week after we opened the account, and happily ordered one for Sarah, and a cheque book when we asked after opening the account. About the only thing it seems we can't do at the moment is transfer money back to Australia. No big deal, it's all coming the other way until I can get paid... Driver's licence requires an SSN ideally, so that's out of the question for the time being... Electricity, telephone and cable were all able to be provisioned with an SSN, although I think for credit-rating purposes, again, it is the primary key. We had to pay a deposit for the electricity, which is fair enough. The lady I spoke to on the phone when I got it connected said that they just treated us aliens like teenagers straight out of home with no credit history. I don't have a problem with that. It's just a shame that you can't import your credit history. Getting a cell phone account appears to be nigh on impossible with an SSN though. It was a battle just to get a prepaid SIM card for Sarah's phone, and this makes a great story of how much hoop-jumping is required. We walked up to a Cingular stand in a shopping mall to see what we could and couldn't do. I explained our situation (lack of SSN, lack of credit history, etc etc) to the sales droid, and he assured us it wasn't a problem to get a prepaid SIM card. He proceeded to take about 30 minutes to organise the SIM card. I watched as he entered a dummy SSN into the computer, and used his own driver's licence number. He was clearly battling the computer system to be able to do it. When we got home, and Sarah called up to try and put some credit on the phone with our Australian Visa card, she was told they only accepted credit cards with a US billing address. (So much for Visa being accepted worldwide). So we headed off again to Safeway to purchase a prepaid Mastercard. Funnily enough, when Sarah called up to activate that, she was initially asked for an SSN, so we almost had a dependency loop that we couldn't break, just to get a US cell phone. Fortunately they could cope with no SSN, so she successfully ended up with a prepaid Mastercard, with a US billing address, so she could put credit on her prepaid SIM. From what I can work out, a lot of the places that do request the SSN seem to using the last four digits as an authenticator, much like everyone just uses name and date of birth back in Australia, so I'm guessing for these organisations, I could probably just quote any old number that fit the pattern and they'd be happy. Just so long as they don't go trying to run a credit check against it... Foreign credit cards As I said earlier, a credit card with a non-US billing address is fine for most face-to-face purchases, but an amazing array of mostly telephone transactions will not accept them. Most notable was trying to add credit to a calling card for making international telephone calls. Couldn't be done. So it meant I had to forego any discounts or bonuses for topping up, and buy a whole new calling card. Car insurance and registration I'm not sure how this is going to go yet. Our Prius is supposed to be available around the 18th of January. I'm hoping I'll have my SSN by then, otherwise we'll have to import a heap of money to pay for it. I'm sure you can get insurance and own a car without an SSN, because you hear of people who do driving holidays across the US, buying a car on one coast, driving it cross-country, and then selling it. It might be more expensive, and I again, you can't import your driving/insurance history, so you have to start off at the bottom of the ladder again... In summary, I think you need to have relatively deep pockets to bootstrap yourself over here. You need to be able to function without getting paid for up to two or three months, and you need to understand that credit-wise and insurance-wise, you're going to be back at square-one again, irrespective of how good you might have been in your home country. The sooner you come to terms with these, and appreciate that you are moving to a foreign country, the sooner you can get on with enjoying the experience.

    1 January 2006

    Antti-Juhani Kaijanaho: A restrospective on a functional programming course

    During the last two months, I taught an elective course on introductory functional programming. The nominal target group was third-year information technology undergrads, but in practice the student body consisted of everything from second-years to almost-done masters students. All had taken at least a year’s worth of general programming courses (taught in Java most recently, earlier in C++), a full semester’s worth of data structures, a half-semester of automata and grammar theory and some mathematics. I have enough teaching experience (been teaching two courses a year since 2002) to know my faults. My biggest fault is that I routinely underestimate the difficulty and laboriousness of tasks I set for my students. My second biggest fault is that if I am not careful, I can easily revert to reciting reference material, that is theoretical definitions, instead of giving a tutorial. I am better at avoiding the latter fault than the former, although when I have little time to prepare, the latter fault will, too, manifest itself. Knowing these faults, I tried to plan this course so that there would not be such trouble. Reading Baen books, I have learned a military saying: Battle plans never survive contact with the enemy. I found myself in a similar situation: my course plan did not survive contact with the actual teaching situation. The broad outlines of what I was going to teach held mostly. Other than that, it ended up being a very different course than I had originally envisioned. I started by giving a crash course on Haskell IO: how to write simple text-line-based interaction in Haskell. The idea was to introduce early the part of Haskell that many people think is hard but is actually quite easy, by explicitly drawing on the students’ imperative programming background. After IO, I ended up trying to give the students a broad, working knowledge of pure functional programming in Haskell, starting with first-order list processing and further discussing topics like parsing, persistent data structures, higher-order list processing, et cetera. I found that it was hard to give any of the topics proper room time-wise, as the basic concepts of functional programming are somewhat circularly related. At this time, the students complained that the course is hard, and many dropped out. They shouldn’t have; we had covered the main topics of the course in half the time. I could then use the rest of the time to go over the topics again from a different point of view, and give them time and tools to integrate it all to their own internal know-how databases. In the latter part of the course, on the surface we discussed Haskell metacircularly, but that was mainly a tool to reinforce the stuff done earlier in the course. Of course, my exercises were a little on the harder side. I ended up lowering official expectations about how much of the exercises the students were expected to solve, and that seems to have helped. Of the 20 people who took the first exam, 18 passed. The advanced course starts in a week or two.

    Andrew Pollock: [life] 2005: The year in review

    2005 is the first year I've blogged from start to finish, so it is interesting to go through and reflect on what has happened. It's certainly been an eventful year. Executive summary: got engaged, got married, got a job with Google, moved to the US. Did a whole lot of other mainly geeky things in between.
    January
    • Moved from living in an old rundown share house in Ainslie to a townhouse in Watson, without the flat mate
    • Started getting my teeth into work at my new job
    • Took Sarah to the ER with chest pains, after having had them on and off over Christmas
    February
    • Proposed to Sarah
    • My blog got syndicated on Planet Linux Australia
    • Wrote my blog post about mitigating SSH brute force attacks using Netfilter's recent module. Still get a lot of search traffic from that today
    • Went camping at Jervis Bay, managed to hit a kangaroo on the way, had a rather traumatic time trying to euthanize it
    • Decided to continue studying at Uni part-time in conjunction with full-time work (masochistic, huh?)
    March
    • Made changelogs.debian.net a whole lot spankier
    • Had a moderately unsuccessful time turning an old laptop with a dead hard drive into a diskless server with an NFS root filesystem. (I really must get around to trying again doing ATA over Ethernet)
    • Bought a QFE card, after much vying on EBay, which is still sitting in a drawer unused
    • Discovered how to make my laptop suspend
    • Completed a Saint John Ambulance Senior First Aid course
    April
    • linux.conf.au happened, and I helped make it happen
    • Interesting side-effect of the above was that I got asked to apply for a job at Google
    • I had fun with a cylinder of surplus helium
    • Sarah is advised to discontinue triathlons because of a possible heart condition
    May
    • My oldest friends separate, and it looks like they're going to get divorced
    • Sarah had her car broken into in the driveway and her purse was stolen
    • I get into a panic about passing Uni and really knuckle down
    • I discover a little too late that I've missed marking my ten thousandth day since birth
    • I organised a dinner meeting of Canberra Perl Mongers, which is a largely dormant group
    • We got a new cat
    • I hit two years as a Debian developer
    • I joined the Linux Australia sysadmin team
    June
    • We decide to bring forward our wedding from April 2006 to July 2005, "just in case" the Google thing comes off
    • caesar, the box I use as my gateway blew up and got replaced with something gruntier
    • I got into discussions with University House about doing a wireless LAN setup for them for their guests
    • Started work on a box for Linux Australia that would host a few User Mode Linux instances for various things
    July
    • My old Rover crew turned 20
    • We discovered the Tea Centre, and the wonders of different varieties of leaf tea
    • I scraped through first semester at Uni
    • I decided to upgrade daedalus and ordered a new box
    • Michael and I went to the US for face to face interviews with Google
    • Started semester 2 at Uni
    • Started migrating services to the new daedalus
    • Sarah and I were married
    August
    • Google makes me a job offer
    • I ordered myself a new laptop
    • My car tyres got slashed while I was at Uni
    • Uni all got a bit much, and I decided to drop out
    • I got a 1 gig USB key
    • I had some fun with LVM snapshotting
    September
    • Video card in my desktop blew up
    • I return to working in the office, and have a crack at catching the bus because of heinous petrol prices
    • I built Linux Australia's content mirroring box
    • The cat vomits one time too many and gets a new diet
    • We went and saw the Warehouse Circus' most excellent BAM! production
    October
    • I ascended Mount Tennant with Rick
    • Sarah and I went and checked out the Tumut 3 power station
    • Sarah got her wisdom teeth out
    • I had some more fun with LVM and data migration
    • I had even more fun with LVM snapshots
    • We finally got our visas for the US
    • I quit my job
    • We bought a new dining table
    • We bought an iPaq and a bluetooth GPS and some navigation software
    • We bought a new digital camera
    • Canberra Perl Mongers had another dinner meeting
    November
    • I finished up at Cybertrust
    • I went to the US
    • Sarah went to Singapore for a holiday with some of her relatives
    • I started at Google
    December
    • Sarah arrived in the US from Singapore
    • We found somewhere more permanent to live
    • We bought new mountain bikes
    • All our stuff arrived from Australia

    Junichi Uekawa: alioth disk full.

    I'll note it down here also, since IRC isn't very active at the moment.alioth server (cvs.alioth.debian.org, haydn) is disk full.My assertion is that org/ldap/log.* files are accumulatingtoo fast. It's consisting 20GB, and it has accumulated 20GB of such files apparently in the past two weeks.

    Enrico Zini: Leap second

    Found in the logs:
    Jan  1 00:59:59 eddie kernel: Clock: inserting leap second 23:59:60 UTC
    
    Oh, coolness!

    31 December 2005

    Antti-Juhani Kaijanaho: New year

    Thirty years ago I was not born yet. Twenty-five years ago I was having an adventure in the student village. Twenty years ago I lived in a red house (there was no potato farm, though). Fifteen years ago I started noticing politics. (It was hard not to.) Ten years ago I was nearly burned out because of both the demands of school and all the extracurricular activities I enjoyed. Five years ago I was doing my best to graduate to Bachelor’s Degree. Four years ago I had succeeded. Three years ago I had just finished my Master’s Degree. Two years ago I was trying to expand my Master’s Thesis into a postgraduate Licentiate’s Thesis. I eventually got sick of the topic. One year ago I had just barely lost my first elections and was fretting about getting elected as one of the local district court’s lay judges. Six months ago I was fretting about going to Debconf.
    Today, I’ve been thinking about tidying my room. In 2006, I hope to graduate to Licentiate’s Degree. I also hope I will be able to make some good progress in some of my bigger hobby projects. And to teach good courses. Maybe even improve dctrl-tools further.
    Happy new year 2006!

    Junichi Uekawa: The real ksh.

    I've implemented the real ksh for hackers.It's a shell that interprets C code line-by-line, and runs each line of code in kernel mode(by building modules with that line on the fly and doing an insmod/rmmod).It's pretty slow, and doesn't feel too interactive, but here it goes.I'm sure most people hacking on the kernel have this kind of setup already.Here is the full text (binfmtc-style).An example transcript follows:

    Antti-Juhani Kaijanaho: Strange sounds

    It’s ten past nine on a Monday morning. I am usually at work at this time, but not today. Tomorrow’s the Independence Day, and I’m, as usual, staying home for the single work day that this generates. Suddenly, I hear a very powerful growling sound. It lasts about ten seconds. It is so powerful that everyone in the neighbourhood ought to hear it. About twenty seconds later, there are a series of equally powerful electric but almost otherworldly jingle sounds. They last about ten seconds. About twenty seconds later, the general alarm is sounded: a continuous siren first raising the pitch then lowering. It stops after one “wave”. A relief: it is a test of the general alarm system. I had read about the sound-based remote control of the general alarm system, but this was the first time I observed it in use. Had I not already surmised that this was going on from the start, I would have been seriously frightened by the strange sounds. About a minute or two later, while I was already composing this, I heard very faint jingling, followed by a very faint general alarm. Obviously, the system was being tested elsewhere.

    Antti-Juhani Kaijanaho: Independence Day repost

    The following is a repost from my old blog, originally written one year ago. As I start to write this, it’s the last minute of my country’s 87th birthday (the Finnish Independence Day). It got me thinking about nation-states and independence and whatnot. And I came to a threefold conclusion: First, there is some value in independence. Getting rid of the status of a Grand Duchy in personal union with Russia was certainly a good step for Finland, in light of the rough road the Russians themselves have since travelled. For the same reason, the two wars Finland fought against the USSR were quite worthwhile. Similarly, if Finland were to be threatened by a neighbour again, armed defense would certainly be justifiable. Second, there is no intrinsic value in independence. If a humanly life (including freedom and local government) can be guaranteed even if there is no Finnish state in itself, I see no reason to hold on to the old-fashioned concept of a nation state. Third, I am in favour, as a long-term goal, of a world government. Of course, a single government becomes a single point of failure in case of a coup, for example, but if the global state is arranged properly, the danger of a successful coup is minimal. On the other hand, a world government is in far better position to institute necessary policies to combat the global problems of poverty, climate change and other such issues than the current system of competing and cooperating nation-states. In the current system, the big issues are easily put aside in name of local opportunism. Finland is by no means immune to that problem. The great crises of the 20th Century were its devastating wars. Fortunately, we have overcome them to a sufficient degree. The great crisis of the 21st Century is not terrorism – though it is a symptom. The great crisis is caused by the limits of growth, and we are already feeling quite concretely the nearness of those limits. If something is not done, our current civilization will crash spectacularly. The human race will probably survive – but do we really want to live through another Dark Age? Long Live the Earth!

    Antti-Juhani Kaijanaho: Pain and suffering and other immaterial personal damage

    Martin- ric Racine asked in the comments to my previous mini-essay on crime-related damage compensation about how immaterial losses, such as pain and suffering, are given monetary value in court. In this essay, which is again part of my essay series on Finnish criminal justice, I will try and sketch an answer. As usual, I am not a lawyer and this is not legal advice, and this is not an exhaustive treatise on the subject. Finnish law is very vague about how immaterial damage is compensated. It basically only gives a list of the forms of immaterial loss for which compensation can be ordered by a court. The main categories related to physical injuries are kipu ja s rky (usually translated somewhat inaccurately as pain and suffering) and pysyv haitta (permanent handicap). Kipu refers to the instant pain suffered when the injury is created, and s rky refers to the longer-term but not permanent pain present after the kipu has ended until the injury is healed. A new act of parliament will amend this at new year, specifying these in greater detail. It amends the existing Damage Compensation Act by defining a list of things that are to be given special weight when measuring the monetary value of personal damage. For pain and suffering, those things are the type of the injury, the type and duration of medical treatment it required, and how long the pain and suffering lasted or is expected to last. For permanent handicap, however, the list is a little different: the type and extent of the injury, and the age of the injured person at the time of injury. This is basically just writing out the existing legal praxis. There is currently no specific standard against which the courts compare individual cases. However, since one is desperately needed, the courts generally use a substitute. There is a governmental board whose job is to set a standard monetary valuation for different types of injuries sustained in traffic accidents. That standard is intended to be used by insurance companies, but in practice, courts also use them as a guide when considering injuries caused by criminal acts. In relation to pain and suffering, the standard categorizes injuries as follows:
    Category A (petty injury)
    will heal fully leaving no marks in a week or two, requires no hospitalization, causes at most two weeks’ inability to work – scratched skin, small cut, minor bruises etc.
    Category B1 (minor injury)
    requires no resuscitation nor intensive care, requires up to a week of hospitalization without surgery, causes at most two months’ inability to work, causes only insignificant permanent disability – significant bruising, loss of few teeth, simple bone fractures etc.
    Category B2 (medium injury)
    may require resuscitation but not intensive care, requires one to three weeks of hospitalization, no complications in treatment, no need for reconstructive surgery in later care, causes at most seven months’ inability to work, causes only minor permanent disability – simple fractures of the long bones, fractures of facial bones, etc.
    -Category C1 (major injury)
    requires cardiovascular or pulmonary resuscitation, requires short-term respirator use or tracheostomy, in the case of a limb injury, requires demanding surgery, requires reconstructive surgery in later care, requires up to eight weeks of hospitalization, causes up to eight months of inability to work, causes significant permanent disability – loss of all teeth, complicated bone fractures etc.
    Category C2 (especially major injury)
    requires long-term mechanical respiration or resuscitation, major complications in treatment, requires extensive surgery, requires hospitalization for longer than eight weeks, causes a year of inability to work, causes major permanent disability – loss of limb, significant brain damage, loss of fertility, severe burns etc.
    Category C3 (extraordinary injury)
    extraordinary complications in treatment, long-term hospitalization, causes complete disability, causes helplessness – extreme brain damage causing dementia, loss of both upper limbs or both lower limbs, causes permanent pain, permanent quadriplegia, causes complete blindness
    As you can see, all categories are described both by the treatment required and by listing sample injuries. These descriptions are complementary, and not identical. In categories A and B, the treatment-based descriptions are conjunctive (all requirements must apply), and in C, they are disjunctive (at least one must apply). I did not translate the descriptions completely; see the Finnish original source if you need more detail. The traffic injury standard currently specifies the following monetary values for each category:
    Category Compensation
    A see below
    B1 200–1,000
    B2 1,000–2,900
    C1 2,900–7,300
    C2 7,300–16,700
    C3 at least 16,700
    Due to a quirk in the traffic injury ccompensation system, Category A is not compensated in the case of traffic injuries. This does not apply in criminal cases, where Category A is usually taken as “up to 200 ”. Of course, the specifics of the case will sometimes require departing from this standard in criminal cases (the aggravation in the crime often is taken as a reason to up the monetary damage estimate). Permanent damage is similarly handled by courts by referring to the standard set for the statutory employee’s accidental injury insurances (see the Finnish sources 1 and 2 for details). I already mentioned above a new act of parliament. That act, which will enter into force January 1, 2006, creates a new Personal Damage Advisory Board (henkil vahinkoasiain neuvottelukunta), which will follow legal praxis and give recommendations, much like the above-described standard, which courts and other instances deciding on compensation for personal damage can take as a base standard against which individual cases can be measured. The advisory board’s recommendations are likely to supplant the traffic damage standard described above in the future.

    Next.

    Previous.