Re: [PATCH] insert_module -> insmod

[David Cantrell <dcantrell redhat com>]

Jon Masters wrote:
> On Mon, 2008-12-01 at 12:03 -1000, David Cantrell wrote:
>> ---
>>  loader/linuxrc.s390 |    8 ++++----
>>  1 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/loader/linuxrc.s390 b/loader/linuxrc.s390
>> index 2643ffe..f6d3f42 100644
>> --- a/loader/linuxrc.s390
>> +++ b/loader/linuxrc.s390
>> @@ -263,10 +263,10 @@ if [ -r /sys/firmware/ipl/ipl_type ]; then
>>  			case $do_cd_install in
>>  				y|Y|[Yy][Ee][Ss])
>>  					# set up FCP cdrom here
>> -					insert_module qdio$LO
>> -					insert_module scsi_mod$LO
>> -					insert_module scsi_transport_fc$LO
>> -					insert_module zfcp$LO
>> +					insmod qdio$LO
>> +					insmod scsi_mod$LO
>> +					insmod scsi_transport_fc$LO
>> +					insmod zfcp$LO
>>  					CD_DEVICE="`cat /sys/firmware/ipl/device`"
>>  					WWPN="`cat /sys/firmware/ipl/wwpn`"
>>  					LUN="`cat /sys/firmware/ipl/lun`"
> 
> So is s390 also using module-init-tools now then? I haven't looked at it
> in a while since the last time it blew up on me in RHEL5 over a rogue
> kernel patch someone had submitted :)

Did s390 ever use something other than the standard kernel module utils?
 The insert_module command was a wrapper function that IBM had written
for debugging purposes.  The calls were left in the first iteration of a
patch from them.

-- 
David Cantrell <dcantrell redhat com>
Red Hat / Honolulu, HI