ifup/ifdown

[ToddAndMargo]

Hi All,

What is this all about?

$ ifdown eno2
WARN      : [ifdown] You are using 'ifdown' script provided by 
'network-scripts', which are now deprecated.
WARN      : [ifdown] 'network-scripts' will be removed from distribution 
in near future.
WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead 
- it provides 'ifup/ifdown' scripts as well.
WARN      : [ifdown] You are using 'ifdown' script provided by 
'network-scripts', which are now deprecated.
WARN      : [ifdown] 'network-scripts' will be removed from distribution 
in near future.
WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead 
- it provides 'ifup/ifdown' scripts as well.
Device 'eno2' successfully disconnected.

-T

[Ed Greshko]

On 12/8/18 10:27 AM, ToddAndMargo via users wrote:
> Hi All,
>
> What is this all about?
>
> $ ifdown eno2
> WARN      : [ifdown] You are using 'ifdown' script provided by 'network-scripts', which
> are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead - it provides
> 'ifup/ifdown' scripts as well.
> WARN      : [ifdown] You are using 'ifdown' script provided by 'network-scripts', which
> are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead - it provides
> 'ifup/ifdown' scripts as well.
> Device 'eno2' successfully disconnected.

Seems pretty clear to me.

One thing it could have done is indicate that you start using "nmcli" to control
interfaces from the command line.

[Samuel Sieb]

On 12/7/18 6:27 PM, ToddAndMargo via users wrote:
> What is this all about?
>
> $ ifdown eno2
> WARN      : [ifdown] You are using 'ifdown' script provided by 
> 'network-scripts', which are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution 
> in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead
> it provides 'ifup/ifdown' scripts as well.
>
> WARN      : [ifdown] You are using 'ifdown' script provided by 
> 'network-scripts', which are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution 
> in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead
> it provides 'ifup/ifdown' scripts as well.
>
> Device 'eno2' successfully disconnected.

ifup and ifdown use the alternatives system which seems to default to 
use the network-scripts version.  You can either switch it or just 
uninstall network-scripts.

[sean darcy]

On 12/7/18 9:27 PM, ToddAndMargo via users wrote:
> Hi All,
>
> What is this all about?
>
> $ ifdown eno2
> WARN      : [ifdown] You are using 'ifdown' script provided by 
> 'network-scripts', which are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution 
> in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead
> it provides 'ifup/ifdown' scripts as well.
>
> WARN      : [ifdown] You are using 'ifdown' script provided by 
> 'network-scripts', which are now deprecated.
> WARN      : [ifdown] 'network-scripts' will be removed from distribution 
> in near future.
> WARN      : [ifdown] It is advised to switch to 'NetworkManager' instead
> it provides 'ifup/ifdown' scripts as well.
>
> Device 'eno2' successfully disconnected.
>
> -T

I also missed the memo. If this stackexchange post is correct,all the 
ifcfg-* configurations remain, but not the executable scripts 
(ifup,ifdown,..). Which is a LOT different than "'network-scripts' will 
be removed from distribution in near future."

But who knows ? Maybe there is a memo.

https://unix.stackexchange.com/questions/483354/rhel-8-deprecated-network-sc...

sean

[Sam Varshavchik]

sean darcy writes:
> On 12/7/18 9:27 PM, ToddAndMargo via users wrote:
>
> I also missed the memo. If this stackexchange post is correct,all the ifcfg-
> configurations remain, but not the executable scripts (ifup,ifdown,..).
>
> Which is a LOT different than "'network-scripts' will be removed from  
> distribution in near future."
>
> But who knows ? Maybe there is a memo.

I'd be shocked if there was any public discussion of this, anywhere.

This is just more of the same: replacing simple, working, well-understood  
infrastructure with an over-engineered hairball and intentionally obfuscated  
documentation, making it possible to generate revenue from providing actual,  
usable knowledge needed to effectively use the replacement frankentools.

See also: systemd

[Matthew Miller]

On Sat, Dec 08, 2018 at 11:58:18AM -0500, Sam Varshavchik wrote:
> > But who knows ? Maybe there is a memo.
>
> I'd be shocked if there was any public discussion of this, anywhere.

Prepare to be shocked! We've talked about this quite a bit over the years.
https://lists.fedoraproject.org/archives/list/[e-mail]/...

These scripts are old, fragile, hard to maintain, and actually not working
and well-understood. They have real bugs and problems. Moving to a single
code path is a big improvement.
> This is just more of the same: replacing simple, working,
> well-understood infrastructure with an over-engineered hairball and
> intentionally obfuscated documentation, making it possible to
> generate revenue from providing actual, usable knowledge needed to
> effectively use the replacement frankentools.

Whatever flaws we've got, this allegation is so far off of the mark that
it's not even in the ballpark. Never attribute to malice that which can be
explained by *this stuff is hard*.

[Sam Varshavchik]

Matthew Miller writes:
> On Sat, Dec 08, 2018 at 11:58:18AM -0500, Sam Varshavchik wrote:
> > > But who knows ? Maybe there is a memo.
> >
> > I'd be shocked if there was any public discussion of this, anywhere.
>
> Prepare to be shocked! We've talked about this quite a bit over the years.
> https://lists.fedoraproject.org/archives/list/[e-mail]/...
>
> These scripts are old, fragile, hard to maintain, and actually not working
> and well-understood. They have real bugs and problems. Moving to a single
> code path is a big improvement.

This is a sleight of hand. This is not about removing redundant code paths,  
but preserving backwards compatibility.
> > This is just more of the same: replacing simple, working,
> > well-understood infrastructure with an over-engineered hairball and
> > intentionally obfuscated documentation, making it possible to
> > generate revenue from providing actual, usable knowledge needed to
> > effectively use the replacement frankentools.
>
> Whatever flaws we've got, this allegation is so far off of the mark that
> it's not even in the ballpark. Never attribute to malice that which can be
> explained by *this stuff is hard*.

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?

[Matthew Miller]

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".

[Samuel Sieb]

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.

[ToddAndMargo]

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

[Samuel Sieb]

On 12/9/18 2:28 PM, ToddAndMargo via users wrote:
> On 12/8/18 11:24 AM, Samuel Sieb wrote:
> > 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

rpm -ql NetworkManager | grep ifup

/usr/libexec/nm-ifup

[ToddAndMargo]

On 12/9/18 2:36 PM, Samuel Sieb wrote:
> On 12/9/18 2:28 PM, ToddAndMargo via users wrote:
> > On 12/8/18 11:24 AM, Samuel Sieb wrote:
> > > 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
>
> rpm -ql NetworkManager | grep ifup
>
> /usr/libexec/nm-ifup

Cool! Thank you.  I adore that rpm command!

I decided to see what I would lose by removing network-scripts.
Nothing I can't live without now that I have nm-ifup/down.

-T

$ rpm -ql network-scripts
/etc/rc.d/init.d/network
/etc/sysconfig/network-scripts
/etc/sysconfig/network-scripts/ifcfg-lo
/etc/sysconfig/network-scripts/ifdown
/etc/sysconfig/network-scripts/ifdown-bnep
/etc/sysconfig/network-scripts/ifdown-eth
/etc/sysconfig/network-scripts/ifdown-ippp
/etc/sysconfig/network-scripts/ifdown-ipv6
/etc/sysconfig/network-scripts/ifdown-isdn
/etc/sysconfig/network-scripts/ifdown-post
/etc/sysconfig/network-scripts/ifdown-routes
/etc/sysconfig/network-scripts/ifdown-sit
/etc/sysconfig/network-scripts/ifdown-tunnel
/etc/sysconfig/network-scripts/ifup
/etc/sysconfig/network-scripts/ifup-aliases
/etc/sysconfig/network-scripts/ifup-bnep
/etc/sysconfig/network-scripts/ifup-eth
/etc/sysconfig/network-scripts/ifup-ippp
/etc/sysconfig/network-scripts/ifup-ipv6
/etc/sysconfig/network-scripts/ifup-isdn
/etc/sysconfig/network-scripts/ifup-plip
/etc/sysconfig/network-scripts/ifup-plusb
/etc/sysconfig/network-scripts/ifup-post
/etc/sysconfig/network-scripts/ifup-routes
/etc/sysconfig/network-scripts/ifup-sit
/etc/sysconfig/network-scripts/ifup-tunnel
/etc/sysconfig/network-scripts/ifup-wireless
/etc/sysconfig/network-scripts/init.ipv6-global
/etc/sysconfig/network-scripts/network-functions
/etc/sysconfig/network-scripts/network-functions-ipv6
/usr/lib/.build-id
/usr/lib/.build-id/17
/usr/lib/.build-id/17/91424f6907165883b30dc186030fb9d11c0312
/usr/sbin/ifdown
/usr/sbin/ifup
/usr/sbin/usernetctl
/usr/share/doc/network-scripts
/usr/share/doc/network-scripts/examples
/usr/share/doc/network-scripts/examples/ifcfg-bond-802.3ad
/usr/share/doc/network-scripts/examples/ifcfg-bond-activebackup-arpmon
/usr/share/doc/network-scripts/examples/ifcfg-bond-activebackup-miimon
/usr/share/doc/network-scripts/examples/ifcfg-bond-slave
/usr/share/doc/network-scripts/examples/ifcfg-bridge
/usr/share/doc/network-scripts/examples/ifcfg-bridge-port
/usr/share/doc/network-scripts/examples/ifcfg-eth-alias
/usr/share/doc/network-scripts/examples/ifcfg-eth-dhcp
/usr/share/doc/network-scripts/examples/ifcfg-vlan
/usr/share/doc/network-scripts/examples/static-routes-ipv6
/usr/share/doc/network-scripts/sysconfig.txt
/usr/share/man/man8/ifdown.8.gz
/usr/share/man/man8/ifup.8.gz
/usr/share/man/man8/usernetctl.8.gz

[ToddAndMargo]

On 12/9/18 6:06 PM, ToddAndMargo via users wrote:
> On 12/9/18 2:36 PM, Samuel Sieb wrote:
> > On 12/9/18 2:28 PM, ToddAndMargo via users wrote:
> > > On 12/8/18 11:24 AM, Samuel Sieb wrote:
> > > > 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
> >
> > rpm -ql NetworkManager | grep ifup
> >
> > /usr/libexec/nm-ifup
>
> Cool! Thank you.  I adore that rpm command!
>
> I decided to see what I would lose by removing network-scripts.
> Nothing I can't live without now that I have nm-ifup/down.
>
> -T

Uh Oh!  If I remove network-scripts, will I still
have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??

[Ed Greshko]

On 12/10/18 10:37 AM, ToddAndMargo via users wrote:
> Uh Oh!  If I remove network-scripts, will I still
> have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??

[egreshko@acer ~]$ rpm -q network-scripts
package network-scripts is not installed

[egreshko@acer ~]$ ls /etc/sysconfig/network-scripts/
ifcfg-asus2  ifcfg-enp8s0  ifcfg-misty-net  keys-asus2  keys-misty-net

[Ed Greshko]

On 12/10/18 10:55 AM, Ed Greshko wrote:
> On 12/10/18 10:37 AM, ToddAndMargo via users wrote:
> > Uh Oh!  If I remove network-scripts, will I still
> > have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??
>
> [egreshko@acer ~]$ rpm -q network-scripts
> package network-scripts is not installed
>
> [egreshko@acer ~]$ ls /etc/sysconfig/network-scripts/
> ifcfg-asus2  ifcfg-enp8s0  ifcfg-misty-net  keys-asus2  keys-misty-net

Oh, and it also can be helpful to do "dnf info network-scripts"

Description  : This package contains the legacy scripts for activating &
             : deactivating of most network interfaces. It also provides a legacy
             : version of 'network' service.
             :
             : The 'network' service is enabled by default after installation of
             : this package, and if the network-scripts are installed alongside
             : NetworkManager, then the ifup/ifdown commands from network-scripts
             : take precedence over the ones provided by NetworkManager.
             :
             : If user has both network-scripts & NetworkManager installed, and
             : wishes to use ifup/ifdown from NetworkManager primarily, then they
             : has to run command: $ update-alternatives --config ifup
             :
             : Please note that running the command above will also disable the
             : 'network' service.

[ToddAndMargo]

On 12/9/18 7:03 PM, Ed Greshko wrote:
> dnf info

I keep forgetting about that command.  Thank you!

[ToddAndMargo]

On 12/9/18 6:55 PM, Ed Greshko wrote:
> On 12/10/18 10:37 AM, ToddAndMargo via users wrote:
> > Uh Oh!  If I remove network-scripts, will I still
> > have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??
>
> [egreshko@acer ~]$ rpm -q network-scripts
> package network-scripts is not installed
>
> [egreshko@acer ~]$ ls /etc/sysconfig/network-scripts/
> ifcfg-asus2  ifcfg-enp8s0  ifcfg-misty-net  keys-asus2  keys-misty-net

Thank you!

I have a ton of things written to read
/etc/sysconfig/network-scripts.ifcfg-xxxx

-T

[Samuel Sieb]

On 12/9/18 6:37 PM, ToddAndMargo via users wrote:
> On 12/9/18 6:06 PM, ToddAndMargo via users wrote:
> > I decided to see what I would lose by removing network-scripts.
> > Nothing I can't live without now that I have nm-ifup/down.

You still have ifup and ifdown.  They are symlinks to the nm scripts.
> Uh Oh!  If I remove network-scripts, will I still
> have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??

NetworkManager still uses those files.

[ToddAndMargo]

On 12/9/18 10:59 PM, Samuel Sieb wrote:
> On 12/9/18 6:37 PM, ToddAndMargo via users wrote:
> > On 12/9/18 6:06 PM, ToddAndMargo via users wrote:
> > > I decided to see what I would lose by removing network-scripts.
> > > Nothing I can't live without now that I have nm-ifup/down.
>
> You still have ifup and ifdown.  They are symlinks to the nm scripts.
> > Uh Oh!  If I remove network-scripts, will I still
> > have /etc/sysconfig/network-scripts.ifcfg-xxxx  ??
>
> NetworkManager still uses those files.

Thank you!

[Ed Greshko]

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"

[Samuel Sieb]

On 12/8/18 10:31 AM, 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".

Nothing prevents that, those scripts still exist.
> Why does this have to stop working, as it does now?

It doesn't.  Remove the network-scripts package and everything will keep 
working and you won't see those warning messages.

[stan]

On Sat, 8 Dec 2018 11:30:31 -0800
Samuel Sieb  wrote:
> It doesn't.  Remove the network-scripts package and everything will
> keep working and you won't see those warning messages.

I don't find a package network-scripts.  The ifup, ifdown, etc.
scripts in /etc/sysconfig/networking-scripts are from package
initscripts.  I don't think it is safe to remove that package, since I
see things like /etc/rc.d owned by it. Is it safe? I also find a package
net-tools that installs things like ifconfig, etc. It claims most of
them are obsolete in the rpm info.  Is it safe to remove that package if
NetworkManager is installed?

They aren't hurting anything, but I prefer not to leave cruft around.

[Samuel Sieb]

On 12/8/18 12:42 PM, stan wrote:
> On Sat, 8 Dec 2018 11:30:31 -0800
> Samuel Sieb  wrote:
> > It doesn't.  Remove the network-scripts package and everything will
> > keep working and you won't see those warning messages.
>
> I don't find a package network-scripts.  The ifup, ifdown, etc.
> scripts in /etc/sysconfig/networking-scripts are from package
> initscripts.  I don't think it is safe to remove that package, since I
> see things like /etc/rc.d owned by it. Is it safe? I also find a package
> net-tools that installs things like ifconfig, etc. It claims most of
> them are obsolete in the rpm info.  Is it safe to remove that package if
> NetworkManager is installed?

The network-scripts package was created from initscripts in F29.  You 
probably can remove net-tools if you don't use those commands, but it's 
fine to keep it for now.

[stan]

On Sat, 8 Dec 2018 14:43:13 -0800
Samuel Sieb  wrote:
> The network-scripts package was created from initscripts in F29.  You 
> probably can remove net-tools if you don't use those commands, but
> it's fine to keep it for now.

Thanks.  I think I will just keep them.

[sean darcy]

On 12/8/18 1:08 PM, Matthew Miller wrote:
> On Sat, Dec 08, 2018 at 11:58:18AM -0500, Sam Varshavchik wrote:
> > > But who knows ? Maybe there is a memo.
> >
> > I'd be shocked if there was any public discussion of this, anywhere.
>
> Prepare to be shocked! We've talked about this quite a bit over the years.
> https://lists.fedoraproject.org/archives/list/[e-mail]/...
>
> These scripts are old, fragile, hard to maintain, and actually not working
> and well-understood. They have real bugs and problems. Moving to a single
> code path is a big improvement.
> > This is just more of the same: replacing simple, working,
> > well-understood infrastructure with an over-engineered hairball and
> > intentionally obfuscated documentation, making it possible to
> > generate revenue from providing actual, usable knowledge needed to
> > effectively use the replacement frankentools.
>
> Whatever flaws we've got, this allegation is so far off of the mark that
> it's not even in the ballpark. Never attribute to malice that which can be
> explained by *this stuff is hard*.

Didn't mean to end up in flames, but is there a description of the 
change ? Is my summary of the stackexchange post actually how this is 
going to work ?

thanks,

sean

[Samuel Sieb]

On 12/8/18 8:33 AM, sean darcy wrote:
> I also missed the memo. If this stackexchange post is correct,all the 
> ifcfg-* configurations remain, but not the executable scripts 
> (ifup,ifdown,..). Which is a LOT different than "'network-scripts' will 
> be removed from distribution in near future."
>
> But who knows ? Maybe there is a memo.
>
> https://unix.stackexchange.com/questions/483354/rhel-8-deprecated-network-sc...

You misunderstood the post.  The ifup-* scripts in 
/etc/sysconfig/network-scripts will become ineffective, but the "ifup" 
script still exists.  Just remove the network-scripts package and 
everything will keep on working the same, unless you have some very 
unusual special configuration that you have manually changed.

[Ed Greshko]

On 12/9/18 3:27 AM, Samuel Sieb wrote:
> On 12/8/18 8:33 AM, sean darcy wrote:
> > I also missed the memo. If this stackexchange post is correct,all the ifcfg-*
> > configurations remain, but not the executable scripts (ifup,ifdown,..). Which is a LOT
> > different than "'network-scripts' will be removed from distribution in near future."
> >
> > But who knows ? Maybe there is a memo.
> >
> > https://unix.stackexchange.com/questions/483354/rhel-8-deprecated-network-sc...
>
> You misunderstood the post.  The ifup-* scripts in /etc/sysconfig/network-scripts will
> become ineffective, but the "ifup" script still exists.  Just remove the network-scripts
> package and everything will keep on working the same, unless you have some very unusual
> special configuration that you have manually changed.

When I posted earlier I missed something.

Yes, if you remove network-scripts you can still run ifup/ifdown.  What will happen is
that that appropriate /etc/alternatives will be created.  So, for example, ifdown will
point to /usr/libexec/nm-ifdown.  (NetworkManager-ifdown).

And if you look at that you'd see.

[egreshko@meimei ~]$ cat /usr/libexec/nm-ifdown
#!/usr/bin/sh
nmcli connection load "/etc/sysconfig/network-scripts/ifcfg-$1" &&
exec nmcli connection down filename "/etc/sysconfig/network-scripts/ifcfg-$1"

I've just become used to using "nmcli".  Just like I've become used to using "ip" instead
of "ipconfig".

Thanks for making me take a deeper look.