On Mon, Feb 10, 2014 at 12:12:53PM +0100, Roberto Carlos Morano wrote: > I've came across with the same problem and I think that the attached > patch could do the job to fix this weird scenario. It looks if file > already exists and only overwrites it "in-target" if it doesn't. > > Since '/e/n/i' is already written by 'debian-installer' itself in > previous steps, I think it makes no sense to overwrite it again when > installation is almost complete. > > It doesn't make sense neither if the file already exists for any > reason (in e.g.: you create it in any other installation step like the > case mentioned in 'debian-users' list [1]), so the only case I think > it makes sense to set the '/e/n/i' file at that installation stage is > if there isn't one already.
This is wrong, I'm afraid. /etc/network/interfaces will *always* exist at this stage, because it's copied by netcfg's base-installer hook. However, the finish-install hook is explicitly using "netcfg write_loopback" in some cases to make sure that /etc/network/interfaces contains only the loopback entry. Declining to copy this to the target system would break those cases. What I'll do instead is copy /etc/network/interfaces only for the netcfg/target_network_config settings that require it. Then this may just work for you if you don't have network-manager installed, and otherwise you can use: d-i netcfg/target_network_config select ifupdown -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140828190355.ga12...@riva.ucam.org
