Re: How to get multistrap rootfs up and running?
-----BEGIN PGP SIGNED MESSAGE-----
On 02/02/11 20:53, Bjørn Forsman wrote:
> 2011/2/2 Neil Williams <email@example.com>:
>> 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
> 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
> 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
The source specifies where the packages are downloaded, that's debian.net.
> 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...
> Hm, "multistrap -h" example config contains a "bootstrap=Debian" line
Sigh. Read the manpage.
> but online doc uses "debootstrap=Debian" (DEbootstrap). What's the
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----