Bug 495486
Summary: | /etc/sysconfig/network is missing | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Mach <dmach> |
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-04-14 18:32:47 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
Daniel Mach
2009-04-13 12:32:32 UTC
... why would it be needed in a chroot? You don't bring up devices there. For example after I install a virtual guest via yum. I don't like that anaconda does all post-install setup and packages do not contain couple files with default values. Well, we don't set up any ifcfg-XXX files with a yum install either, so I'm not sure we should special-case this as well. Similarly, we don't configure grub during yum-based package installation either (and my, would that be gross.) I'm inclined to close this WONTIFX. If the tools we ship such as system-config-network and/or NetworkManager can't work on a yum-installed chroot and then write a proper /etc/sysconfig/network, I may reconsider. Right, but several scripts (like avahi initscript) depend on this file. example from rhel-5 after I removed /etc/sysconfig/network: /etc/init.d/avahi-daemon restart /etc/init.d/avahi-daemon: line 18: /etc/sysconfig/network: No such file or directory Erm, yes, but ... don't remove it? |