Re: [master] Get crashkernel arguments from the crashkernel code dynamically.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 05/17/2012 10:26 AM, Chris Lumens wrote:
>> diff --git a/pyanaconda/ b/pyanaconda/
>> index cfbd152..a45ae22 100644
>> --- a/pyanaconda/
>> +++ b/pyanaconda/
>> @@ -1631,6 +1631,11 @@ class GRUB2(GRUB):
>>      stage2_raid_levels = [mdraid.RAID0, mdraid.RAID1, mdraid.RAID4,
>>                            mdraid.RAID5, mdraid.RAID6, mdraid.RAID10]
>> +    def __init__(self, storage):
>> +        super(GRUB2, self).__init__(self, storage)
>> +        self.boot_args.add("$([ -x /usr/sbin/rhcrashkernel-param ] && "\
>> +                            "/usr/sbin/rhcrashkernel-param)")
>> +
>>      # XXX we probably need special handling for raid stage1 w/ gpt disklabel
>>      #     since it's unlikely there'll be a bios boot partition on each disk
> Where does rhcrashkernel-param come from?

kexec-tools, which is an optional component in comps in the base group in
fedora, and I don't know what in rhel yet.  Here's the current commit:;a=commitdiff;h=ca94c80a91400e9ce95bb56023ca4391d5b41d85

They tell me they're going to remove ".sh" from it, so I've coded it without
it, but we've got the -x check so it just won't call it if they don't fix the


All parts should go together without forcing. You must remember that
the parts you are  reassembling were disassembled by you.  Therefore,
if you can't get them together again, there must be a reason. By all
means, do not use a hammer.
		-- IBM maintenance manual, 1925

Anaconda-devel-list mailing list

[Home]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Red Hat 9 Bible]     [Fedora Bible]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

Powered by Linux