Fwd: Problem with most recent live-scripts
My apologies to Peter - I meant to reply to the list, not just to him.
Here's the last message I wrote:
----8<----
On 10/17/07, Peter Skogstr?m <peter.skogstrom at bitrunner.com> wrote:
>
> Add also
> --union-filesystem aufs
> --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-modules-2.6'
>
> And it will work, see earlier threads about this issue in the maillist.
With the following command line, I still got the errors:
lh_config -b usb-hdd --bootloader syslinux --union-filesystem aufs
--linux-packages 'linux-image-2.6 aufs-modules-2.6
squashfs-modules-2.6' --initramfs live-initramfs --packages-lists
kde-desktop --packages "less kile wireshark kismet mplayer perl-doc
scm hugs ruby1.8 audacious python2.5 iceweasel texlive-latex-base
xdebconfigurator lynx w32codecs openssh-server dnsutils
libcurl4-gnutls-dev libglut3-dev rsync ltrace strace"
Looking in the config/ directory, it did properly make the necessary
configuration changes:
$ grep LH_LINUX_PA config/*
config/chroot:# $LH_LINUX_PACKAGES: set kernel packages to use
config/chroot:LH_LINUX_PACKAGES="linux-image-2.6 aufs-modules-2.6
squashfs-modules-2.6"
$ grep LH_UNION config/*
config/chroot:# $LH_UNION_FILESYSTEM: set union filesystem
config/chroot:LH_UNION_FILESYSTEM="aufs"
I'm currently re-running the build process with output sent to a file
so I can check for errors during the process.
> You can test your newly built image with qemu first.
>
> qemu -hda binary.img
Yes, but in my case it's not much slower to write to flash, and if it
works I'm all done instead of having more steps to be finished.
Sorry for not searching the lists before posting; this is the primary
boot mechanism for my laptop right now and I was in a hurry. Thanks
for answering my question despite the answer probably being on the
list already.
Will
----8<----
That build process has finished now, and the log is posted here:
http://userpages.umbc.edu/~willm1/output.txt.gz egrep -i
'(error|warning)' output.txt shows nothing particularly interesting:
WARNING: The following packages cannot be authenticated!
Authentication warning overridden.
warning: /etc/X11/fonts/X11R7/Type1 does not exist or is not a directory
warning: /etc/X11/fonts/X11R7/Type1 does not exist or is not a directory
xserver-xorg postinst warning: not updating configuration as per $XORG_CUSTOM
libglu1-mesa-dev libgnutls-dev libgnutlsxx13 libgpg-error-dev libgtop2-7
libgnutls-dev libgnutlsxx13 libgpg-error-dev libgtop2-7 libgtop2-common
Selecting previously deselected package libgpg-error-dev.
Unpacking libgpg-error-dev (from .../libgpg-error-dev_1.4-2_i386.deb) ...
Setting up libgpg-error-dev (1.4-2) ...
Configuring mplayer ...Mplayer warning: dvd device '/dev/cdrom' does not exist!
/usr/lib/python2.5/site-packages/reportlab/lib/PyFontify.py:35:
Warning: 'with' will become a reserved keyword in Python 2.6
/usr/lib/python2.5/site-packages/reportlab/lib/PyFontify.py:36:
Warning: 'with' will become a reserved keyword in Python 2.6
!!! The following error/warning messages can be ignored !!!
Error: Error informing the kernel about modifications to partition
/dev/loop1p1 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/loop1p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Warning: The kernel was unable to re-read the partition table on
/dev/loop1 (Invalid argument). This means Linux won't know anything
about the modifications you made until you reboot. You should reboot
your computer before doing anything with /dev/loop1.
Error: Error informing the kernel about modifications to partition
/dev/loop1p1 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/loop1p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Warning: The kernel was unable to re-read the partition table on
/dev/loop1 (Invalid argument). This means Linux won't know anything
about the modifications you made until you reboot. You should reboot
your computer before doing anything with /dev/loop1.
!!! The above error/warning messages can be ignored !!!
... but the image still fails to boot properly.
Will
Reply to: