Bug 383441
| Summary: | netconfig is removed rather than fixed with update 1 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jim Perrin <james.l.perrin> |
| Component: | system-config-network | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.1 | CC: | lmiksik, pasteur, psklenar, sdahl |
| 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: | 2014-01-31 13:18:19 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: | 1049888 | ||
|
Description
Jim Perrin
2007-11-14 21:08:58 UTC
Re-assigning to component owner... FYI, scripting can also be done with system-config-network-cmd Yes, however system-config-network-cmd has a distinct and abysmal lack of documentation. There's no manpage, there's no /usr/share/doc/ files, nothing. If you're going to recommend it for scripting, providing some documentation within the package would be helpful. Not trying to slam you for pointing something out, because you are absolutely correct, just saying that the package is not yet a suitable replacement for netconfig. The only thing that works for system-config-netork-cmd is --help, which leaves a bit to be desired for clarity.
yes - we are hosed by this too. We use the netconfig command for our
automated kickstart post-install scripts. Is there something that can
do the equiv of this now?
/usr/sbin/netconfig --device=eth0 --domain=blarg.com --hostname=${HOSTNAME}
--ip=${MYIP} --nameserver=192.0.0.1 --netmask=${M
YNETMASK} --gateway=${MYGATEWAY}
Since netconfig has been removed, it also means rc.sysinit and sys-unconfig needs to be fixed. This needs to be done as on executing sys-unconfig, rc.sysinit still calls netconf and not system-config-network-tui. Also my guess is system-config-network-xxx.rpm is not part of the base (minimal) OS install. Just ran into this issue migrating my 5.0 kickstart config to 5.1. In response to comment #5, the solution I used was: TEMPFILE=`mktemp` system-config-network-cmd -e -d | sed 's|BootProto=dhcp|BootProto=none|' \ > $TEMPFILE echo "DeviceList.Ethernet.eth0.Netmask=${MASK}" >> $TEMPFILE echo "DeviceList.Ethernet.eth0.IP=${IP}" >> $TEMPFILE echo "DeviceList.Ethernet.eth0.Gateway=${GW}" >> $TEMPFILE system-config-network-cmd -i -d -f $TEMPFILE rm -f $TEMPFILE which replaced this call to netconfig: netconfig --bootproto=none --gateway=${GW} --ip=${IP} --netmask=${MASK} thanks Chris - I will try that and comment back to this thread... It's a bit sad that a 1 line solution which worked had to be replaced by an 8 line script which uses a mostly undocumented command like system-config-network-cmd |