Search Results: "ag"

13 April 2007

Ross Burton: Announcing Pimlico

Pimlico OpenedHand have announced Pimlico, an umbrella project for our PIM applications: Contacts, Dates, Tasks and Sync (in progress). Released at the same time was Dates 0.4: this release is a vast improvement on the previous release and now available in three flavours: desktop, Maemo, and OpenMoko. At the same time we sneaked out an updated set of evolution-data-server packages for Maemo 3.0. As far as the user is concerned the only changes are that addressbook syncing will work (using OpenSync or SyncEvolution), and that WebCal is supported (as used by Dates). NP: Urban Biology, Machine Drum

Arnaud Vandyck: libhibernate-java Take 4, fop and other updates

    • New packages
  • qdox_1.6.1-1 (#323043 and #418673)
  • xmlgraphics-commons (#418896)
    • New upstreams
  • commons-io: #418973, #397567
    • Bug fixes
  • libgef-java: #418865
  • read more

    Daniel Burrows: coq's -ness-nesses

    In response to Stefano's reply to my post about Coq:

    toy-ness

    Usually such pieces of software are more seen as academic toys, seeing it promoted as a geeky software is a joy to me.


    I really hate to detract from your happiness -- but I definitely had the word "math" implicitly stuck before "geek toy". :) Most coders that I've met are, at best, indifferent to mathematics, outright hostile at worst, so I doubt that coq will get far outside of small niches where the benefits are irresistable (security software, maybe? -- and of course pure math). I read up on this stuff despite it being utterly useless for anything I'm likely to be paid to do (unless I return to academia) because I'm a hopeless weenie loser who likes math. :P

    programming-language-ness

    Coq is not really a programming language (even if the CoqArt book says so, to attract the developer community), it is mainly a proof assistant; i.e. a software in which you give definitions, state theorems and prove them.


    Well, this all depends on how you define programming language, which is one of those never-ending definitional questions. But using my general conception of what a programming language is, I actually have noticed two programming languages inside Coq.


    1. The more interesting one (IMO) is the proof language they call "Gallina" and the "Vernacular", in which you construct proofs by reducing your goal to a tautology. The goal here seems to be to compute a well-typed term in Coq's core calculus, and you generally construct programs interactively: Coq shows you the current program state (expressed as one or more goals and a set of local hypotheses) and you manipulate it by (e.g.) applying lemmas to yield new known facts.

      I think this language is fairly weak viewed as a programming language. It's completely unreadable and the proofs generated don't correspond to the reasoning process one normally follows when working out a proof. I am less annoyed by it now that I've learned how to do forward reasoning :), but it seems like backwards reasoning is really pushed, and that just seems .. well .. backwards to me. There's also a strong tendency to use implicitly generated names for things and to just "know" what the state of the system after issuing a command will be; as far as I can tell, the only way to understand a Coq proof is to step through it in coqide.

      While it's nice to be able to "trust the kernel", it would also be nice to be able to "read a proof" directly. Among other things, their inscrutability makes me think that Coq proofs would be annoying to maintain over time. This is not necessary for stuff that's part of Principia Mathematica, but seems likely if you're developing a new theory -- in particular, I would shudder (theatrically) at the mere thought of including embedded Coq proofs in my programs.

      Some additional brief comments on this were written by Nick Benton and put on the Web under the title of Machine Obstructed Proof.

    2. The other sense is that Coq directly embeds a strongly normalizing variant of System F (I think? -- at least the simply typed LC with some type parametricity) with primitive recursion over inductive structures. This isn't Turing-complete (of course!), but I would certainly call it a real programming language.

      As you note, though, this is less interesting unless you want to prove facts about your programs.


    OCaml-ness

    Regarding the synergy of Coq with OCaml: yes, you can prove in Coq the correctness of OCaml program, but actually not more than you can do with programs written in other programming languages


    I was specifically thinking about Concoqtion; I have no idea how other projects compare, and I apologize if I incorrectly summarized it!

    Christian Perrier: Running etch (2)

    A coupld of glitches appeared lately during my sarge->etch upgrade for my home server: There are probably a few others things to tweak, still. But I had no problem with the samba server, the squid cache, the postfix settings, IMAP server, which means that the entire family can still use their computers without hassle, which was the major challenge in this migration.

    Jaldhar Vyas: That LILUG Talk

    As mentioned previously I was invited to talk about Debian at the Long Island Linux User Group. Much to my embarrassment I had forgotten I had actually spoken at this venue before way back in 2003. But the audience (which of course included many members who had joined since then) were receptive, and asked lots of questions which I like. I did my "Three Pillars of Debian" talk updated for Etch with snazzy new slides — feel free to use them in your own presentations if you like. I was supposed to speak for two hours and ended up speaking for three. So hopefully I managed to impart some useful information and maybe make some new recruits. I would like to publically thank John Teddy and all the people at LILUG for inviting me. Also, note for the future: I really ought to learn how to correctly pronounce Hocevar. Sam, you should put up an audio clip somewhere.

    Sam Hocevar: shlib-with-non-pic-code: have inline assembly and PIC mix well

    Perhaps the most accessible documentation on what PIC code is and how an ELF dynamic linker works is John Levine s Linkers and Loaders (and it has amazing sketches, too!). The Gentoo documentation also has an Introduction to Position Independent Code. I d like to give a few hints on how to fix the shlib-with-non-pic-code lintian error caused by inline assembly on the i386 and amd64 platforms, as well as build errors that may occur due to inline assembly being used. I m not going to cover the trivial all objects were not built using gcc s -fPIC flag problem. It usually requires a fix to the build system, not to the code. gcc can t find a register (i386) PIC on i386 uses a register to store the GOT (global offset table) address. This register is usually %ebx, making it unavailable for use by inline assembly (and also restricting the compiler's register usage when compiling C or C++ code). So the following perfectly valid code will not build with the -fPIC flag:
     void cpuid(uint32_t op, uint32_t reg[4])
      
        asm volatile("cpuid"
                     : "=a"(reg[0]), "=b"(reg[1]), "=c"(reg[2]), "=d"(reg[3])
                     : "a"(op)
                     : "cc");
      
    Using -fPIC, gcc will say something around the lines of error: can't find a register in class BREG while reloading asm . Several things need to be done to fix this: And here is the PIC-compliant version:
     void cpuid(uint32_t op, uint32_t reg[4])
      
        asm volatile("pushl %%ebx      \n\t" /* save %ebx */
                     "cpuid            \n\t"
                     "movl %%ebx, %1   \n\t" /* save what cpuid just put in %ebx */
                     "popl %%ebx       \n\t" /* restore the old %ebx */
                     : "=a"(reg[0]), "=r"(reg[1]), "=c"(reg[2]), "=d"(reg[3])
                     : "a"(op)
                     : "cc");
      
    using variables from assembly code (i386) Directly using variables from inline assembly always creates non-PIC code even if -fPIC is being used. There are at least three strategies to consider when trying to fix this. Here is an example of PIC-incompatible code:
     extern uint32_t sym1, sym2, sym3;
     
     void store_in_symbols(uint32_t x)
      
         asm volatile("movl %0, sym1   \n\t"
                      /* ... */
                      "movl %0, sym2   \n\t"
                      /* ... */
                      "movl %0, sym3   \n\t"
                      : : "r"(x));
      
    The first strategy is to pass the variable through the usual gcc inline assembly syntax. This is not always possible because there might be a shortage of registers, but here is what it looks like:
     extern uint32_t sym1, sym2, sym3;
     
     void store_in_symbols(uint32_t x)
      
         asm volatile("movl %3, %0   \n\t"
                      /* ... */
                      "movl %3, %1   \n\t"
                      /* ... */
                      "movl %3, %2   \n\t"
                      : "=r"(sym1), "=r"(sym2), "=r"(sym3) : "r"(x));
      
    If there are too many variables and not enough registers, one can use the second strategy: put all required variables (or addresses) in a table, thus requiring only one extra register:
     extern uint32_t sym1, sym2, sym3;
     
     void store_in_symbols(uint32_t x)
      
         uint32_t tab[3];
         asm volatile("movl %1, (%0)   \n\t"
                      /* ... */
                      "movl %1, 4(%0)  \n\t"
                      /* ... */
                      "movl %1, 8(%0)  \n\t"
                      : : "r"(tab), "r"(x));
         sym1 = tab[0];
         sym2 = tab[1];
         sym3 = tab[2];
      
    If the second method happens to be unsuitable because variable types differ too much, there is a third, more complicated strategy: retrieve the GOT address using some linker-specific magic, then use @GOT addressing to access variables:
     extern uint32_t sym1, sym2, sym3;
     
     void store_in_symbols(uint32_t x)
      
         uint32_t got;
         asm volatile("call get_got                               \n\t"
                      "get_got:                                   \n\t"
                      "popl %0                                    \n\t"
                      "addl $_GLOBAL_OFFSET_TABLE_ - get_got, %0  \n\t"
                      : "=r"(got));
         /* ... */
         asm volatile("pushl %%ebx                \n\t" /* save ebx */
                      "movl sym1@GOT(%0), %%ebx   \n\t" /* retrieve sym1 address */
                      "movl %1,( %%ebx)           \n\t"
                      /* ... */
                      "movl sym2@GOT(%0), %%ebx   \n\t" /* retrieve sym2 address */
                      "movl %1, (%%ebx)           \n\t"
                      /* ... */
                      "movl sym3@GOT(%0), %%ebx   \n\t" /* retrieve sym3 address */
                      "movl %1, (%%ebx)           \n\t"
                      "popl %%ebx                 \n\t" /* restore ebx */
                      : : "r"(got), "r"(x));
      
    It is of course possible to merge the two above asm statements into one. However the performance implications of the GOT address retrieval should not be overlooked, especially if the assembly code takes place inside a critical loop, which means the loop might have to be unrolled and the GOT address retrieval done outside the loop. Note also that _GLOBAL_OFFSET_TABLE_ is ELF-specific. On BSD and a.out systems you should use __GLOBAL_OFFSET_TABLE_. I am not aware of a way to do the same on Darwin / Mac OS X, which is a shame because it is the only widespread i386 platform where shared objects cannot be non-PIC. gcc silently generates non-PIC code (amd64) The amd64 architecture has the same problem as i386 when trying to access variables from assembly code. However, the solution is a lot easier: the GOT address can always be retrieved from the special %rip register. This is called rip-relative addressing:
     extern uint32_t sym1, sym2, sym3;
     
     void store_in_symbols(uint32_t x)
      
         asm volatile("pushl %%rax                       \n\t" /* save rax */
                      "movq sym1@GOTPCREL(%rip), %%rax   \n\t" /* retrieve sym1 address */
                      "movl %0,(%%rax)                   \n\t"
                      /* ... */
                      "movq sym2@GOTPCREL(%rip), %%rax   \n\t" /* retrieve sym2 address */
                      "movl %0,(%%rax)                   \n\t"
                      /* ... */
                      "movq sym3@GOTPCREL(%rip), %%rax   \n\t" /* retrieve sym3 address */
                      "movl %0,(%%rax)                   \n\t"
                      "popl %%rax                        \n\t" /* restore rax */
                      : : "r"(x));
      
    amd64 also has more registers than i386, which makes the first discussed technique less prone to register shortage. Why bother? Good question. Currently many shared libraries simply disable entire chunks of inline assembly on the amd64 architecture. Whether these routines bring any performance benefit compared to the C alternative is uncertain, but without being able to build the code there is no way to tell. Even fewer developers care about i386, because this architecture can handle non-PIC shared objects quite fine (but then they are no longer really shared). I am in favour of making all shared objects PIC-friendly (ie. not necessarily build them as PIC if there is a valid reason not to, but at least don t make it too difficult to build PIC versions) because that makes it easier to port the code to Darwin. I also believe the memory gain and especially the cache gain when using real shared libraries is underestimated.

    Erich Schubert: Init followup

    Gunnar Wolf commented on my recent series of init script posts. Thanks for the feedback.The thing is that I've been doing a lot of Debian stuff these days (such as our GSoC coordination, and lots of stuff you saw in this blog). But I shouldn't... instead I should be trying to finally get my diploma thesis done.I had my exams last july. If I had been focused, I could have been finished with my degree last christmas. Now it will likely by this fall. :-( All that is remaining is my final thesis. It should be written in 6 months, but I still havn't submitted my topic yet. So if you are wondering what took me 8 months already: I investigated two topics, but they didn't work out. Then I started researching for my 'current' topic, and I have a vision for it, but I still havn't managed to convince my professor (which of course is largely due to me not being able to convey this idea, and that the topic is in information management and representation, where it's probaly often hard to find a solid theoretical part. I have examples I'd like to do, and I hope they are actually convincing, but I have no idea how to 'prove' something here; it's too much about social aspects and human perception I guess, and I'm not really qualified or capable to do solid research in that field.)(And as you can probably imagine, I'm pretty fed up with studying now. A year ago, I'd have considered to go for a PhD afterwards, but now I just want to get out, and work on my projects.)Anyway, I got distracted. Back to the init topic.I already posted this link: Init Hackfest, as well as a pointer to the initscripts-ng mailing list. I'd really like to get this topic on it's way for lenny. So please, join this effort. While I'd like to push it, I shouldn't; on contrary, I should suspend my Debian efforts.As for your (Gunnar) suggestion on how to handle multiple inits: what's wrong with just including multiple init scripts in one package? They are not particularly large and compress well. A single init script package might already be bigger than all the init scripts.The problem is more on how to write these init scripts; by the time we're done with this project, we might actually have hit 1000 init scripts. Yes; I didn't just make up this number: packages.debian.org has 890 hits for /etc/init.d; the init-like scripts in /etc/dbus-1/event.d not included. So if just want to add support to 5 alternate init systems, this means we would need to write 5000 new init scripts. Ouch. So we maybe should convert them to 1000 meta-init-scripts instead, and generate the 6000 real init scripts from them.Please join the discussion, and lets get this project going, despite having to face such scaringly high numbers...

    Evan Prodromou: 22 Germinal CCXV

    A lot of people have asked me about the Tim Wu piece in Slate about Wikitravel. I've commented already about the article in Wikitravel's Logbook: 8 April 2007. The upshot: Wu got a lot of things really wrong about Wikitravel (like saying we didn't have any hotel listings for Bangkok). But if our readers get things wrong, that means Wikitravellers need to do some more work to help them get things right. User errors are developer errors writ large; we can do better. But I think Tim Wu missed the main reason Wikitravel guides will always be better than proprietary guides: they are Free Cultural Works. Where I come from, that means a lot. I wrote to Tim about his article, and he responded really kindly. The thing I liked most is that when he got home, he updated Wikitravel with the information he picked up on his trip to Thailand. That is pretty cool. I'm not taking others' responses to the article too seriously. Wikitravel got a Webby Award nomination for Best Travel Site the same week. As Tom Wolfe said, "The lead dog is the one they always try to bite in the ass." And Oscar Wilde: "The only thing worse than being talked about is not being talked about." (Thanks to Hugh!) tags:

    Off to San Juan We're getting prepared this morning to head out to Puerto Rico for the first annual World-wide Wikitravel Get-together. Our flight leaves at 2:20PM, so we've got kind of a leisurely morning to get ready. As usual, we're pretty tense: what are we forgetting? And I usually get hung up on unnecessary stuff to deal with. I should probably print out the Spanish phrasebook from Wikitravel, because my Spanish is pretty rusty. And I should download all the WT pages about Puerto Rico destinations to my laptop, just to know where we should fill in. And we can't find the charger for our camera's battery. And I want to bring a certain pair of cargo pants, but there's a button missing. Do I have time to sew on another? Of course, all these anxieties melt once we get out of the house and into a taxi to the airport. Once you can't do things, you stop worrying about what you should do. I think. The more I learn about Puerto Rico, the more fascinated I am. San Juan (Puerto Rico)'s Old Town is a UNESCO World Heritage site. The giant telescope at Arecibo is world-renowned as the SETI site. The islands of Vieques and Culebra are isolated and fun, and Fajardo and Rincon has world-class surfing. My friend Biella Coleman gave me a great list of travel tips for San Juan and Culebra, which have been a big help in our planning. OK, enough blogging: gotta get to work sewing on that button. (I've been stalling long enough for Maj to have found the camera charger under a baseball hat. Yay!) tags:

    12 April 2007

    Rob Bradford: Dates 0.4 Released!

    (Rapidly followed by 0.4.1) I’m very pleased to announce that Dates 0.4 has been released to the world, this release includes support for multiple local and remote calendars (including read-only access to Google Calendar.) It is available in three stunning flavours all guaranteed to be buzzing with energy but 100% fat free. N800 owners can use the Application Manager to install dates by using this install link. Packages for Debian/Ubuntu are being built now. Hopefully we should be able to get packages built for the Nokia 770 soon. Dates also has a cool new icon, courtesy of Andreas Nilsson. Andreas has also designed icons for the other components of, as well as the website for, the Pimlico Project which launches today. Pimlico is the umbrella project for all the OpenedHand PIM applications; Dates, Contacts, Tasks and Sync.
    The funky new Dates icon.

    Christian Perrier: Running etch

    I just upgraded my home server (kheops) to etch. I just had an issue with lifelines-report, which the former maintainer should be ashamed of. Apart from that glitch, the upgrade went well, thanks to the excellent upgrade advices in the Release Notes. Funnily, I got warned that kheops still has the "base" package installed which I didn't notice in former upgrades. This is pretty expected as kheops has never been reinstalled, is my home server since october 1996 when I installed Debian Buzz on it. I think that I'll just avoid following Santiago Vila's advice and leave "base" installed on my system, indeed. Just for fun. This is the 6th server I upgrade as of now. All other servers were pretty minor servers at work. The big issue is now upgrading the file and print servers and particularly the samba file server which hosts files for 250 users. This is probably the one and only server for which we will setup a clone and play the upgrade scenario a few times. Etch rocks, as expected.

    Biella Coleman: On My Aunt Enid, Cars, and History

    Those who know me even moderately well (as well as every doctor I have ever seen), knows that my real first name as “Enid.” That is the mysterious E. that sometimes precedes the Gabriella. My mom’s intention was to call me Gabriella, the first name of some famous Italian Cabaret singer, Gabriella Ferranti. But when Enid, my aunt on my fathers side, passed away a few months before I was born, I was given the name Enid Gabriella. We have always used Biella or Gabriella but I like that I have Enid in there and have fancied from time to time to start using the name Enid. By all accounts, Enid was an amazing and energetic woman, who reared her four kids with passion, was very open to friends and family, and who, despite living a solidly upper middle class Jewish life, was also involved in interesting political work(like helping Americans doge the draft by escaping to Canada). My mom held a special fondness for her because, well, honestly I think she was one of the only members of my dad’s family who she deeply loved. And Enid always went out of her way to show her care and concern, as when she immediately went to Caracas after my mothers first child unexpectedly died of a high fever at the age of five months. Today as I was writing away, I received an email from my father that he sent to me and a bunch of cousins and other siblings where he attached a 9 page document of remembrances and memories of Enid. My dad, though in no way as bad off as my mother (health wise), is no spring chicken. And I think as he fast approaches 80 years old, he is committing a lot to writing and thus, keeping his memory alive for us. In fact, this reminded me of a really beautiful quote I recently came across on memory:
    “You have to begin to lose your memory, if only in bits and pieces, to realize that memory is what makes our lives. Life without memory is no life at all, just as an intelligence without the possibility of expression is not really an intelligence. Our memory is our coherence, our reason, our feeling, even our action. Without it, we are nothing.” Luis Bu uel
    But what was a little odd (but nonetheless very endearing) about most of the account is that it was not organized by stories, or date, but by car models. Yes, by technology. My dad organized the stories about Enid by virtue of the cars they had, which struck me a little strange because it is not like he was a car buff or anything (growing up we always had the most unsexy cars, like Ford Tauruses). The cars he covers are the following: The Model A Ford Convertible
    The 1941 Oldsmobile
    The 1948 Buick Convertible
    A Chevy Convertible Once you read his little tribute, it becomes immediately clear that his choice of talking about cars is also way for him to talk about history which is my dad’s great love (he can talk to you straight for 5 hours about some odd event in WW II and why he should have become a historian) as it is about Enid. Case in point here:
    This was the first General Motors car with automatic drive. It was called Hydromatic and even though this car had a powerful 8-cylinder engine, this first automatic drive was very sluggish. Forget about 0 to 60 miles an hour in 7 seconds. This was in minutes. It was the car that Abe used to teach both Enid and I to drive. We both had to have additional lessons with a stick shift car, because the driving test was only given on stick shift cars. I learned to drive in 1944, when I was 16. Enid took lessons from Abe and learned to drive in 1945 when she was fifteen. This was against the law, but the law in the name of Tom, the policeman that covered our neighborhood, liked Enid and looked the other way.
    For those who care to read more (it may only be amusing to me and those few people that are into American car history), I have included all the cars and here are the main cast of characters. Ruth = My Grandmother
    Abe = Grandfather
    David = Dad
    Enid = My Aunt, David’s sister (more…)

    Erich Schubert: System init - part #3

    Today's post (previous parts) tries to show what benefits other init systems can offer.I'm picking 'minit' as an example; not because it's the ultimate solution or anything, but because I happen to know it quite well. I used to be the package maintainer for some time, and I've also used it on an embedded system (where it was a perfect match). However, it's not very distribution-friendly; it's great when you can invest some time into configuring it (such as when building an embedded system) but not when it should ideally work automatically out of the box. The Debian package is still there, but it's orphaned. Still it's well written, clean code; there shouldn't be any bigger bugs in there.The first thing to notice is that minit is tiny. It's statically linked, but only about 6.5 kb. Regular init is 86 kb plus some libraries (despite actually not doing much during init!). This makes it very well-suited for embedding.But now for the benefits of minit over regular init:1. Service monitoring. This is the biggest point: minit will keep an eye on the services and restart them when needed. (Another thing very useful in embedded situations, btw.)Minit doesn't use the start/stop paradigm of sysv/shell-style-init. Instead it has a "run" script for every service. If a service is flagged as 'respawn', it will automatically be restarted when the run script quits; therefore the applications should not background themselves. This offers some benefits, for example the init process will be notified by the kernel of a termination, and can immediately respawn the service; in contrast to other monitoring systems suchas monit it doesn't rely on 'busy polling'.2. Dependency handling. Minit handles startup dependencies. If a service lists another service as a dependency, it will bring that service up first.3. Parallel startup. Unless an ordering is given via dependencies, minit will start the services in parallel.4. Control apps. In minit, you don't start a service by running some random shell script. Instead you call "msvc -u servicename", which will signal minit to bring up the service (and it's dependencies). This would (there currently is no policy for minit) be especially useful in SELinux, but it also allows to e.g. give a user the permission of running "sudo msvc -u" without introducing a huge security hole, since this cannot be used to execute arbitrary scripts. "msvc" can also be used to check if a service is up. (Another benefit for embedded systems, since that removes the need for pid files, which then need a ram (writeable) filesystem)I'll also give an example for a minit service:A service is represented by a directory in /etc/minit which can contain various files. I'm going to look at getty/1 example; which will bring up a console login on the first terminal. There are three files: If the service would need it, there could also be a file called "depends" listing service dependencies.This allows minit to start the getty with no overhead. There is no shell script being executed or anything (note: sysvinit also does this for gettys, but it's not being used much for other services).Of course minit isn't perfect. I've already said that it isn't particularly distribution friendly. This is because it uses a lot of magic files (e.g. an empty file named 'respawn' to flag a service as needing to be respawned), and it's configuration files aren't easy to handle automatically. The often frowned-upon 'symlink farms' of sysv-shell-style init are much better here.Another thing that is missing from minit is an automatic rollback of dependencies. If we told minit to bring up service 'a', which lists dependencies 'b' and 'c', minit will bring these three up. If we tell it to shutdown 'a', it will however not shutdown 'b' or 'c'. And unfortunately, even if we shutdown 'b', it won't shutdown 'a'. If you want a more complex dependency handling (or things such as runlevels), you need to do this externally. (An example is my 'enitdir' app, it adds runlevel support to minit, and allows switching of runlevels by replacing a symlink; Services are added and removed from runlevels by adding a symlink to the service into the runlevels directory. By using dnotify, this also takes virtually no CPU time.)Minit also lacks a differentiation between a 'started' and a 'running' service. It has support for 'sync' services, such as e.g. mounting a filesystem. It will wait for this operation to complete before it starts services depending on it. However, there are services that will continue to run, while not being instantly available when the exec() was called. Sometimes it would be nice if a service could go into a 'started' state, then do some cleanup work, and then when actually running the real service signal minit that it's now 'running'.As a last malus, minit won't print progress messages to the console. A minit boot is pretty much silent, directing it's output to some logging processes. There are good reasons for this (since services are started in parallel!), but it makes debugging harder, and users might be wondering what their system is actually doing (though some users prefer to see a colored 'busy' bar)...I guess this concludes this series of blog posts. Maybe someone can follow up with some details on upstart (which seems to be the most promising init replacement)? I hope to have given an impression on where there is room for improvement in our current init to one or the other. Now we just need some people to actually work on a better support for other inits in Debian...

    MJ Ray: Environment: Low Carbon Lifestyle Tour

    Carpenter Mukti Mitchell has set off on a tour of the coastline of Britain in a zero-emission microyacht promoting low carbon lifestyles. During the course of his voyage, he will be stopping at 40 ports and towns around the country with events organised to promote low carbon products and services. He doesn't call at Clevedon or King's Lynn (I guess they're too far inland) but he's currently in South Wales and should be calling at Wells-next-the-Sea on 21 July and Sheringham on 23. More dates The Phone Co-op (agent 471) is a co-sponsor of this event with, among others, Ecotricity, Resurgence and Co-operative membership so at least two of my co-operatives are supporting it.

    MJ Ray: BBC Radio 4, Again, Again

    Kris Marsh commented:
    "Thanks for the blog, I'd never have known about the BBC4 open source slot otherwise! Unfortunately I missed it, but I did notice that it's available on BBC's "listen again" feature "
    So, what did you think of it? Post comments to my site or to fsfe-uk.

    Kartik Mistry: Re: How To Minimize Your Value to The Company

    * t3rmin4t0r wrote a really great post “How To Minimize Your Value to The Company“. Here is my views: - Answer questions on devel forums - Yes. I used to maintain some forums, which gave me some ‘pet’ name!
    - Write a technical blog - Yes (sometime!)
    - Live the company values - Yes
    - Write cool hacks - Yes.
    - Have a serious hobby - Yes.
    - Contribute to an open source project - Yes. It depends. All of us know that ‘How much business you bring to company?’ is the core question. But, I am not feeling that my value has decreased or become minimized yet.

    Erich Schubert: Apologies if I'm breaking a planet

    I've done a needed upgrade to my blog software. In this process, I've also been changing my blogs GUIDs. Unfortunately, this probably means that some planets or feed readers will recognize all of my postings as 'new'. Sorry about that. I'm not sure if I can somehow prevent it from happening.Every now and then I receive a mail from someone complaining that the links to my blog entries are broken. Well, they aren't. The link tag has an appropriate value. However some applications (usually involving planet) prepend the feeds base URI to the GUID field or use it in other RDF places. And then some readers seem to not know about the link tag and use that instead. So I'm now using the permalink as GUID, so it should be a bit easier for some people, since they now can just click on my entries.

    Carlos Villegas: Etch boots as fast as Woody...

    With the Post-etch frenzy, I installed Debian 4.0 stable as soon as I could. I used the same system used a few months ago for the google Summer of Code. Under the same conditions, the system required 32 seconds until KDE started. Compared with the previous stable releases:
    Nevertheless, Etch has significantly more process started at boot time and the CPU usage is more intensive --with still some room for improvement --. Follow this link for the bootcharts and more detailed information.

    As I starting point, using dash instead of bash, the boot time is reduced to 30 seconds and it could be further improved but there is some "hald" process (maybe part of dbus) that doesn't seem to want to run in parallel. See bootcharts. Any ideas?

    Russell Coker: presentations about SE Linux

    I have just read the Presentation Zen blog post about PowerPoint.

    One of the interesting suggestions was that it's not effective to present the same information twice, so you don't have notes covering what you say. Having a diagram that gives the same information is effective though because it gives a different way of analyzing the data. I looked at a couple of sets of slides that I have written and noticed that the ratio of text slides to diagram slides was 6:1 and 3:1 in favor of text, and that wasn't counting the first and last slides that have the title of the talk and a set of URLs respectively.

    So it seems that I need more and better diagrams. I'll include most of the diagrams I use in my current SE Linux talks in this post with some ideas on how to improve them. I would appreciate any suggestions that may be offered (either through blog comments or email).

    The above diagram shows how the SE Linux identity limits the roles that may be selected, and how the role limits the domains that may be entered. Therefore the identity controls what the user may do and in this example the identity "root" means that the user has little access to the machine (a Play Machine configuration). I think that the above is reasonably effective and have been using it for a few years. I have considered a more complex diagram with the "staff_r" role included as well and possibly including the way that "newrole" can be used to change between roles. So I could have the above as slide #1 about identities and roles with a more detailed diagram following to replace a page of text about role transition.

    The above diagram shows the domain transitions used in a typical system boot and login process. It includes the names of the types and a summary of the relevant policy rules used to implement the transitions. I also have another diagram that I have used which is the same but without the file types and policy. In the past I have never used both in the one talk - just used one of the two and had text to describe the information content of the other. To make greater use of diagrams I could start with the simple diagram and then have the following slide have all the detail.

    The above diagram simply displays the MCS security model with ellipses representing processes and rectangles representing files.

    The above diagram shows a simplified version of the MMCS policy. With MMCS each process has a range with the low level representing the minimum category set of files to which it is permitted to write and the high level representing the files that it may read and write. So to write to a file with the "HR" category the process must have a low level that's no higher than "HR" and a high level that is equal or greater than "HR". The full set of combinations of two categories with low and high levels means 10 different levels of access for processes which makes for a complex diagram. I need something other than plain text for this but the above diagram is overly complex and a full set is even more so. Maybe a table with process contexts on one axis, file contexts on another and access granted being one of "R", "RW" or nothing?

    I also have a MLS diagram in the same manner, but I now think it's too awful to put on my blog. Any suggestions on how to effectively design a diagram for MLS? For those of you who don't know how MLS works the basic concept is that every process has an "Effective Clearance" (AKA low level) which determines what it can write, it can't write to anything below that because it might have read data from a file at it's own level and it can't read from a level higher than it's own level. MLS also uses a high level for ranged processes and filesystem objects (but that's when it gets really complex).

    This last one is what I consider my most effective diagram. It shows the benefits of SE Linux in confining daemons in a clear and effective manner. Any suggestions for improvement (apart from fixing the varying text size which is due to a bug in Dia) would be appreciated.

    The above diagrams are all on my SE Linux talks page, along with the Dia files that were used to create them. They may be used freely for non-commercial purposes.

    If anyone has some SE Linux diagrams that they would like to share then please let me know, either through a blog comment, email, or a blog post syndicated on Planet SE Linux.

    Evan Prodromou: 21 Germinal CCXV

    Amita June's name for the Teletubbies? "Tummy monkeys." She's a genius. tags:

    11 April 2007

    Daniel Burrows: Wikipedia is case-sensitive, who'da thunk?

    This is part of my ongoing series of posts wherein I am the last person on the planet to discover various things. (this is not a planned series, it's just how life is. :) )

    If I ask Wikipedia about Virtual Server, I get an article about a Microsoft Hproduct. If I ask it about Virtual server, I get a page on server virtualization. Presumably if you know enough Wiki-lore, this makes sense.

    Unsurprisingly, neither article gives me a clue about how I might go about renting a virtual server to avoid the hassle of maintaining hardware or which providers (if any) are reasonably trustworthy.

    Next.

    Previous.