Re: initramfs-tools problem follows apt-get install mintupdate

Sorry guys. I was too engaged to see any other interpretation of my original post.

While trying to find packages that would help me mount my
Android cell phone, turns out I enabled a "poison pill" package
for initramfs-tools-ubuntu-touch. This is ONLY for use on Android devices.

The solution was to remove this set packages that had no business being
on a desktop install and guarantees failure of subsequent kernel builds.
The documentation does not in anyway warn you.

This package has no business being in a desktop distro as it
tries to build a kernel in boot locations only used my these touch pads.

After initramfs-tools does much of its thing it invokes initramfs-tools-ubuntu-touch

which then invokes

root@apr01$ cat -n flash-touch-initrd
      1    #!/bin/sh
      2
      3    BOOT="LNX boot KERNEL"
      4 INITRD="/usr/lib/ubuntu-touch-generic-initrd/initrd.img-touch"
      5
      6    # we dont want to run if FLASH_KERNEL_SKIP is set, the ubuntu
      7    # image build system uses this
      8    if [ -n "$FLASH_KERNEL_SKIP" ]; then
      9        exit 0
     10    fi
     11
     12    # if there is "recovery" on the kernel cmdline, we are most
     13    # likely running in dual boot mode, do nothing then, else we
     14    # trash the android boot.img
     15    grep -q recovery /proc/cmdline && exit 0
     16
     17    case "$1" in
     18        /*)
     19            [ ! -e "$1" ] && echo "E: No initrd at $1" && exit 1
     20            INITRD="$1"
     21        ;;
     22        -h|--help)
     23            echo "usage: $(basename $0) [path to initrd]"
     24            exit 0
     25        ;;
     26    esac
     27
     28    for i in $BOOT; do
     29        path=$(find /dev -name "$i"|grep disk| head -1)
     30        [ -n "$path" ] && break
     31    done
     32
     33    [ -z "$path" ] && echo "E: No boot partition found !" && exit 1
     34
     35    abootimg -u $path -r $INITRD


line 3 gives choices for possible  boot locations
line 33 gives the fail message I saw
line 35 abootimg - manipulate Android Boot Images

The related group of packages is not a cross anything
but intended for direct use on an Android device.

How it made it into the Mint 17.1 distro (or Ubuntu)
is a bad mistake like putting a "kick me"  sign on a live land mine.

Thanks,
Chris




On 15-06-04 02:00 AM, Viorel Tabara wrote:
> On 06/03/2015 07:03 AM, caziz wrote:
>> Partition flags OK as the machine has booted correctly [...]
> Your original post suggest otherwise:
>
>> root apr01 # apt-get install mintupdate
>> [...]
>> Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
>> update-initramfs: Generating /boot/initrd.img-3.13.0-37-generic
>> E: No boot partition found !
> ...and thus Gustin's recommendations.
>
>> Problem is with apt trying to build new initrd.img-3.13.0-37-generic
>> something with the scripts around initramfs-tools has  gone screwy
>


_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying