-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/02/11 20:53, Bjørn Forsman wrote: > 2011/2/2 Neil Williams <[email protected]>: >> Baked cannot simply be created and booted. It requires a LOT of >> specialist knowledge about your specific board. > > When I said "freshly baked" I didn't know about "Baked" the Emdebian > flavor (sorry). I'm using (or trying to use) Grip.
Right, OK. In that case, it's probably down to how you are trying to access the rootfs. dpkg --configure -a is normally best run *before* booting the rootfs, whether you connect to it over NFS or anything else, some (many) packages need to be configured before the binaries will run correctly. These cannot be configured on a different architecture because the process involves executing lots of binaries of the wrong architecture. > [General] > arch=armel > directory=/opt/multistrap/ > cleanup=true > noauth=true <----- I changed this to 'true' so it would build Wrong version of multistrap. Pull in the one from Debian experimental. It's not good to rely on noauth unless you have direct access to the unauthorised repositories. http://www.emdebian.org/multistrap/keyrings.html > source=http://cdn.debian.net/debian > keyring=debian-archive-keyring > suite=lenny > > > BTW, is this Debian or Emdebian Grip? How to tell when > "aptsources=Grip Updates" and "bootstrap=Debian"? That's Debian. See http://www.emdebian.org/multistrap/examples.php http://www.emdebian.org/multistrap/repositories.html The source specifies where the packages are downloaded, that's debian.net. http://www.emdebian.org/grip/#mirrors http://www.emdebian.org/multistrap/examples/grip-lenny.conf > It says that multistrap should create a normal debootstrap... I'm new > at this, but isn't a debootstrap supposed to have a debootstrap binary > inside? Mine does not... No > Hm, "multistrap -h" example config contains a "bootstrap=Debian" line Sigh. Read the manpage. > but online doc uses "debootstrap=Debian" (DEbootstrap). What's the > difference? None. Read the manpage. "(Older versions of multistrap supported the same option under the "debootstrap" name - this spelling is still supported but new configuration files should be "bootstrap" instead." > The multistrap doc doesn't seem to talk about what to do after you > have built the rootfs. I have successfully built a rootfs with it but > none of the packages are configured so I cannot login. What to do? Mount the system without booting it in such a way that you can chroot into it and execute the binaries on a device of the same architecture. - -- Neil Williams ============= http://www.linux.codehelp.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJNSc1NAAoJEPFn5DyBQ7aCKpwP/2Th5MBmwLd6cLAb7375809t ZPMXbf6BtL/XPNB5RdZUE8lYX2OynxQ6r/Di5h2aj5Xtk2OB/p0X8houMgl39Fu9 R3CsajBP8UQ2lLxTn+BNiKYAiLOL8IqPUw8JBjlCHNsPdN9It1+LN3CRmWgRgmfF FVyM+61HF4Xrh4ELt/HCyL94dGxj4YUJzHkb75LwNIIwsEINM+0S5QiOpB1TjlVx 4rxMrM1y8hej1ijPbbDveGm7EEQc1uuJEUYeFWveQMQOFDP9ThxSVwOhq2crLqg7 ahqKnYN1lwcyE9nDPKLximGtZ7tfnqMu3haQS31pN6gMwOiS66hYqfQoFnzP+uag uk0QT4JkbssWARPwzf01wQ9JhcI2m5OgoSXwF/EJOiYe8bbqQnDNog1tejygnsGS U75es4wtuz+RaH/Qh2pyInAmmCeb2UwPHElREkz7buYZ05v9CrwfXOcjG8W3y5L6 99b6MgHvP4XFuWZfb4O2ajQ7+4G3vNmXaGKN2houZlLvBIZp8NNrcNG/pa7EM8I7 7MlBxM6gNk/l+5OnGX8DKhEMiROCxkZoqDELhu5YxM5w7t02S/zxogsF0RGcjVES FcUteZOp3zs57KIP91C5CXO3JqtTMMRFwiHLYhDDw/KFh/0r7nN3HcYbg46pgcXL U7CT8GtzfYoMjaG3tBkw =i6Kw -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
