On Fri, 16 Jan 2009 23:10:47 +0100 Jelle de Jong <jelledejong@powercraft.nl> wrote: > > 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 That is fine - as long as the debootstrapped system is always going to live on the system that donates the hostname. We move that debootstap onto a new system and then try to connect to that new system over a local network and the hostname goes bang. > 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 Take a look at balloon3-config - that provides the workaround for balloon3 and something like that may be necessary more generally. The issue is can we realistically enforce a fixed hostname on all systems? D-I avoids this issue entirely, this only relates to debootstrap used outside d-i. -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
Attachment:
pgpBKNNRuq2Nq.pgp
Description: PGP signature