rootfs_rpm: Fix bug 936

From: Xiaofeng Yan <[email protected]>

"update-alternatives" installed: one in /usr/sbin from chkconfig (symlinked to "alternatives"), and the other in /usr/bin from update-alternatives-cworth. It appears for whatever reason that the one from chkconfig is run during postinst processing but if you run the script from the command line it gets the other one; this is due to differences in the PATH environment variable.

The following is the sequence to call scripts after kernel booting
inittab
-->rcS
-->./S40networking(PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin) -->S98configure(call rpm-postinstall)
#"/usr/sbin" is found prior to "/usr/bin", so update-alternatives from chkconfig is run in this script
-->rc5.d
-->profile(profile:4:PATH="/usr/local/bin:/usr/bin:/bin"
profile:15: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin)
#"/usr/bin/" is found prior to "/usr/sbin", so update-alternatives from update-alternatives-cworth is run in this script

So I remove the symlink for solving this problem.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/rootfs_rpm
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/rootfs_rpm

Thanks,
Xiaofeng Yan <[email protected]>
---

Xiaofeng Yan (1):
rootfs_rpm: Fix bug 936

 .../recipes-extended/chkconfig/chkconfig_1.3.52.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

From: Xiaofeng Yan <[email protected]>

[YOCTO #936]
"update-alternatives" installed: one in /usr/sbin from chkconfig \
(symlinked to "alternatives"), and the other in /usr/bin \
from update-alternatives-cworth.
It appears for whatever reason that the one from chkconfig is run \
during postinst processing but if you run the script from the command \
line it gets the other one.
this is due to differences in the PATH environment variable.

The following is the sequence to call scripts after kernel booting inittab
-->rcS

     -->./S40networking(PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin)
     -->S98configure(call rpm-postinstall)
        #"/usr/sbin" is found prior to "/usr/bin", so update-alternatives from chkconfig is run in this script

-->rc5.d
-->profile(profile:4:PATH="/usr/local/bin:/usr/bin:/bin" profile:15: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin) #"/usr/bin/" is found prior to "/usr/sbin", so update-alternatives from update-alternatives-cworth is run in this script

So I remove the symlink (update-alternatives linked to chkconfig). The one from update-alternatives-cworth is left alone.

---
 .../recipes-extended/chkconfig/chkconfig_1.3.52.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

index 659f964..6dc8a0e 100644
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=5574c6965ae5f583e55880e397fbb018"
 
 DEPENDS = "libnewt popt"
 
-PR = "r0"
+PR = "r1"
 
 SRC_URI = "http://fedorahosted.org/releases/c/h/chkconfig/${BPN}-${PV}.tar.bz2"
 

@@ -23,4 +23,5 @@ inherit autotools gettext
 
 do_install_append() {
     mkdir -p ${D}/etc/chkconfig.d
+    rm -f ${D}/usr/sbin/update-alternatives
 }

1.7.0.4

Hello,

I was looking at the udev recipes and noticed that there is minor difference between oe-core and meta-oe recipes. I went through logs but could not find the reason. The difference is meta-oe recipe is creating extra files

touch ${D}${sysconfdir}/udev/saved.uname
touch ${D}${sysconfdir}/udev/saved.cmdline
touch ${D}${sysconfdir}/udev/saved.devices
touch ${D}${sysconfdir}/udev/saved.atags

which is used in init and cache script. But oe-core is not creating such files and cache script does not exist in oe-core udev and init script is totally different. Secondly meta-oe udev is copying modprob rules and touchscreen rules but oe-core udev recipe is not doing that. Can anybody explain to me that why there is such differences. Thanks.

Regards,
Noor

Hi,

Kindly explain this difference to me. Thanks.

Regards,
Noor

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Ahsan, Noor
Sent: Wednesday, August 10, 2011 3:12 PM
To: [email protected]
Subject: [OE-core] difference between udev recipes of meta-oe and oe-core

Hello,

I was looking at the udev recipes and noticed that there is minor difference between oe-core and meta-oe recipes. I went through logs but could not find the reason. The difference is meta-oe recipe is creating extra files

touch ${D}${sysconfdir}/udev/saved.uname
touch ${D}${sysconfdir}/udev/saved.cmdline
touch ${D}${sysconfdir}/udev/saved.devices
touch ${D}${sysconfdir}/udev/saved.atags

which is used in init and cache script. But oe-core is not creating such files and cache script does not exist in oe-core udev and init script is totally different. Secondly meta-oe udev is copying modprob rules and touchscreen rules but oe-core udev recipe is not doing that. Can anybody explain to me that why there is such differences. Thanks.

Regards,
Noor

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core