Thanks for testing. I'll do the changes and testing here as soon as I can.
On Thu, Oct 2, 2014 at 3:07 PM, Olivier Sallou wrote:
>
> On 10/01/2014 06:56 PM, Javier Fontan wrote:
>> This can probably be caused because after save the network
>> configuration is already generated and the next time t
On 10/01/2014 06:56 PM, Javier Fontan wrote:
> This can probably be caused because after save the network
> configuration is already generated and the next time that network stop
> is not working. Can you check that using the same method as ubuntu
> makes it work? If this is correct I can modify t
Another solution is to move context to early stage (before networking)
as we do already and let OS start network. Also that solves problem with
saved images. Of cause if some context script wants network it should
fork and wait for network, or install itself to /etc/network/if-up.d/.
http://gr
This can probably be caused because after save the network
configuration is already generated and the next time that network stop
is not working. Can you check that using the same method as ubuntu
makes it work? If this is correct I can modify the context packages
accordingly.
Thanks
On Tue, Sep
Hi,
we face some issues with the network restart on Debian with the
00-network script.
The issue occurs after an image save and a start of the new image, not
at first boot.
The "network stop" fails.
In the 00-network script, there is a test if [ ... "ubuntu"], to apply
ifup/ifdown commands.
Here
