On 12/8/18 11:24 AM, Samuel Sieb wrote:
On 12/8/18 10:46 AM, Matthew Miller wrote:
> On Sat, Dec 08, 2018 at 01:31:34PM -0500, Sam Varshavchik wrote:
>> I'm trying to understand what prevents having a shell script, or
>> two, that takes a single parameter, and turns on or off the
>> specified network interface. And then calling those scripts "ifup"
>> and "ifdown".
>>
>> Why does this have to stop working, as it does now?
>
> Oh -- those shell scripts exist. They're there now. The person who
> maintains
> them isn't interested in doing so forever, so there's a warning. If
you'd
> like, I'm sure you could step up and say "I want to maintain these
> commands
> as a compatibility layer".
The NetworkManager package contains ifup and ifdown scripts. I don't
see how there's any maintenance involved, since they just call nmcli.
The warning message just says to use the scripts from NetworkManager
instead of network-scripts, not that they're going away.
Where are NetworkManager's located?
$ which ifup
/usr/sbin/ifup
$ su root -c "find / -name ifup"
Password:
/etc/sysconfig/network-scripts/ifup
/etc/alternatives/ifup
/usr/sbin/ifup
/usr/share/bash-completion/completions/ifup
/var/lib/alternatives/ifup