Public bug reported: Binary package hint: rootstock
i am trying to build an ubuntu lucid image for a beagleboard. the image boots, but i cant log in. when i inspected the image i found that there was not entry for my username in /etc/passwd. i used the following script to run rootstock: PACKAGES="ubuntu-minimal,linux-firmware,wireless-tools,usbutils" PACKAGES+=",openssh-server,denyhosts,rsync" PACKAGES+=",vim,wget,bash-completion,screen" PACKAGES+=",mpd,alsa-utils,pulseaudio,pulseaudio-module-zeroconf" PACKAGES+=",rtorrent" sudo rootstock \ --fqdn beagleboard \ --login sam --password temppwd \ --imagesize 4G \ --seed $PACKAGES \ --dist lucid \ --serial ttyS2 \ --script fixup.sh \ --components "main universe multiverse" \ --kernel-image http://rcn-ee.net/deb/kernel/beagle/lucid/v2.6.32.11-l13/linux-image-2.6.32.11-l13_1.0lucid_armel.deb i spotted the following error message in the rootstock output: Processing triggers for libc-bin ... ldconfig deferred processing now taking place I: Virtual Machine done I: Creating tarball from rootfs I: Mounting temporary Image /usr/bin/rootstock: line 195: 13642 Segmentation fault qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1 I: ARM rootfs created as /data/beagleboard/ubuntu-lucid/build/armel-rootfs-201004270934.tgz I: Extracting vmlinuz from *.deb cp: cannot stat `/tmp/tmp.7KG74k1ImH/tmpmount/boot/initrd.img-*': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rootstock 0.1.99.3-0ubuntu1 Uname: Linux 2.6.34-020634rc5-generic x86_64 Architecture: amd64 Date: Tue Apr 27 10:01:18 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.utf8 SourcePackage: rootstock ** Affects: rootstock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- /usr/bin/rootstock: line 195: 13642 Segmentation fault qemu-system-arm $QEMUOPTS -append "${APPEND}" > $QEMUFIFO 2>&1 https://bugs.launchpad.net/bugs/570588 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs