<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>2350</bug_id>
          
          <creation_ts>2012-04-19 19:23:28 +0000</creation_ts>
          <short_desc>init-live-boot: CONFIG_UNION_FS changes not updated in init-live.sh</short_desc>
          <delta_ts>2012-04-22 14:36:01 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>2256</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tom Zanussi">tom.zanussi</reporter>
          <assigned_to name="Yang Shi">yang.shi</assigned_to>
          <cc>bruce.ashfield</cc>
    
    <cc>dvhart</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>yang.shi</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>20733</commentid>
    <comment_count>0</comment_count>
    <who name="Tom Zanussi">tom.zanussi</who>
    <bug_when>2012-04-19 19:23:28 +0000</bug_when>
    <thetext>If you turn off CONFIG_UNION_FS in the kernel, the init-live.sh doesn&apos;t get updated with UNIONFS=&quot;no&quot;, so the init script that gets installed still has the old UNIONFS=&quot;yes&quot; setting and mounts unionfs, etc, which results in an unbootable system.

The workaround is to just force init-live-boot to be rebuilt after the kernel config change.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20736</commentid>
    <comment_count>1</comment_count>
    <who name="Yang Shi">yang.shi</who>
    <bug_when>2012-04-19 20:16:33 +0000</bug_when>
    <thetext>So, this is why we add virtual/kernel depend for initramfs-live-boot.

diff --git a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
index e85a0e1..f7f0c9d 100644
--- a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
@@ -2,10 +2,17 @@ DESCRIPTION = &quot;A live image init script&quot;
 LICENSE = &quot;MIT&quot;
 LIC_FILES_CHKSUM = &quot;file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420&quot;
 RDEPENDS = &quot;udev&quot;
+DEPENDS = &quot;virtual/kernel&quot;
 SRC_URI = &quot;file://init-live.sh&quot;

When I did the test, I found I need clean initramfs-live-boot, then rebuild it once kernel config is changed, it can&apos;t be rebuilt automatically.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20741</commentid>
    <comment_count>2</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-04-19 23:16:21 +0000</bug_when>
    <thetext>Because the kernel config is in the linux-yocto/meta, bitbake won&apos;t detect the change unless the SRCREV is updated. If the SRCREV was updated and initramfs-live-boot doesn&apos;t rebuild automatically, then I think we have a bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20742</commentid>
    <comment_count>3</comment_count>
    <who name="Yang Shi">yang.shi</who>
    <bug_when>2012-04-19 23:22:14 +0000</bug_when>
    <thetext>In this usecase, I don&apos;t think changing of SRCREV is involved. The changing to kernel config is just to temporarily disable a kernel config (here it is CONFIG_UNION_FS) via &quot;bitbake -c menuconfig linux-yocto&quot;, then rebuild kernel.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20745</commentid>
    <comment_count>4</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-04-19 23:28:36 +0000</bug_when>
    <thetext>Bug 2256 might be related.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20746</commentid>
    <comment_count>5</comment_count>
    <who name="Yang Shi">yang.shi</who>
    <bug_when>2012-04-19 23:36:22 +0000</bug_when>
    <thetext>If we rebuild kernel via the steps suggested in Bug #2256, will or should any package which depends on virtual/kernel be rebuilt automatically?

In my understanding, this should be expected.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20759</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-04-20 03:53:08 +0000</bug_when>
    <thetext>This definitely looks to be the same as 2256 to me.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20800</commentid>
    <comment_count>7</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2012-04-22 14:36:01 +0000</bug_when>
    <thetext>I&apos;ve tested this and if the sstate checksum of the kernel changes, the script does rebuild. So if you change the kernel SRCREV or add a fragment to SRC_URI it will notice and update.

Even if we fix 2256 so sstate isn&apos;t reused, we&apos;re still going to have to be careful with this since its possible to change the kernel config manually but not change the sstate checksum. At that point the user should really know what they&apos;re doing though and I&apos;m not sure there is much we can realistically do.

I think the only option will be to shows users a big warning when they use menuconfig that the dependencies of the kernel will not rebuild automatically, they&apos;re doing something outside the normal system and are on their own.

*** This bug has been marked as a duplicate of bug 2256 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>