Cubic

  1. Bug #1860345
  2. Comment #6

Comment 6 for bug 1860345

Revision history for this message
Cubic PPA (cubic-wizard) wrote :

ISSUE #2:
---------

Cubic does not find a vmlinuz or initrd file in your customized file system. These would be the files you see in your /boot directory ~inside~ Cubic's chroot environment. I noticed something "odd" about the 19.10 live CD from Ubuntu: there are broken links in /boot pointing to non-existent vmlinuz and initrd files.

Here is the structure of /boot

    boot
    ├── config-5.3.0-18-generic
    ├── grub
    │   ├── gfxblacklist.txt
    │   └── unicode.pf2
    ├── initrd.img -> initrd.img-5.3.0-18-generic [BROKEN LINK!]
    ├── initrd.img.old -> initrd.img-5.3.0-18-generic [BROKEN LINK!]
    ├── memtest86+.bin
    ├── memtest86+.elf
    ├── memtest86+_multiboot.bin
    ├── System.map-5.3.0-18-generic
    ├── vmlinuz -> vmlinuz-5.3.0-18-generic [BROKEN LINK!]
    └── vmlinuz.old -> vmlinuz-5.3.0-18-generic [BROKEN LINK!]

As you can see, all symlinks to the kernel files are broken.

    $ file vmlinuz
    vmlinuz: cannot open `vmlinuz' (No such file or directory)

    $ file vmlinuz.old
    vmlinuz.old: cannot open `vmlinuz.old' (No such file or directory)

    $ file initrd.img
    initrd.img: cannot open `initrd.img' (No such file or directory)

    $ file initrd.img.old
    initrd.img.old: cannot open `initrd.img.old' (No such file or directory)

According to...

    https://packages.ubuntu.com/eoan/amd64/linux-image-5.3.0-18-generic/filelist

...the file "/boot/linux-headers-5.3.0-18" should be included in package linux-headers-5.3.0-18.

Surprisingly, `dpkg -l` shows that linux-headers-5.3.0-18 is actually installed.

    $ dpkg -l linux-image-5.3.0-18-generic
    ii linux-image-5.3.0-18-generic 5.3.0-18.19+1

RESOLUTION:
-----------

This is an issue with the original ISO, because past versions of Ubuntu did not have this problem. Because the ISO boots using the kernel (vmlinuz and initrd) on the ISO, and not the kernel in the compressed Linux file system (the chroot environment in Cubic), the ISO boots up just fine without these files. (The correct kernel files are probably eventually copied to /boot during installation, so the end user never notices).

As a result, there are no code changes we can do in cubic that can directly resolve ISSUE #2, but there is something you can do, which I will post in a separate comment.