Running script after installation (postinst)
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a pkg_postinst function.
This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
Thanks in advance for any help !
Patrick
DESCRIPTION = "System modifications needed for System"
LICENSE = "MIT"LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302" PACKAGE_ARCH = "${MACHINE_ARCH}"ALLOW_EMPTY = "1"
PR = "r5"
RDEPENDS = "\
rpm \
"pkg_postinst_task-system-tweaks () {
#!/bin/sh -e
#Mount tmprecovery at startup
mkdir -p /tmprecovery
mkdir -p /data
echo "/dev/mtdblock6 /tmprecovery yaffs2 0 0" >>/etc/fstab
echo "/dev/mtdblock7 /data yaffs2 noauto 0 0"
Quoted 1 line
Quoted 1 line
/etc/fstab
}
Hi,
Quoted 9 lines · Patrick
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a
pkg_postinstfunction.This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
It will be run both times (often postinst scripts have to be run on the actual HW). You can chose when your code takes effect by testing the $D variable; when it is set, your script is being run during the rootfs creation, when it is unset, it is being run on the first boot. There are many examples of this in the Yocto recipes.
Your particular script will not work as is at rootfs time, since it is trying to modify '/etc', which at that point is the host /etc directory.
Tomas
Quoted 6 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a
pkg_postinstfunction.
Quoted 7 lines
This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable (note, $D, not ${D}). For example, you could therefore do:
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e
#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6 /tmprecovery yaffs2 0 0" >> $D/etc/fstab echo "/dev/mtdblock7 /data yaffs2 noauto 0 0" >> $D/etc/fstab
Cheers,
Richard
Quoted 31 lines · Richard Purdie
Quoted 6 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a
pkg_postinstfunction.Quoted 7 lines
This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable (note, $D, not ${D}). For example, you could therefore do:
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6/tmprecovery yaffs2 0 0">> $D/etc/fstab
echo "/dev/mtdblock7/data yaffs2 noauto 0 0">> $D/etc/fstab
Quoted 4 lines
Cheers,
Richard
Thanks for your answer
The problems when using $D is that the script is executed against the files of the package not against the whole rootfs. For example in the dummy recipes above we change the file $D/etc/fstab that is not in the package of the recipes.
We have also tried to add (R)DEPENDS to the package that contains fstab with no change.
Any idea why ?
Patrick
Quoted 33 lines · Patrick
Quoted 22 lines · Richard Purdie
Quoted 6 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a
pkg_postinstfunction.Quoted 7 lines
This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable (note, $D, not ${D}). For example, you could therefore do:
Quoted 9 lines
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6/tmprecovery yaffs2 0 0">> $D/etc/fstab
echo "/dev/mtdblock7/data yaffs2 noauto 0 0">> $D/etc/fstab
Quoted 4 lines
The problems when using $D is that the script is executed against the files of the package not against the whole rootfs. For example in the dummy recipes above we change the file $D/etc/fstab that is not in the package of the recipes.
If you reference $D as part of a postinst script, it will run against the files of the rootfs, not just the package. There are some problems ensuring dependencies are present when this happens though, some backends like rpm don't like ensuring that dependencies are present.
Quoted 4 lines
We have also tried to add (R)DEPENDS to the package that contains fstab with no change.
Any idea why ?
You would need to add the dependency in and then it sounds like you're probably using rpm and it doesn't want to honour the dependency for some reason. You could add a rootfs post process command to add in what you need which would guarantee all the files are present first...
Cheers,
Richard
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 55 lines · Patrick
Quoted 47 lines · Richard Purdie
Quoted 33 lines · Patrick
Quoted 22 lines · Richard Purdie
Quoted 6 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we have added a
pkg_postinstfunction.Quoted 7 lines
This doesn’t work properly as the script is executed at first start-up and not after installation. Below are an example of this recipe.
Do you have any idea why this script is started as first boot time and not after installation ?
Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable (note, $D, not ${D}). For example, you could therefore do:
Quoted 9 lines
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6/tmprecovery yaffs2 0 0">> $D/etc/fstab echo "/dev/mtdblock7/data yaffs2 noauto 0 0">> $D/etc/fstabQuoted 4 lines
The problems when using $D is that the script is executed against the files of the package not against the whole rootfs. For example in the dummy recipes above we change the file $D/etc/fstab that is not in the package of the recipes.
If you reference $D as part of a postinst script, it will run against the files of the rootfs, not just the package. There are some problems ensuring dependencies are present when this happens though, some backends like rpm don't like ensuring that dependencies are present.
Quoted 3 lines
We have also tried to add (R)DEPENDS to the package that contains fstab with no change.
Quoted 6 lines
Quoted 1 line
Any idea why ?
You would need to add the dependency in and then it sounds like you're probably using rpm and it doesn't want to honour the dependency for some reason. You could add a rootfs post process command to add in what you need which would guarantee all the files are present first...
Quoted 5 lines
That's a good idea ! What would be the correct function name ? Something like
do_rootfs_append()?
In this case do we have to prefix all the path with ${IMAGE_ROOTFS} ?Patrick
I reply myself:
as suggested above, using do_rootfs_append() and ${IMAGE_ROOTFS} it works nicely !
Thanks to all for your help
Patrick
Quoted 64 lines · Patrick
Quoted 63 lines · Patrick
Quoted 51 lines · Richard Purdie
Quoted 37 lines · Patrick
Quoted 26 lines · Richard Purdie
Quoted 11 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we
have added apkg_postinstfunction.This doesn’t work properly as the script is executed at first start-up
and not after installation. Below are an example of this recipe.Quoted 5 lines
Do you have any idea why this script is started as first boot time and
not after installation ?Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable
(note, $D, not ${D}). For example, you could therefore do:Quoted 9 lines
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6/tmprecovery yaffs2 0 0">> $D/etc/fstab echo "/dev/mtdblock7/data yaffs2 noauto 0 0">> $D/etc/fstabQuoted 4 lines
The problems when using $D is that the script is executed against the files of the package not against the whole rootfs. For example in the dummy recipes above we change the file $D/etc/fstab that is not in the package of the recipes.
If you reference $D as part of a postinst script, it will run against the files of the rootfs, not just the package. There are some problems ensuring dependencies are present when this happens though, some backends like rpm don't like ensuring that dependencies are present.
Quoted 3 lines
We have also tried to add (R)DEPENDS to the package that contains fstab with no change.
Quoted 6 lines
Quoted 1 line
Any idea why ?
You would need to add the dependency in and then it sounds like you're probably using rpm and it doesn't want to honour the dependency for some reason. You could add a rootfs post process command to add in what you need which would guarantee all the files are present first...
That's a good idea ! What would be the correct function name ? Something like
do_rootfs_append()?
In this case do we have to prefix all the path with ${IMAGE_ROOTFS} ?
Quoted 6 lines
Quoted 1 line
Patrick
I reply myself:
as suggested above, usingdo_rootfs_append()and ${IMAGE_ROOTFS} it works nicely !
Argh, in fact it doesn't work. The script is executed against right files but *after* packaging everything into a single image... The script should be executed just before packaging of the image.
Any idea how to do that ?
Quoted 74 lines · Patrick
Quoted 66 lines · Patrick
Quoted 65 lines · Patrick
Quoted 52 lines · Richard Purdie
Quoted 37 lines · Patrick
Quoted 26 lines · Richard Purdie
Quoted 11 lines · Patrick
Dear all,
In one of our recipes we need to execute a small script after the installation of the package. Following yocto dev manual point 4.3.6 we
have added apkg_postinstfunction.This doesn’t work properly as the script is executed at first start-up
and not after installation. Below are an example of this recipe.Quoted 5 lines
Do you have any idea why this script is started as first boot time and
not after installation ?Thanks in advance for any help !
We try and run postinstalls "offline" at image creation time. If they fail, they run at first boot.
You can tell which context you're in by the contents of the $D variable
(note, $D, not ${D}). For example, you could therefore do:Quoted 9 lines
pkg_postinst_task-system-tweaks () {
#!/bin/sh -e#Mount tmprecovery at startup
mkdir -p $D/tmprecovery
mkdir -p $D/data
echo "/dev/mtdblock6/tmprecovery yaffs2 0 0">> $D/etc/fstab echo "/dev/mtdblock7/data yaffs2 noauto 0 0">> $D/etc/fstabQuoted 4 lines
The problems when using $D is that the script is executed against the files of the package not against the whole rootfs. For example in the dummy recipes above we change the file $D/etc/fstab that is not in the package of the recipes.
If you reference $D as part of a postinst script, it will run against the files of the rootfs, not just the package. There are some problems ensuring dependencies are present when this happens though, some backends like rpm don't like ensuring that dependencies are present.
Quoted 4 lines
We have also tried to add (R)DEPENDS to the package that contains fstab
with no change.Quoted 7 lines
Quoted 1 line
Any idea why ?
You would need to add the dependency in and then it sounds like you're probably using rpm and it doesn't want to honour the dependency for some
reason. You could add a rootfs post process command to add in what you need which would guarantee all the files are present first...That's a good idea ! What would be the correct function name ? Something like
do_rootfs_append()?
In this case do we have to prefix all the path with ${IMAGE_ROOTFS} ?Quoted 6 lines
Quoted 1 line
Patrick
I reply myself:
as suggested above, usingdo_rootfs_append()and ${IMAGE_ROOTFS} it works nicely !
Quoted 6 lines
Argh, in fact it doesn't work. The script is executed against right files but *after* packaging everything into a single image... The script should be executed just before packaging of the image.
Any idea how to do that ?
I reply myself, it works with rootfs_rpm_do_rootfs_append instead of using do_rootfs_append but I don't know if it's the best way to do. If you know more recommended way to do feel free to comment here !
Patrick
Quoted 19 lines · Patrick
Quoted 11 lines · Patrick
Quoted 10 lines · Patrick
Quoted 4 lines · Richard Purdie
You would need to add the dependency in and then it sounds like you're probably using rpm and it doesn't want to honour the dependency for some reason. You could add a rootfs post process command to add in what you need which would guarantee all the files are present first...
That's a good idea ! What would be the correct function name ? Something like
do_rootfs_append()?
In this case do we have to prefix all the path with ${IMAGE_ROOTFS} ?Quoted 6 lines
Quoted 1 line
Patrick
I reply myself:
as suggested above, usingdo_rootfs_append()and ${IMAGE_ROOTFS} it works nicely !
Quoted 5 lines
Argh, in fact it doesn't work. The script is executed against right files but *after* packaging everything into a single image... The script should be executed just before packaging of the image.
Any idea how to do that ?
ROOTFS_POSTPROCESS_COMMAND is probably what you're looking for.
Cheers,
Richard