(mirror of https://github.com/vyos/live-boot.git) https://git.amelek.net/vyos/live-boot.git/atom?h=current 2011-03-09T16:52:46+00:00 2011-03-09T16:52:46+00:00 Daniel Baumann daniel@debian.org 2010-05-24T13:27:36+00:00 urn:sha1:e66f79476042794195978ee641aa7ea0d9ca6e0a 2011-03-09T16:48:02+00:00 Chris Lamb lamby@debian.org 2008-09-30T23:56:55+00:00 urn:sha1:2b0b270f2445897b6137fbe48919097ca42e9c9e 2011-03-09T16:48:02+00:00 Chris Lamb lamby@debian.org 2008-09-30T23:56:30+00:00 urn:sha1:116f7ddd2e6ebb1377474da592b7d43604e7b166 2011-03-09T16:48:02+00:00 Marco Amadori amadorim@vdavda.com 2008-09-16T15:26:09+00:00 urn:sha1:c00d324467314b6f4d6a1d6cc2d9a6ecfbd308cd * This is one of a series of interventions that means to be gentle to debian-live builders and to persistence users; the rationale is that if a file is present on the rootfs it does not need to be overwritten from scratch since its presence means either a live-helper configuration at build time or a persistent/snapshot at run time. 2011-03-09T16:48:01+00:00 Chris Lamb chris@chris-lamb.co.uk 2008-08-08T03:54:34+00:00 urn:sha1:5f0f3b0c36d433a462176f970d371c77c3020749 2011-03-09T16:47:55+00:00 Chris Lamb chris@chris-lamb.co.uk 2008-03-21T20:06:30+00:00 urn:sha1:bc986e631b2dcba0f5ce7c742d498f5820028f0b We must configure a valid hostname in the target before 10adduser, or sudo fails with "unable to resolve host (none)" - before 18hostname is called /root/etc/hostname is empty. This was resulting in the "su as sudo" modifications not being applied in the target which was causing X configuration applications to show different behaviours when attempting elevating their priviledges. Reordering the hostname configuration seems somewhat preferable to applying a hack inside 10adduser to use 'su' or similar, as other pre-XXhostname calls may incorporate calls to sudo in the future.