On Mon 26 Nov 2018 at 18:32:47 (-0500), Gary Dale wrote: > On 2018-11-26 7:57 a.m., Luciano Andress Martini wrote: > > Good morning Rob, > > Your message is what i am expecting to receive... > > > > Please don't judge me if you are a dedicated developer of Debian. I > > love and I am using it since the first versions, but I never come to > > this list because I am not welcome in groups in my life, and will be > > no different here. And i promisse I you get out from here the faster > > as I can, I just can't believe what you are doing to Debian... > > > > In older Debian versions, I am able to just do this: > > #vi /etc/network/interfaces > > #at 20:00 > > > ifdown eth0 > > > sleep 10 > > > ifup eth0 > > CTRL+D > > > > Debian must have a option during the installation a option like > > "Legacy mode" that install sysvinit, net-tools, and etc this will > > make everyone here happy.
I don't see the connection between this and the OP problem. > sysvinit is going the way of the dodo. I have nothing against it > personally but some things deserve a dignified retirement. Being able > to configure things with a few declarative files and standard commands > is simply a better way to run an operating system. > > Your example suggests that you want to change the ip address "after > hours". You can still do the same thing pretty much the same way. If > you are using the interfaces file, I don't see why your example won't > work as is. That's already dealt with in the thread. > In my case, I can simply change the ip address in > /etc/systemd/network/Management.network then instead of all the > commands you want to run, just do systemctl restart systemd-networkd. > Again, you can put that into an ad hoc script to run with "at" if you > want. That would seem to be most unhelpful to someone who, if they're running systemd at all, appears to be doing so reluctantly. Cheers, David.
