Bug 70648
Summary: | no place for wireless config parameters | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | david d zuhn <zoo> | ||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||
Status: | CLOSED DEFERRED | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | limbo | CC: | rvokal | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2002-08-14 15:47:15 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: | |||||||
Attachments: |
|
Description
david d zuhn
2002-08-03 01:01:03 UTC
Created attachment 68666 [details]
My /etc/sysconfig/wireless example
This is done in /etc/sysconfig/network-scripts/ifcfg-<whatever> I think this is a serious regression in functionality. Under the older system (7.[0123]), I had a mechanism that was independent of what the actual interface name was, as it was based on the card type (in /etc/pcmcia/wireless.opts or whatever the exact file name was). The fact that ifup-wireless is a separate piece from the remainder of the ifup- mechanisms is a clear sign that its possible for a wireless card to be on any interface and separated from some of the basic networking infrastructure. I like the idea that this networking info is in /etc/sysconfig/network-scripts now. The problem now is that my wireless interface changes from time to time, because sometimes I'm using a wired connection at the same time. If ifup-wireless would be interface independent by moving the wireless config info out of ifcfg-*, I could easily be running with or without additional interfaces, regardless of the order that I installed the network cards into this machine. Now if there were a simple non-code file to edit to place these wireless config parameters into, I'd be interface independent. This is probably best done by changing the association to something other than ethX device names; this is a non-trivial change. |