On 12/10/18 6:28 AM, ToddAndMargo via users wrote:
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?
/usr/libexec/nm-ifup
I described what happens in an earlier post.
[egreshko@f29bk ~]$ which ifup
/usr/sbin/ifup
[egreshko@f29bk ~]$ ll /usr/sbin/ifup
lrwxrwxrwx. 1 root root 22 Nov 7 10:35 /usr/sbin/ifup -> /etc/alternatives/ifup
[egreshko@f29bk ~]$ ll /etc/alternatives/ifup
lrwxrwxrwx. 1 root root 20 Nov 7 10:35 /etc/alternatives/ifup -> /usr/libexec/nm-ifup
[egreshko@f29bk ~]$ cat /usr/libexec/nm-ifup
#!/usr/bin/sh
nmcli connection load "/etc/sysconfig/network-scripts/ifcfg-$1" &&
exec nmcli connection up filename "/etc/sysconfig/network-scripts/ifcfg-$1"
--
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme