Bug#512066: problem identified
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Neil Williams wrote:
> Package: buildd.emdebian.org
> tag 512066 + confirmed
> retitle 512066 debootstrap needs customised hostname handling
> severity 512066 important
> thanks
>
> On Fri, 16 Jan 2009 22:12:25 +0100
> Jelle de Jong <jelledejong@powercraft.nl> wrote:
>
>> I did some research and the problem is that there is no hostname. The
>> below command fix this.
>>
>> up to the next issue.
>>
>> unset LANG
>> echo "emdebian" | tee /etc/hostname
>> echo "127.0.0.1 emdebian localhost.localdomain localhost" | tee
>> /etc/hosts
>> dpkg --configure -a
>
> Yes, this is an old (-ish) bug but it's difficult to see how to fix it
> without using Debian-Installer to set a user-specified hostname.
>
> Setting a default hostname is problematic. Copying the hostname of the
> host system is normal practice for a chroot because it's not expected
> to copy that debootstrap onto a completely different machine.
>
> Whatever scripts people use to copy the debootstrap onto the device
> need to make that decision and implement the appropriate fix.
>
> Ideas?
>
I am wondering, when doing a normal debootstrap of sid or lenny, it just
takes the hostname of the debootstraping system, this always worked
fine... what is diffrent with emdebian that this does not work. Can't it
just copy the /etc/hostname /etc/hosts /etc/resolv.conf and you got a
working network directly after chrooting.
This bug is no stopper, it just needs to be documentation correctly. It
is just not so nice that debootstrap fails, it should run in one time
100% successful :-D
Best regards,
Jelle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iJwEAQECAAYFAklxBeUACgkQ1WclBW9j5HmmVQP/dp+xoKYqYbMTcD1CMADk+/8U
ijvW3jlJPyAeCSkrtVdsACmX9CFDyqTXCByIIT6phlrpHuJy0drJiH6RVHd+irAt
T4jIvmnHTWldE5rlm12CeZWrzKnO5P/z1xwWYeSktqC2pFc2iYAYfgROec8qeEHN
qTXovSd04xBn9DNlSFM=
=+xJi
-----END PGP SIGNATURE-----
Reply to: