Why 'CTC' over 'ctc'? Other system tools expect the NETTYPE variable in the
ifcfg file on s390x to contain 'ctc' or 'lcs' or 'qeth' (possibly other
values), so we should probably keep it lowercase.
+
+ def clear(self):
+ IfcfgFile.clear(self)
+ if self.iface.startswith('ctc'):
+ self.info["TYPE"] = "CTC"
+
def __str__(self):
s = ""
s = s + "DEVICE=" + self.info["DEVICE"] + "
"
@@ -263,10 +276,44 @@ class NetworkDevice(SimpleConfigFile):
Why 'CTC' over 'ctc'? Other system tools expect the NETTYPE variable in
the
ifcfg file on s390x to contain 'ctc' or 'lcs' or 'qeth' (possibly other
values), so we should probably keep it lowercase.
I just keep doing what we used to do. I can commit the change
to lowercase as separate patch (assuming it acked by you).
We were writing CTC to the NETTYPE variable? That does not seem right. A
separate patch to make sure the NETTYPE is lowercase would be a good thing, I
think.
Radek
- def __init__(self, dev):
- self.info = { "DEVICE" : dev }
- if dev.startswith('ctc'):
- self.info["TYPE"] = "CTC"
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-06-2010, 04:28 PM
Steffen Maier
Use IfcfgFile class to back NetworkDevice objects (#520146)
On 05/06/2010 04:59 PM, David Cantrell wrote:
> On Tue, 4 May 2010, Radek Vykydal wrote:
>>> On Tue, 27 Apr 2010, Radek Vykydal wrote:
>>>>
>>>> -class NetworkDevice(SimpleConfigFile):
>>>> +class NetworkDevice(IfcfgFile):
>>>> +
>>>> + def __init__(self, dir, iface, logfile='/tmp/ifcfg.log'):
>>>> + IfcfgFile.__init__(self, dir, iface)
>>>> + self.logfile = logfile
>>>> + if iface.startswith('ctc'):
>>>> + self.info["TYPE"] = "CTC"
>>>
>>> Why 'CTC' over 'ctc'? Other system tools expect the NETTYPE variable
>>> in the
>>> ifcfg file on s390x to contain 'ctc' or 'lcs' or 'qeth' (possibly other
>>> values), so we should probably keep it lowercase.
>>
>> I just keep doing what we used to do. I can commit the change
>> to lowercase as separate patch (assuming it acked by you).
>
> We were writing CTC to the NETTYPE variable? That does not seem right. A
> separate patch to make sure the NETTYPE is lowercase would be a good
> thing, I think.
Last time, I checked, there are no consumers of what this code fragment
initializes. Linuxrc.s390 sets NETTYPE in the ifcfg file (previously it
used to be loader) and anaconda just copies it over to /mnt/sysimage.
Here it says just TYPE and I have no idea what this was used for.
Looking at the scripts in /etc/sysconfig/network-scripts/ it looks like
there is only "Bridge" or "Tap" for TYPE. s390x network devices use only
NETTYPE (and optionally DEVICETYPE, but that can be derived from NETTYPE
[https://bugzilla.redhat.com/show_bug.cgi?id=507214#c7]).
I guess we can just leave it as is, in order not to risk breaking some
old stuff.
My 2 ct,
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-06-2010, 09:00 PM
David Cantrell
Use IfcfgFile class to back NetworkDevice objects (#520146)
Why 'CTC' over 'ctc'? Other system tools expect the NETTYPE variable
in the
ifcfg file on s390x to contain 'ctc' or 'lcs' or 'qeth' (possibly other
values), so we should probably keep it lowercase.
I just keep doing what we used to do. I can commit the change
to lowercase as separate patch (assuming it acked by you).
We were writing CTC to the NETTYPE variable? That does not seem right. A
separate patch to make sure the NETTYPE is lowercase would be a good
thing, I think.
- def __init__(self, dev):
- self.info = { "DEVICE" : dev }
- if dev.startswith('ctc'):
- self.info["TYPE"] = "CTC"
Last time, I checked, there are no consumers of what this code fragment
initializes. Linuxrc.s390 sets NETTYPE in the ifcfg file (previously it
used to be loader) and anaconda just copies it over to /mnt/sysimage.
Here it says just TYPE and I have no idea what this was used for.
Looking at the scripts in /etc/sysconfig/network-scripts/ it looks like
there is only "Bridge" or "Tap" for TYPE. s390x network devices use only
NETTYPE (and optionally DEVICETYPE, but that can be derived from NETTYPE
[https://bugzilla.redhat.com/show_bug.cgi?id=507214#c7]).
I guess we can just leave it as is, in order not to risk breaking some
old stuff.
That's probably fine then. I was still thinking something lurking in
/etc/sysconfig/network-scripts might still use NETTYPE.