Skip to contentSkip to conversation

wic status

DISCUSSION Maciek Borzecki 6 participants 11 messages Jul 17, 2014 – Jul 18, 2014 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Does this mean that wic is deprecated? If so what is the current method of creating partitioned images?

I'm a bit confused as it seems meta-raspberrypi keeps maitaining
sdcard_image-rpi.bbclass, Freescale has their image_types_fsl.bbclass.
In meta-ti, there was this commit:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=2b524321a25c35c5f987b8331e41b49d3b2e2d2b that effectively removed sdclass_image.bbclass, indicating that wic is the new way.

Signature · 19 lines
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended addressee,
you may neither use this message nor copy or deliver it to anyone. In
such case, you should immediately destroy this message and kindly notify
the sender by reply email. Thank you.
#1 lore raw
Quoted 4 lines · Maciek Borzecki

Hi,

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

I'm not sure where the docs are, but people are responding to bug reports about wic with patches :)

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6513

Philip

Quoted 13 lines

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Does this mean that wic is deprecated? If so what is the current method of creating partitioned images?

I'm a bit confused as it seems meta-raspberrypi keeps maitaining
sdcard_image-rpi.bbclass, Freescale has their image_types_fsl.bbclass.
In meta-ti, there was this commit:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=2b524321a25c35c5f987b8331e41b49d3b2e2d2b that effectively removed sdclass_image.bbclass, indicating that wic is the new way.

#2 lore raw
In reply to Maciek Borzecki
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Thanks,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre

A message that is not in the archive (sent off-list or not yet received): CAFNP8Os559bt59bx6tfqp+R+HyUxz66kaxjuvzBGiRKbdUMjdQ@mail.gmail.com

#4 lore raw
Quoted 10 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 8 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Quoted 5 lines
Quoted 1 line

Scott, can you take a look at this if you haven't already?

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#5 lore raw
Quoted 13 lines · Paul Eggleton
Quoted 12 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 9 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Quoted 9 lines
Quoted 3 lines

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Thanks,

Tom

Quoted 3 lines

Cheers,
Paul

#6 lore raw
In reply to Paul Eggleton
Quoted 13 lines · Paul Eggleton
Quoted 12 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 9 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Quoted 9 lines
Quoted 3 lines

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Thanks,

Tom

Quoted 7 lines

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#7 lore raw
Quoted 28 lines · Tom Zanussi
Quoted 13 lines · Paul Eggleton
Quoted 12 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 9 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Quoted 9 lines
Quoted 3 lines

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

Quoted 5 lines

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Right, I've seen your patches in master, very helpful.

There's one more thing that I'm a bit confused about. The 1.5.2 docs state the following:

<excerpt start>
Here are the actual partition language commands used in the mkefidisk.wks file to generate an image:

# short-description: Create an EFI disk image
# long-description: Creates a partitioned EFI disk image that the
user

     # can directly dd to boot media.
     part /boot --source bootimg --ondisk sda --fstype=efi --label msdos

--active --align 1024
<excerpt end>

I'd assume to find scripts/lib/mic/plugins/source/bootimg.py in the tree, but the file is not there. Have I missed something?

(btw. I'm also assuming that bootimg would prepare a boot partitiong without pushing any particular bootloader, like syslinux or whatever right?)

Signature · 19 lines
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended addressee,
you may neither use this message nor copy or deliver it to anyone. In
such case, you should immediately destroy this message and kindly notify
the sender by reply email. Thank you.
#8 lore raw

So tomorrow I should have an updated version of that wic section in the dora branch of the docs. I will need Tom to look at it. I am making some changes based on the write up I got from that first email thread Tom sent out. Then, based on that copy in the 1.5.x docs, I will get the section into the daisy branch and the master branch. Tom - I will send you a note and link when it is ready for review.

Scott

Quoted 98 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Maciek Borzecki
Sent: Thursday, July 17, 2014 10:39 AM
To: Tom Zanussi
Cc: Paul Eggleton; Scott Rifenbark; [email protected]
Subject: Re: [yocto] wic status

Quoted 6 lines · Tom Zanussi
Quoted 5 lines · Paul Eggleton
Quoted 4 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 2 lines · Paul Eggleton
Quoted 1 line · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in

1.5.2:

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.h
tml

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-

manua

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
Quoted 1 line

l.html

Scott, can you take a look at this if you haven't already?

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never

documented in the 1.6 set.

Quoted 11 lines
Quoted 6 lines

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

Quoted 5 lines

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Right, I've seen your patches in master, very helpful.

There's one more thing that I'm a bit confused about. The 1.5.2 docs state the following:

<excerpt start>
Here are the actual partition language commands used in the mkefidisk.wks file to generate an image:

# short-description: Create an EFI disk image
# long-description: Creates a partitioned EFI disk image that the user # can directly dd to boot media.

part /boot --source bootimg --ondisk sda --fstype=efi --label msdos --active
--align 1024 <excerpt end>

I'd assume to find scripts/lib/mic/plugins/source/bootimg.py in the tree, but the file is not there. Have I missed something?

(btw. I'm also assuming that bootimg would prepare a boot partitiong without pushing any particular bootloader, like syslinux or whatever right?)

--
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged or confidential information and is sent solely for the attention and use of the intended addressee(s). If you are not an intended addressee, you may neither use this message nor copy or deliver it to anyone. In such case, you should immediately destroy this message and kindly notify the sender by reply email. Thank you.

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#9 lore raw
In reply to Maciek Borzecki
Quoted 47 lines · Maciek Borzecki
Quoted 28 lines · Tom Zanussi
Quoted 13 lines · Paul Eggleton
Quoted 12 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 9 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Quoted 9 lines
Quoted 3 lines

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

Quoted 5 lines

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Right, I've seen your patches in master, very helpful.

There's one more thing that I'm a bit confused about. The 1.5.2 docs state the following:

<excerpt start>
Here are the actual partition language commands used in the mkefidisk.wks file to generate an image:

# short-description: Create an EFI disk image
# long-description: Creates a partitioned EFI disk image that the
user

Quoted 9 lines
     # can directly dd to boot media.
     part /boot --source bootimg --ondisk sda --fstype=efi --label msdos

--active --align 1024
<excerpt end>

I'd assume to find scripts/lib/mic/plugins/source/bootimg.py in the tree, but the file is not there. Have I missed something?

Yeah, the documentation is wrong - I need to update it. Previous versions had --source bootimg treated specially and hard-coded the different cases - for --source bootimg, it would look at the --fstype and decide which hard-coded version to use, efi in this case.

Versions after that implemented those cases completely as --source plugins, which you see now as bootimg-efi and bootimg-bios plugins.

Quoted 3 lines

(btw. I'm also assuming that bootimg would prepare a boot partitiong without pushing any particular bootloader, like syslinux or whatever right?)

Right now, those plugins do push specific bootloaders, which so far has been enough for our initial images. You can use --source rootfs to create general-purpose partitions of the supported fstypes including contents needed for bootloaders, but the actual installation of a bootloader would need a plugin containing the logic to do that. With support for more architectures and bootloaders coming online, we may want to provide a more generic mechanism or implementation, but I don't have any specifics in mind at the moment..

Tom

Quoted 24 lines
Signature · 20 lines
-- 
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended addressee,
you may neither use this message nor copy or deliver it to anyone. In
such case, you should immediately destroy this message and kindly notify
the sender by reply email. Thank you.
#10 lore raw
Quoted 70 lines · Tom Zanussi
Quoted 47 lines · Maciek Borzecki
Quoted 28 lines · Tom Zanussi
Quoted 13 lines · Paul Eggleton
Quoted 12 lines · On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
Quoted 9 lines · Paul Eggleton
Quoted 6 lines · On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:

There used to be an entry about wic in development manual back in 1.5.2:
http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

This entry is gone in current documentation and there seems to be no mention of wic at all:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html

Scott, can you take a look at this if you haven't already?

Quoted 9 lines
Quoted 3 lines

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Well, wic is still a part of the system in 1.6 and beyond so we do need to document it; as far as I can tell what was in the 1.5 manual linked above should be perfectly fine and we can just extend / update it as needed. Tom should be able to help fill in any blanks.

Right, wic is still included in the system, and like the rest of the system is undergoing continual development, so I'm not sure why it would be treated differently.

Quoted 5 lines

In any case, to make it easier for users and to avoid a mismatch with external documentation, over the past couple weeks I've submitted a set of patches (which have now been merged) that puts most of the help content into the tool itself, which is all now accessible via 'wic help'.

Right, I've seen your patches in master, very helpful.

There's one more thing that I'm a bit confused about. The 1.5.2 docs state the following:

<excerpt start>
Here are the actual partition language commands used in the mkefidisk.wks file to generate an image:

# short-description: Create an EFI disk image
# long-description: Creates a partitioned EFI disk image that the
user

Quoted 9 lines
     # can directly dd to boot media.
     part /boot --source bootimg --ondisk sda --fstype=efi --label msdos

--active --align 1024
<excerpt end>

I'd assume to find scripts/lib/mic/plugins/source/bootimg.py in the tree, but the file is not there. Have I missed something?

Yeah, the documentation is wrong - I need to update it. Previous versions had --source bootimg treated specially and hard-coded the different cases - for --source bootimg, it would look at the --fstype and decide which hard-coded version to use, efi in this case.

Versions after that implemented those cases completely as --source plugins, which you see now as bootimg-efi and bootimg-bios plugins.

Quoted 3 lines

(btw. I'm also assuming that bootimg would prepare a boot partitiong without pushing any particular bootloader, like syslinux or whatever right?)

Quoted 8 lines

Right now, those plugins do push specific bootloaders, which so far has been enough for our initial images. You can use --source rootfs to create general-purpose partitions of the supported fstypes including contents needed for bootloaders, but the actual installation of a bootloader would need a plugin containing the logic to do that. With support for more architectures and bootloaders coming online, we may want to provide a more generic mechanism or implementation, but I don't have any specifics in mind at the moment..

I've submitted this patch to meta-ti with a source plugin and *.wks for getting wic to build a SD card image for BeagleBone Black:
http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/4171

I guess a more generic solution would actually set BOOTIMG_DIR and fill contents of a directory that would end up as a boot partition. Sounds like something that should be handled by a recipe.

Signature · 19 lines
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended addressee,
you may neither use this message nor copy or deliver it to anyone. In
such case, you should immediately destroy this message and kindly notify
the sender by reply email. Thank you.
#11 lore raw
In reply to a message not in the archive
Quoted 4 lines · Scott Rifenbark

wic was documented in the 1.5.x set and was not put into the 1.6 set. I was told that it was going to change or be further completed so it did not go in that development branch. Wic was never documented in the 1.6 set.

Makes sense now. Thanks.

Quoted 31 lines

Scott

On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton
<[email protected]> wrote:

        On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:
        > There used to be an entry about wic in development manual
        back in 1.5.2:
        >
        http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html
        >
        > This entry is gone in current documentation and there seems
        to be no
        > mention of wic at all:
        >
        https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
        
        Scott, can you take a look at this if you haven't already?
        
        Thanks,
        Paul
        
        --
        
        Paul Eggleton
        Intel Open Source Technology Centre
Signature · 19 lines
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
lub poufne informacje i została wysłana wyłącznie do wiadomości i
użytku osób, do których została zaadresowana. Jeśli wiadomość została
otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do
osób trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej
sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.

This message, including any attachments hereto, may contain privileged
or confidential information and is sent solely for the attention and
use of the intended addressee(s). If you are not an intended addressee,
you may neither use this message nor copy or deliver it to anyone. In
such case, you should immediately destroy this message and kindly notify
the sender by reply email. Thank you.