Public bug reported:

currently we set up linking in /etc/writable during image build for files that 
need atomic writes (on the phone thats only three, on snappy it seems to 
increase a lot). 
doing it from livecd-rootfs is hackish and will bind us forever to that image 
builder (or at least require to move such hacks forward and maintain them in a 
potentially new build system). instead this should be set up from teh initrd 
during boot, after the writable mounts are in place, this is a one time thing 
(should check for existing linkage and just bail out then)

** Affects: snappy
     Importance: Undecided
         Status: New

** Affects: initramfs-tools-ubuntu-core (Ubuntu)
     Importance: Medium
     Assignee: Oliver Grawert (ogra)
         Status: Confirmed

** Affects: livecd-rootfs (Ubuntu)
     Importance: Medium
     Assignee: Oliver Grawert (ogra)
         Status: Confirmed

** Also affects: initramfs-tools-ubuntu-core (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: livecd-rootfs (Ubuntu)
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
   Importance: Undecided => Medium

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
       Status: New => Confirmed

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512361

Title:
  /etc/writable should be handled by the initrd, not by rootfs builds

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1512361/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to