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
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.
On 12/9/18 7:03 PM, Ed Greshko wrote:
dnf info
I keep forgetting about that command. Thank you!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https
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- ??
[egreshko@acer ~]$ rpm -q network-scripts
package network-scripts is not installed
[egreshko@acer ~]$
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- ??
> [egreshko@acer ~]$ rpm -q network-scripts
> package network-scripts is not installed
>
> [egres
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- ??
[egreshko@acer ~]$ rpm -q network-scripts
package network-scripts is not installed
[egreshko@acer ~]$ ls /etc/sysconfig/network-scripts/
if
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, sin
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
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
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 NetworkMana
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 inte
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.
_
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/sys
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 fro
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
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 e
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 w
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 "if
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.
htt
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 h
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.fedor
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
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
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.
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
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
26 matches
Mail list logo
