Sylvain Le Gall: OCaml meeting 2008 participants
Unfortunately I forget to post the last year participant pictures. Here is the official picture.
Unfortunately I forget to post the last year participant pictures. Here is the official picture.
Since September 2008, Alan Schmitt and I have decided to organize a new OCaml Meeting following the JFLA. This will be the second time of such an event. Last year we were 50 people -- after a very short period for organizing it (less than a month). This year we decided to prepare things earlier.
As a matter of fact, the last year events has at least generated a peak in OCaml mailing list (602 message in January, 487 in february...) It also has given birth to several things like planet and forge. It has also help to start things like batteries. I hope this year events will help people to meet and exchange great ideas for OCaml promotion.
Waiting to see a lot of "OCaml"ers at OCaml Meeting 2009.
I spent much of this week in Alicante. It was wonderful to have a
few days away from the beginnings of Winter in Cambridge - Alicante's
in South West Spain, right on the Mediterranean. It's a lovely city,
although it was very quiet due to the time of year.
I was invited down to Alicante by organisers of the Congr s de Programari Lliure,
Comunitat Valenciana, to present a talk about Debian. That I did,
and as always my slides
and photos
are available in case people are interested. I wasn't too sure about
what level to aim the talk, so I deliberately went for a general
introduction to Debian. That seems to have been the correct level -
nobody threw anything at me, and nobody was visibly falling
asleep. *grin* It's also the first time I've ever given a talk with
official translators, which is a weird experience! The main topic for
the conference was the new release of Lliurex, Valencia's own GNU/Linux
distribution targeted primarily at use in schools.
The conference was massive; I was told there were about 1500
attendees in all, most of whom were teachers who wanted to come and
learn more about Free Software. There was a good spread of talks and
workshops, covering topics from development through to deployment in
the classroom. The level of enthusiasm for Free Software here was
immense - lots of people were keen to learn more about it and get
involved. I was told that out of the 15 regions/states of Spain, 11 of
them have now started their own distributions to use in schools!
Extremadura were the first region to experiment with Free Software
like this, and their success with LinEx was a clear inspiration to
their neighbours elsewhere in Spain. As well as the obvious cost
advantages of moving from proprietary to Free Software, the local
governments also love the freedom to use and modify their software
however they like - including the ability to provide their own
translations.
I met up with a lot of cool people at the conference too. The local
education minister (Alejandro Font de Mora) was keen to talk with all
the speakers and very enthusiastic about the future of Free Software
in his schools. As is increasingly common at FS events around the
world, there were of course quite a few Debian people around too.
Luciano and Miriam were also giving talks, and I bumped into Rene and
Miguel and a whole bunch of others whose names I'm too crap to
remember - sorry! I also spoke a lot with Kurt Gramlich, the
mega-enthusiastic Skolelinux developer who was also happy to push
Debian to everybody he spoke to *grin*. Jon "Maddog" Hall had some
excellent ideas that I'm sure we'll all hear more about soon, and his
talk was excellent. He did a very good job of explaining how Free
Software makes such a difference, including how it helps people to
make money. He also explained that due to travel he had missed
Halloween at home and he wanted to share the experience of scary masks
with the people at the conference:
I had a great time in Alicante, and I'm very grateful for the
invitation to go there. I wish that the UK was as far as advanced as
Spain in the use of Free Software in education - they've done a huge
amount of good work in this area and I'm glad we can help them.
--exclude Packages* --exclude Sources* --exclude Release* --exclude ls-lR*The first stage must not delete any files. The second stage should then transfer the above excluded files and delete files that no longer belong on the mirror. Rationale: If archive mirroring is done in a single stage, there will be periods of time during which the index files will reference files not yet mirrored. And that will lead to a lot of confusion for our users.
Today someone asked me to take a look at an Evolution enhancement that's just begging to get into trunk. Since this is a Gnome program in a subversion repository I've commenced the process of cloning the repository so I can look at the issue against the current head.
At the current rate I should have a copy of the repository by early tomorrow morning, in order to be able to start looking at it. Of course today is when I actually do have some time to spare, and I hope to be fast asleep at the time when I expect this to finish.
Presumably subversion isn't this slow for everyone, but since my latency to their repository is 300mS I'm probably on the worst end the pain, with each commit seemingly taking around a second. It sure would be nice if subversion provided some kind of chunked compression of these five-year-old commits, so I could be bandwidth limited, rather than latency challenged.
The addition of a day to the checkout of a software project must be a significant barrier to entry for anyone considering contributing. It makes it much less likely to be opportunistic.
So far I'm up to r3600 in 75 minutes. That's 75 minutes that I could have spent actually looking at the code, but now it's time for me to go and vote for me...
When I first read http://two.sentenc.es/ in (if I remember correctly) madduck’s
signature, I thought something like “This can’t be! Why are people
castrating themself?”
Although I really understand that the inventor has good reasons for such a personal policy, I notice how much
time I waste by trying to fit all the information I want to transmit
in the 160 characters a short messages allows — or, even worse,
into the 140 characters microblogging services like identi.ca or Twitter allow.
So I had to oppose something to this, but even to only reach the
coolness level of the domain “sentenc.es” is hard, you probably can’t
top it at all. For luck, I’m not alone and Venty had the right idea
for a hostname which has at least some geeky niveau.
So here it is, our pleading for e-mails as long and detailed as
necessary:
http://e-mail.is-not-s.ms/ A German version will be available soon at http://e-mail.ist-nicht-s.ms/. Feel free to add either URL to your e-mail signature. :-) Oh, and thanks to the Government of Montserrat which allows strangers to register .ms domains without any hassles. :-) Update / FAQ Seems to be necessary to make a few things clear…
debian-installer rc1 is going to be officially announced next week.
However, the netboot images are already available. I'm now looking for
people who are interested in testing these installer images on ARM and
MIPS based machines.
If you have a spare ARM or MIPS machine or want to reinstall your
machine for some reason (for example to move from arm to armel), please
see my messages on debian-arm
and debian-mips
for more information.
I've used this opportunity to update all my installation instructions to
lenny. See here for Debian on Linksys NSLU2, Thecus N2100, QNAP Turbo Station, HP mv2120 and
Cobalt.
#include <stdio.h>
#include <stdlib.h>
int main(void)
union
unsigned char raw[8];
struct
char one;
int two;
char three;
char four;
char five;
formatted __attribute__((packed));
test;
printf("one : %d\n", (int)&test.formatted.one - (int)&test);
printf("two : %d\n", (int)&test.formatted.two - (int)&test);
printf("three : %d\n", (int)&test.formatted.three - (int)&test);
printf("four : %d\n", (int)&test.formatted.four - (int)&test);
printf("five : %d\n", (int)&test.formatted.five - (int)&test);
return 0;
$ gcc -Wall -o packing packing.c $ ./packing one : 0 two : 4 three : 8 four : 9 five : 10
For an enum, struct or union type, you may specify attributes either between the enum, struct or union tag and the name of the type, or just past the closing curly brace of the definition. The former syntax is preferred.By getting the packed attribute in the wrong place (if it's not clear, it should be before formatted), it is applied to the variable rather than the type. The compiler (both gcc and icc do this) has already laid out the structure, so misses the packing directive, and unfortunately doesn't warn (that may be a bug?). I can tell you from experience this can be hard to track down!
A lot has been said about the elections already. I just want to share my personal experiences about it. During the weekend, Tom invited us to his place in lower Harlem (we live upper Harlem) on 123rd St and Adam Clayton Powell Jr Ave, for Tuesday night. As Tuesday arrived, we didn’t see too many people too excited about it. Living in Harlem, we were pretty used to black people supporting Obama, so getting closer and closer to the elections, we didn’t feel people anxious. On Tuesday, we commuted to work and some of our co-workers got to work late because they have been standing in lines for a couple of hours to vote in polls. The whole day was about talking on how much that day was representing for the US and the world, guessing how they results were going to end up, etc.
Later at night, Greg, Phil, Raquel and I headed to Tom’s place for his watch-the-results party. His fridge was full of Blue Moon beer, but he also had some Red Stripe
Bash is probably the most common command-line shell in the GNU/Linux world. Although a lot of people use alternate shells (such as Zsh), Bash is still shipped with most mainstream distros as the default. Once you have a lot of different remote machines, all running Bash as the shell, it becomes increasingly difficult to pay attention to the prompt, and typing reboot in a machine different from the one you wanted becomes more likely. I deal with that problem by changing Bash prompts
First of all, the basics: Bash prompts are just environment variables with special characters you can set and export. Bash has four of these variables: PS1 to PS4, but usually only the first two matters (actually, just PS1 for a reference on the others, check the manpage). The most common PS1 string is:
spectra@home:~$ echo $PS1
\u@\h:\w\$
spectra@home:~$
This has 4 special characters, escaped with a backslash: \u informing us the username; \h informing us the hostname; \w, informing us the working directory; and \$, which gives us the $ in the end of the prompt (more on this later).
So, essentially, one can change that string to anything else
spectra@home:~$ PS1="my_shell_prompt\$ "
my_shell_prompt$
Pretty easy. You can check a complete reference of the special characters at the section PROMPTING of bash manpage, but the most useful IMHO are the following:
spectra@hospital:~$ PS1="\[\e[1;33m\]\u\[\e[0m\]@\[\e[0;35m\]\h\[\e[0m\]:\[\e[0;32m\]\w\[\e[0m\]\$ "
spectra@hospital:~$
With \e[0;35m (Purple) for the hostname. On home machine, it may be \e[0;34m (Blue)... On server , it may be \e[0;36m (Cyan), and so on After a while, you get used to the color and end up linking the color to the machine so that typing reboot on a machine with the wrong color gets harder than before.
To make the changes permanent, put export PS1 in one of the config script of bash (.bashrc, .bash_profile, etc). On some systems, /etc/environment holds lots of environment variables definitions.
I just scratched the surface That s just what works for me The Bash-Prompt-HOWTO has some interesting examples, and I actually have a friend who uses more esoterical stuff, such as fancybash or bashish, but I ll leave this up to you
df would say there is (almost) no space left on some device, while du doesn’t see as much data present as you would expect from this situation. This happens when you delete a file that another process has opened (and, obviously, not yet closed).
In typical UNIX filesystems, files are actually only entries in a directory, pointing (linking) to the real information about the content, the inode.
The inode contains the information about how many such links exist on the filesystem, the link count. When you create a hard link (ln without -s), you create another file entry in some directory, linking to the same inode as the “original” file. You also increase the link count for the inode.
Likewise, when removing a file, the entry in the directory is removed (though most of the time, really only skipped, but that’s another story), and the link count decreased. When the link count is zero, usually, the inode is marked as deleted.
Except when the usage count is not zero.
When a process opens a file, the kernel keeps a usage count for the corresponding inode in memory. When some process is reading from a file, it doesn’t really expect it to disappear suddenly. So, as long as the usage count is not null, even when the link count in the inode is zero, the content is kept on the disk and still takes space on the filesystem.
On the other hand, since there is no entry left in any directory linking to the inode, the size for this content can’t be added to du’s total.
Back to our problem, the origin was that someone had to free some space on a 1GB filesystem, and thought a good idea would be to delete that 860MB log file that nobody cares about. Except that it didn’t really remove it, but he didn’t really check.
Later, the “filesystem full” problem came back at someone else, who came to ask me what files from a small list he could remove. But the files were pretty small, and that wouldn’t have freed enough space. That gave me the feeling that we probably were in this typical case I introduced this post with, which du -sk confirmed: 970MB used on the filesystem according to df, but only 110MB worth of data…
Just in case you would need to find the pid of the process having the deleted file still opened, or even better, get access to the file itself, you can use the following command:
find -L /proc/*/fd -type f -links 0
(this works on Linux ; remove -L on recent Solaris ; on other OSes, you can find the pid with lsof)
Each path this command returns can be opened and its content accessed with a program, such as cat. That will give access to the deleted content.
I already adressed how to re-link such a file, which somehow works under Linux, but in my case, all that mattered was to really remove the file, this time. But we didn’t know if it was safe to stop the process still holding the file, nor how to properly restart it. We were left without a possible resolution, but still needed to come up with something before the filesystem gets really full while waiting to be able to deal with the root of the problem.
The first crazy idea I had was to attach a debugger to the process, and use it to close the file descriptor and open a new file instead (I think you can find some examples with google). But there was no debugger installed.
So, I had this other crazy idea: would truncate() work on these /proc/$pid/fd files?
You know what? It does work. So I bought us some time by running:
perl -e 'truncate("/proc/$pid/fd/$fd", 0);'
(somehow, there is no standard executable to do a truncate(), so I always resort to perl)
Afterwards, I also verified the same works under Linux (where you wouldn’t really know what it’d do with these files that are symbolic links to somewhere that doesn’t exist).
The even simpler following command works, too.
> /proc/$pid/fd/$fd
It doesn’t truncate() but open() with O_WRONLY O_CREAT O_TRUNC, and close() right after (to simplify), which has the same effect.
Good to know, isn’t it?
A couple of years ago, I started what has probably been the best job I've held so far, as a Business Development Manager for Artec Group where I focused on marketing and selling the ThinCan LTSP client.
During that time, I used a combination of Guerrilla Marketing techniques to spread the word about this cool Estonian embedded platform in its LTSP client configuration and defined an extremely tight market-oriented focus that saw this relatively obscure electronic design start-up rise to the forefront of the LTSP hardware market and also brought the company commendable notoriety in the Coreboot community, thanks to its Programmable LPC Dongle, a low-cost ROM emulator that can be used to bootstrap various embedded hardware and test firmware images.
Looking back at close to 3 years with Artec (if we include the stint I did at Linutop), I most fondly remember how I managed to bring the Estonian and Turkish nations closer together in collaborating on Innovation. On my first visit to Turkey, I had noticed that very little is know about Estonia in Turkey, even though both countries have a collaboration that dates back to the 1920's, so my tactic was to introduce Estonia's achievements as a whole, to establish confidence in Artec's offering. It worked:
Among other things, my idea to organize an Estonian ICT Conference during the visit of Estonian PM Andrus Ansip in Turkey created a lot of extremely positive buzz that resulted in Estonia being mentioned as a trendy country in a prime time Turkish TV series. During this time, I've also made a lot of contacts among the Estonian and Turkish business communities and, more surprisingly, among the Estonian diplomacy who, much to my amazement, welcomed my ideas for better promoting Estonian interests abroad with great enthusiasm.
Come December 2008, my time at Artec will become a page in my employment history. While the Thincan remains one of Artec's key products, current marketing and sales resources are focused on new markets and new technologies that completely fall outside my core expertise, which is why the company decided to let me go.
I thus welcome offers from interested parties in Coreboot or LTSP markets. Other refreshing offers from outside the box - such as in business diplomacy - are equally welcome, as I've been pondering a career change for a long time.
Note: this is quite long and might not be interesting for people not involved with /in either of: debian i18n, debian l10n, git, shell scripting.
The Open Source Repository and Observatory (OSOR), a new site sponsored
by the European Commission to foster the exchange of FOSS related
information and software among European public administrations, recently
published guidelines
on the procurement of open source software. Public administrations
in Europe have to follow public tender procedures and the new guidelines
give practical and legal advice on how open source software and related
services can be incorporated into the procurement process.
Rishab Ghosh, who presented the guidelines at the Open Source World
Conference in Malaga, argued that the procurement guidelines were needed
because of two reasons. First, they studied recent tenders and found
that many explicitly
mentioned proprietary applications. 16% of 3615 software tenders
explicitly asked for products from top 10 software vendors, such as
Microsoft, SAP and Oracle. This practice may be illegal because public
tenders generally have to describe functional requirements in a general
way instead of specifying specific products. Second, many public
administrations don't have any experience with the procurement of FOSS.
In fact, they often don't know whether or under which circumstances they
are allowed to adopt and ask for FOSS solutions. The guidelines are
specifically designed in order to clearly and simply explain how public
administrations can acquire open source and they don't assume that a
country has adopted a specific policy regarding open source.
The guidelines include a long section about open standards, open source
and how they relate. Both open standards and open source align very
well with the needs of public administrations who have an "obligation to
support interoperability, transparency and flexibility, as well as
economical use of public funds". The guidelines argue that the exit
cost, i.e. the cost incurred in moving to another IT system, is also an
important consideration but one that is often neglected. The adoption
of a proprietary solution without open standards may limit the future
choice, thereby increasing the long-time costs and giving the
proprietary vendor an unfair advantage in future tenders.
The procurement guidelines describe two ways of acquiring FOSS: it is
possible to go the usual route of publishing a tender for the supply of
software (possibly with related services). However, in the case of
FOSS, it is also possible to download the software directly from the
Internet. This is possible because the software is not only free of
charge but comes with no contractual obligations. If there were any
obligations involved with the download (such as fees, the agreement to
an EULA or the requirement to purchase services in the future), software
download is not an allowed method. What I like about the guidelines is
that they explicitly say that downloading software has to be part of the
formal procurement process. You have to think about your requirements,
look at various alternatives, and so on, and not just blindly download
something from the Internet.
When it comes to the procurement of FOSS, the guidelines don't suggest
that tenders should explicitly ask for FOSS. Instead, they should
describe the functional requirements of the software as well as certain
properties. For example, a tender could specify that the public
administration as well as third parties must have the right to study,
distribute and modify the software. In a sense, the guidelines suggest
that tenders should include the principles of the Free Software
Definition along with justifications for these requirements.
Personally, I think there is a great need for these procurement
guidelines. There are many public administrations that don't know how
to acquire FOSS and these guidelines offer clear advice. Furthermore, I
find the guidelines very balanced. They don't recommend that you should
always ask for FOSS but incorporate FOSS principles into tenders where
it makes sense. It remains to be seen whether the procurement
guidelines will have an impact on the FOSS adoption in Europe, but I
surely hope so.
(Originally published on FOSSBazaar)
So, as everyone knows by now, the party which is a lot like our Conservatives won the US elections (instead of the other party which is a lot like our Conservatives). I’m particularly touched by Aq’s comment:-
The mood in America has been likened to the one here in 97 when we managed to kick the conservatives out for the first time in about 20 years, which amuses me. However, the fact that ours failed to live up to that optimism doesn t mean yours necessarily won tOh well, at least it was better than drifting further to the right (in both cases). I’ll wait and see whether it lives up to the optimism. As you may know, SPI is associated with the Open Voting Foundation. That doesn’t sit well with me - while paper voting is imperfect, it seems more verifiable and scalable than machine voting. I’ve been assured that OVF seeks to replace current election machines, rather than spread machine voting to new places and it looks like my area is not under immediate threat (ORG latest news), so I’m not working on it just now. Broadly, I agree with Simon Rumble on Voting machines: a solution searching for a problem?
So without even going into the serious problems with voting machines, it seems they don’t actually solve any actual problems, and I suspect cost a lot more to operateI’m currently finding out more about standing for election to The Cooperative Group committee and ThePhoneCoop board - I’m not sure yet, but I think both still use paper voting. Cooperatives-SW and TTLLP both use in-person voting. What’s the current thinking here? What’s best?
So, as everyone knows by now, the party which is a lot like our Conservatives won the US elections (instead of the other party which is a lot like our Conservatives). I’m particularly touched by Aq’s comment:-
The mood in America has been likened to the one here in 97 when we managed to kick the conservatives out for the first time in about 20 years, which amuses me. However, the fact that ours failed to live up to that optimism doesn t mean yours necessarily won tOh well, at least it was better than drifting further to the right (in both cases). I’ll wait and see whether it lives up to the optimism. As you may know, SPI is associated with the Open Voting Foundation. That doesn’t sit well with me - while paper voting is imperfect, it seems more verifiable and scalable than machine voting. I’ve been assured that OVF seeks to replace current election machines, rather than spread machine voting to new places and it looks like my area is not under immediate threat (ORG latest news), so I’m not working on it just now. Broadly, I agree with Simon Rumble on Voting machines: a solution searching for a problem?
So without even going into the serious problems with voting machines, it seems they don’t actually solve any actual problems, and I suspect cost a lot more to operateI’m currently finding out more about standing for election to The Cooperative Group committee and ThePhoneCoop board - I’m not sure yet, but I think both still use paper voting. Cooperatives-SW and TTLLP both use in-person voting. What’s the current thinking here? What’s best?
Next.