the initamfs-tools-ubuntu-core side as well as livecd-rootfs changes have
landed for this
if we want to go with split-initrd from thw bootloader only the snappy task
remains
** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
Status: New => Fix Released
** Changed in: initramfs-tools-ub
** Changed in: snappy
Status: New => Triaged
** Changed in: snappy
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490115
Title:
build a fully generic ini
"I don't understand the disconnect here. The only reason for putting kernel
modules in an initramfs is if they're needed to access the rootfs."
correct, except this should read "any rootfs" ... we ship all possible
filesystem modules as well as all network card modules (for possible
netboot) etc .
On Sun, Aug 30, 2015 at 08:43:23AM -, Oliver Grawert wrote:
> would the concaternating approach allow the move mount when switching to
> the rootfs ?
I'm afraid I don't know the answer to this. I'm aware this functionality
exists in the kernel but we've never used it in practice.
> i don't u
hmm, and re-reading all the above, i actually meant system-boot
everywhere i wrote /boot indeed (i.e. the partition that gets later
mounted under /boot/$bootloader/ ), not the /boot directory/mountpoint
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
would the concaternating approach allow the move mount when switching to the
rootfs ?
our readonly filesystems will soon be img files under /boot as well (as i
understood one of the short term targets is currently to achieve a 2 partition
setup) so i dont see an issue with loop mounting just an
