fs/iso9660: allow building a hybrid ISO image
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
This adds an option to build an ISO image using ISOLINUX as a bootloader, as ISOLINUX provides "isohybrid", an utility that enables using an ISO image as a bootable disk image.
--- fs/iso9660/Config.in | 41 ++++++++++++++++++++++++++++++++++++----- fs/iso9660/iso9660.mk | 48 ++++++++++++++++++++++++++++++++++++++++-------- fs/iso9660/isolinux.cfg | 4 ++++ 3 files changed, 80 insertions(+), 13 deletions(-) create mode 100644 fs/iso9660/isolinux.cfg
fs/iso9660/Config.in +36 -5
@@ -3,15 +3,46 @@ config BR2_TARGET_ROOTFS_ISO9660 depends on (BR2_i386 || BR2_x86_64) depends on BR2_LINUX_KERNEL select BR2_TARGET_ROOTFS_CPIO - select BR2_TARGET_GRUB - select BR2_TARGET_GRUB_FS_ISO9660 help Build a bootable iso9660 image -config BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU - string "Boot menu.lst file" +choice + prompt "bootloader" + default BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + depends on BR2_TARGET_ROOTFS_ISO9660 + help + Select the bootloader used on the ISO image + +config BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + bool "isolinux" + select BR2_TARGET_SYSLINUX + select BR2_TARGET_SYSLINUX_ISOLINUX + help + Select this if you want a hybrid ISO, flashable from either an optical + disk or a flash drive. + +config BR2_TARGET_ROOTFS_ISO9660_GRUB + bool "grub" + select BR2_TARGET_GRUB + select BR2_TARGET_GRUB_FS_ISO9660 + +endchoice + +config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + bool "Use a custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660 + +config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG_PATH + string "Path to custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + +config BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIG + string depends on BR2_TARGET_ROOTFS_ISO9660 - default "fs/iso9660/menu.lst" + default $(BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG_PATH) \ + if BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + default "fs/iso9660/isolinux.cfg" if BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + default "fs/iso9660/menu.lst" if BR2_TARGET_ROOTFS_ISO9660_GRUB comment "iso image needs a Linux kernel to be built" depends on BR2_i386 || BR2_x86_64
fs/iso9660/iso9660.mk +40 -8
81 lines not on this page · raw message
fs/iso9660/isolinux.cfg new file +4 -0
@@ -0,0 +1,4 @@ +default 1 +label 1 + kernel /kernel + append initrd=/initrd
Signature · 40 lines
2.1.4 Please ignore the below footer, which is of course irrelevant to this patch. -- *This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by Aldebaran Robotics on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind Aldebaran Robotics to third parties by email, or act on behalf of Aldebaran Robotics by email, without express written confirmation by Aldebaran Robotics? duly authorized representatives.* ------------------------------ *Ce message ?lectronique et ?ventuelles pi?ces jointes sont confidentiels, et exclusivement destin?s ? la personne ou l'entit? ? qui ils sont adress?s.* *Si vous n'?tes pas le destinataire vis?, vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute d?cision sur la foi de ce message ?lectronique. Merci d'en aviser imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles pi?ces jointes de votre syst?me.* *Ce message ?lectronique n'?quivaut pas ? une offre, ? une acceptation d?offre, ou ? un accord d'Aldebaran Robotics sur toute discussion ou document contractuel quel qu?il soit, et ne peut ?tre interpr?t? comme tel. Aucun employ? ou agent d?Aldebaran Robotics n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ? agir au nom et pour le compte de la soci?t? par email, sans qu?une confirmation ?crite soit donn?e par le repr?sentant l?gal d?Aldebaran Robotics ou par toute autre personne ayant re?u d?l?gation de pouvoir appropri?e.*
PATCH 2/3 fs/iso9660: remove obsolete code
This rule is superseded by a rule defined in fs/common.mk:
rootfs-$(1)-show-depends:
@echo $$(ROOTFS_$(2)_DEPENDENCIES)--- fs/iso9660/iso9660.mk | 3 --- 1 file changed, 3 deletions(-)
fs/iso9660/iso9660.mk +0 -3
@@ -77,9 +77,6 @@ endif rootfs-iso9660: $(BINARIES_DIR)/rootfs.iso9660 -rootfs-iso9660-show-depends: - @echo $(ROOTFS_ISO9660_DEPENDENCIES) - ################################################################################ # # Toplevel Makefile options
Signature · 40 lines
2.1.4 Please ignore the below footer, which is of course irrelevant to this patch. -- *This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by Aldebaran Robotics on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind Aldebaran Robotics to third parties by email, or act on behalf of Aldebaran Robotics by email, without express written confirmation by Aldebaran Robotics? duly authorized representatives.* ------------------------------ *Ce message ?lectronique et ?ventuelles pi?ces jointes sont confidentiels, et exclusivement destin?s ? la personne ou l'entit? ? qui ils sont adress?s.* *Si vous n'?tes pas le destinataire vis?, vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute d?cision sur la foi de ce message ?lectronique. Merci d'en aviser imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles pi?ces jointes de votre syst?me.* *Ce message ?lectronique n'?quivaut pas ? une offre, ? une acceptation d?offre, ou ? un accord d'Aldebaran Robotics sur toute discussion ou document contractuel quel qu?il soit, et ne peut ?tre interpr?t? comme tel. Aucun employ? ou agent d?Aldebaran Robotics n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ? agir au nom et pour le compte de la soci?t? par email, sans qu?une confirmation ?crite soit donn?e par le repr?sentant l?gal d?Aldebaran Robotics ou par toute autre personne ayant re?u d?l?gation de pouvoir appropri?e.*
PATCH 2/3 fs/iso9660: remove obsolete code
Dear No? Rubinstein,
Quoted 6 lines · No? Rubinstein
This rule is superseded by a rule defined in
fs/common.mk:rootfs-$(1)-show-depends: @echo $$(ROOTFS_$(2)_DEPENDENCIES)Signed-off-by No? Rubinstein <[email protected]>
No, this is not correct, because iso9660.mk unfortunately does not use the fs/common.mk code. See the comment at the top of the iso9660.mk file:
################################################################################
#
# Build the iso96600 root filesystem image
#
# Cannot be converted to the ROOTFS_TARGET infrastructure, because of
# the temporary construction in ISO9660_TARGET_DIR. # ################################################################################
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 3/3 docs/manual/beyond-buildroot: building and testing live-CDs
In reply to Noé Rubinstein--- docs/manual/beyond-buildroot.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
docs/manual/beyond-buildroot.txt +26 -0
@@ -35,3 +35,29 @@ you should be aware of: * Buildroot does not currently provide +host-qemu+ and +binfmt+ correctly built and set for that kind of use. + +==== Live-CD + +To build a live-CD image, enable _iso image_ in the _Filesystem images_ menu. +(This works only on x86 and x86_64.) + +You can build a live-CD image with either ISOLINUX or Grub as a bootloader, +but only ISOLINUX supports using this image with a live-USB drive. + +You can test your live-CD image using QEMU: + +------------------- +qemu-system-i386 -cdrom output/images/rootfs.iso9660 +------------------- + +Or use it as a hard-drive image if it is an hybrid ISO: + +------------------- +qemu-system-i386 -hda output/images/rootfs.iso9660 +------------------- + +It can be easily flashed to an USB drive with +dd+: + +------------------- +dd if=output/images/rootfs.iso9660 of=/dev/sdb +-------------------
Signature · 40 lines
2.1.4 Please ignore the below footer, which is of course irrelevant to this patch. -- *This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by Aldebaran Robotics on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind Aldebaran Robotics to third parties by email, or act on behalf of Aldebaran Robotics by email, without express written confirmation by Aldebaran Robotics? duly authorized representatives.* ------------------------------ *Ce message ?lectronique et ?ventuelles pi?ces jointes sont confidentiels, et exclusivement destin?s ? la personne ou l'entit? ? qui ils sont adress?s.* *Si vous n'?tes pas le destinataire vis?, vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute d?cision sur la foi de ce message ?lectronique. Merci d'en aviser imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles pi?ces jointes de votre syst?me.* *Ce message ?lectronique n'?quivaut pas ? une offre, ? une acceptation d?offre, ou ? un accord d'Aldebaran Robotics sur toute discussion ou document contractuel quel qu?il soit, et ne peut ?tre interpr?t? comme tel. Aucun employ? ou agent d?Aldebaran Robotics n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ? agir au nom et pour le compte de la soci?t? par email, sans qu?une confirmation ?crite soit donn?e par le repr?sentant l?gal d?Aldebaran Robotics ou par toute autre personne ayant re?u d?l?gation de pouvoir appropri?e.*
PATCH 3/3 docs/manual/beyond-buildroot: building and testing live-CDs
Hi No?,
Quoted 19 lines · No? Rubinstein
Signed-off-by No? Rubinstein <[email protected]>--- docs/manual/beyond-buildroot.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)docs/manual/beyond-buildroot.txt +6
-0@@ -35,3 +35,29 @@ you should be aware of: * Buildroot does not currently provide +host-qemu+ and +binfmt+ correctly built and set for that kind of use. + +==== Live-CD + +To build a live-CD image, enable _iso image_ in the _Filesystem images_ menu. +(This works only on x86 and x86_64.) +
docs/manual/beyond-buildroot.txt you should be aware of: · line 53
Quoted 10 lines
docs/manual/beyond-buildroot.txt +10
-0+You can build a live-CD image with either ISOLINUX or Grub as a bootloader, +but only ISOLINUX supports using this image with a live-USB drive. + +You can test your live-CD image using QEMU: + +------------------- +qemu-system-i386 -cdrom output/images/rootfs.iso9660 +------------------- + +Or use it as a hard-drive image if it is an hybrid ISO:
an hybrid --> a hybrid
docs/manual/beyond-buildroot.txt you should be aware of: · line 59
Quoted 6 lines
docs/manual/beyond-buildroot.txt +6
-0+ +------------------- +qemu-system-i386 -hda output/images/rootfs.iso9660 +------------------- + +It can be easily flashed to an USB drive with +dd+:
an USB --> a USB
Best regards,
Thomas
PATCH 3/3 docs/manual/beyond-buildroot: building and testing live-CDs
In reply to Noé RubinsteinDear No? Rubinstein,
Quoted 4 lines · No? Rubinstein
Signed-off-by No? Rubinstein <[email protected]>--- docs/manual/beyond-buildroot.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
I've reworded a little bit, mentioned that we supported Grub 2, made it explicit that there is an option to get the Hybrid image functionality, and applied.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
In reply to Noé RubinsteinHi No?,
Quoted 5 lines · No? Rubinstein
This adds an option to build an ISO image using ISOLINUX as a bootloader, as ISOLINUX provides "isohybrid", an utility that enables using an ISO image as a bootable disk image.
Signed-off-by No? Rubinstein <[email protected]>
Thanks for your contribution! Some comments below...
Quoted 37 lines
--- fs/iso9660/Config.in | 41 ++++++++++++++++++++++++++++++++++++----- fs/iso9660/iso9660.mk | 48 ++++++++++++++++++++++++++++++++++++++++-------- fs/iso9660/isolinux.cfg | 4 ++++ 3 files changed, 80 insertions(+), 13 deletions(-) create mode 100644 fs/iso9660/isolinux.cfgfs/iso9660/Config.in +15
-4@@ -3,15 +3,46 @@ config BR2_TARGET_ROOTFS_ISO9660 depends on (BR2_i386 || BR2_x86_64) depends on BR2_LINUX_KERNEL select BR2_TARGET_ROOTFS_CPIO - select BR2_TARGET_GRUB - select BR2_TARGET_GRUB_FS_ISO9660 help Build a bootable iso9660 image -config BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU - string "Boot menu.lst file" +choice + prompt "bootloader" + default BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + depends on BR2_TARGET_ROOTFS_ISO9660 + help + Select the bootloader used on the ISO image + +config BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + bool "isolinux" + select BR2_TARGET_SYSLINUX + select BR2_TARGET_SYSLINUX_ISOLINUX + help + Select this if you want a hybrid ISO, flashable from either an optical + disk or a flash drive. +
fs/iso9660/Config.in config BR2_TARGET_ROOTFS_ISO9660 · line 33
Quoted 10 lines
fs/iso9660/Config.in +10
-0+config BR2_TARGET_ROOTFS_ISO9660_GRUB + bool "grub" + select BR2_TARGET_GRUB + select BR2_TARGET_GRUB_FS_ISO9660 + +endchoice + +config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + bool "Use a custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660
There should be some help text on this option: what is the format of the config file, what is the default one, ... ?
Quoted 21 lines
fs/iso9660/Config.in +11
-1+ +config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG_PATH + string "Path to custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + +config BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIG + string depends on BR2_TARGET_ROOTFS_ISO9660 - default "fs/iso9660/menu.lst" + default $(BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG_PATH) \ + if BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + default "fs/iso9660/isolinux.cfg" if BR2_TARGET_ROOTFS_ISO9660_ISOLINUX + default "fs/iso9660/menu.lst" if BR2_TARGET_ROOTFS_ISO9660_GRUB comment "iso image needs a Linux kernel to be built" depends on BR2_i386 || BR2_x86_64fs/iso9660/iso9660.mk +0
-0
fs/iso9660/iso9660.mk line 12
Quoted 6 lines
fs/iso9660/iso9660.mk +2
-1@@ -8,41 +8,73 @@ ################################################################################ ISO9660_TARGET_DIR = $(BUILD_DIR)/iso9660 -ISO9660_BOOT_MENU := $(call qstrip,$(BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU)) +ROOTFS_ISO9660_DEPENDENCIES = host-cdrkit host-fakeroot linux rootfs-cpio +$(info BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIG: $(BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIG))
This $(info) call should be removed.
Best regards,
Thomas
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
Hi Thomas, thanks for your review.
2015-02-02 21:39 GMT+01:00 Thomas De Schampheleire <[email protected]>:
Quoted 6 lines
fs/iso9660/Config.in config BR2_TARGET_ROOTFS_ISO9660 · line 33
Quoted 3 lines
fs/iso9660/Config.in +3
-0+config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + bool "Use a custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660There should be some help text on this option: what is the format of the config file, what is the default one, ... ?
This is a bool option, and when toggled it shows option BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIG which has a visible default value. Should I add a link to
http://www.syslinux.org/wiki/index.php/Isolinux.cfg and
http://www.gnu.org/software/grub/manual/html_node/Configuration.html ?
Signature · 31 lines
*This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by Aldebaran Robotics on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind Aldebaran Robotics to third parties by email, or act on behalf of Aldebaran Robotics by email, without express written confirmation by Aldebaran Robotics? duly authorized representatives.* ------------------------------ *Ce message ?lectronique et ?ventuelles pi?ces jointes sont confidentiels, et exclusivement destin?s ? la personne ou l'entit? ? qui ils sont adress?s.* *Si vous n'?tes pas le destinataire vis?, vous ?tes pri? de ne pas divulguer, copier, distribuer ou prendre toute d?cision sur la foi de ce message ?lectronique. Merci d'en aviser imm?diatement l'exp?diteur et de supprimer toutes les copies et ?ventuelles pi?ces jointes de votre syst?me.* *Ce message ?lectronique n'?quivaut pas ? une offre, ? une acceptation d?offre, ou ? un accord d'Aldebaran Robotics sur toute discussion ou document contractuel quel qu?il soit, et ne peut ?tre interpr?t? comme tel. Aucun employ? ou agent d?Aldebaran Robotics n'est autoris? ? repr?senter ou ? engager la soci?t? par email, ou ? agir au nom et pour le compte de la soci?t? par email, sans qu?une confirmation ?crite soit donn?e par le repr?sentant l?gal d?Aldebaran Robotics ou par toute autre personne ayant re?u d?l?gation de pouvoir appropri?e.*
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
Hi No?,
Quoted 7 lines · No? RUBINSTEIN
Hi Thomas, thanks for your review.
2015-02-02 21:39 GMT+01:00 Thomas De Schampheleire <[email protected]>:
Quoted 4 lines
Quoted 3 lines
fs/iso9660/Config.in +3
-0+config BR2_TARGET_ROOTFS_ISO9660_CUSTOM_BOOT_CONFIG + bool "Use a custom boot config file" + depends on BR2_TARGET_ROOTFS_ISO9660
Quoted 8 lines
Quoted 2 lines
There should be some help text on this option: what is the format of the config file, what is the default one, ... ?
This is a bool option, and when toggled it shows option
BR2_TARGET_ROOTFS_ISO9660_BOOT_CONFIGwhich has a visible default value. Should I add a link to
http://www.syslinux.org/wiki/index.php/Isolinux.cfg and
http://www.gnu.org/software/grub/manual/html_node/Configuration.html ?
Yes, that could be a good idea, along with some short explanation on why a user would want this option, and what the default config file does...
Thanks,
Thomas
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
In reply to Noé RubinsteinQuoted 5 lines · No? Rubinstein
This adds an option to build an ISO image using ISOLINUX as a bootloader, as ISOLINUX provides "isohybrid", an utility that enables using an ISO image as a bootable disk image.
Signed-off-by No? Rubinstein <[email protected]>
Hi No?,
While you're working on this, there is something else that you may be
interested in doing.
Currently, the iso image that is generated is not really the root filesystem,
but it contains a cpio image with the real root filesystem. But in fact, there is no good reason to work that way, and it really complicates the build. Instead, it would be a lot more logical to create a real iso9660 root filesystem using the RockRidge extensions.
That would also allow the iso9660 fs to finally use the ROOTFS_TARGET
infrastructure, removing a lot of cruft.
If you're willing to work on this, you can add it as an additional patch to
your series. It's very likely that it will need a couple of review cycles, so be prepared for that :-)
Regards,
Arnout
[snip]
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH 1/3 fs/iso9660: allow building a hybrid ISO image
Quoted 18 lines · Arnout Vandecappelle
Quoted 5 lines · No? Rubinstein
This adds an option to build an ISO image using ISOLINUX as a bootloader, as ISOLINUX provides "isohybrid", an utility that enables using an ISO image as a bootable disk image.
Signed-off-by No? Rubinstein <[email protected]>Hi No?,
While you're working on this, there is something else that you may be
interested in doing.Currently, the iso image that is generated is not really the root filesystem,
but it contains a cpio image with the real root filesystem. But in fact, there is no good reason to work that way, and it really complicates the build. Instead, it would be a lot more logical to create a real iso9660 root filesystem using the RockRidge extensions.
Quoted 7 lines
That would also allow the iso9660 fs to finally use the
ROOTFS_TARGET
infrastructure, removing a lot of cruft.If you're willing to work on this, you can add it as an additional patch to
your series. It's very likely that it will need a couple of review cycles, so be prepared for that :-)
By the way, take a look at these two very old patches by Jerome Sagnole:
http://patchwork.ozlabs.org/patch/328051/
http://patchwork.ozlabs.org/patch/328052/
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F