Package: extlinux
Version: 2:4.03+dfsg-12
Severity: minor
I was really confused by this /boot/extlinux/memdisk.cfg in my
hand-bootstrapped images:
label m0
menu label Memdisk, image initrd.img
linux /boot/extlinux/memdisk
initrd /boot/initrd.img
append raw
>From reading the source, this is because extlinux-update assumes any
file /boot/*.img or /boot/*.iso is a bootable root filesystem.
Obviously this is not the case for initrd.img, which is a symlink to
the current ramdisk -- created in /boot by the Debian kernel
infrastructure because kernel-img.conf contains
link_in_boot=yes
Which I added for my own static extlinux.conf :-)
PROMPT 0
LABEL linux
KERNEL vmlinuz
APPEND ro initrd=initrd.img
LABEL old
KERNEL vmlinuz.old
APPEND ro initrd=initrd.img.old
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
