Thanks again for all your help and ideas. I went for the easiest way and tried to adapt my preseed late_command in order to invoke a copy of /target/e/n/i to /e/n/i once my post installation PERL script has finished running. So my late_command looks like that now:
d-i preseed/late_command string \ in-target wget http://x.x.x.x/d-i/wheezy/postinst.pl -O /tmp/postinst.pl; \ in-target /bin/chmod 755 /tmp/postinst.pl; \ in-target /tmp/postinst.pl; \ cp /target/etc/network/interfaces /etc/network/interfaces; Just did a test preseed installation using that and it worked perfectly. Nice and easy workaround for a weird modification in netcfg as you say... I guess a few other people will get stuck too. I am still suprised that netcfg does not support the configuration of bonding, VLAN or bridging. But until it does people will have to find solutions like mine and modify /e/n/i afterwards. ----- Original Message ----- From: Brian <a...@cityscape.co.uk> To: debian-user@lists.debian.org Cc: Sent: Monday, May 20, 2013 8:55 PM Subject: Re: Wheezy preseed overwritting interfaces file On Mon 20 May 2013 at 08:54:21 -0700, ML mail wrote: > Maybe I could add an extra command to late_command after running my > PERL script such as: > > cp /target/etc/network/interfaces /etc/network/interfaces > > but I am not sure if it is possible to mix "in-target" commands with > no "in-target" commands in one single late_command config param. Did > you maybe already try that and know? else I will simply give it a try > later on. I've not tried it. Please let us know if it works. A couple of ideas, neither tested: 1. Backup /target/e/n/i. At least it will be on the new system and give you less work should you want to use it. 2. Delete /usr/lib//finish-install.d/55netcfg-copy-config at some stage of the install. This will effectively give you a Squeeze situation. 55netcfg-copy-config is a pain anyway. It appears to focus on making sure someone who installed GNOME and Network Manager has a connected system. If you go for a minimal install with ifupdown it seems you are penalised. Installing over a wireless connection without a DE surely epitomises that. No network connection on first boot and not a single indication in the installer or in the documentation it might happen. This removal of connectivity legitimately configured during the install must be a first in Debian's history. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520185508.GI23758@desktop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1369085136.71104.yahoomail...@web164601.mail.gq1.yahoo.com
