Bug 480578

Summary:	move the classic network configuration scripts out of the initscripts package
Product:	[Fedora] Fedora	Reporter:	Dan Horák <dan>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	notting, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-19 19:22:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	471381

Description Dan Horák 2009-01-19 09:04:22 UTC

With the recent development that makes NetworkManager the default mechanism for network configuration I would like to move the classic network configuration scripts out of the initscripts package into a separate package with me as the submitter/owner of the new package.

affected files:
/etc/rc.d/init.d/network
/etc/sysconfig/network-scripts/*
related part of sysconfig.txt

Comment 1 Bill Nottingham 2009-01-19 19:21:50 UTC

To the best of my (occasionally fuzzy) recollection:

- you've never submitted patches for the scripts
- you've never filed bugs against them
- you've never applied even for access to upstream git
  (of course, the first two would be a prerequisite for that)

Ergo, no.

Comment 2 Bill Nottingham 2009-01-19 19:22:30 UTC

Without a usage case as to what this would accomplish/serve, I'm not seeing a big reason why this would need to be done.

Comment 3 Dan Horák 2009-01-19 22:30:51 UTC

Well, I have got the impression during the previous few months that this feature will be depreciated in the really near future because we have NM. So I am glad to see you are still ready to maintain the scripts as a part of initscripts. But please let me know, when you would like to drop them out.

Comment 4 Dan Horák 2009-01-20 07:59:05 UTC

(In reply to comment #1)
> To the best of my (occasionally fuzzy) recollection:
> 
> - you've never submitted patches for the scripts
> - you've never filed bugs against them
> - you've never applied even for access to upstream git
>   (of course, the first two would be a prerequisite for that)
> 
> Ergo, no.

Are those really required for an overtake of a to-be-abandoned feature? I don't think so.

Comment 5 Bill Nottingham 2009-01-20 18:06:53 UTC

It's a maintained subsystem, so... yes.

What sorts of changes do you want to make?

Comment 6 Dan Horák 2009-01-20 20:44:13 UTC

No changes are planned, it works well AFAIK. I (and the server and other people) just want to make sure it survives, because its role is non-replaceable due the number of variants it allows to configure and no resource usage.

But the split would show a distinction between classic and NM network setups.