On 12/02/2009 05:12 PM, Chris Lumens wrote:
>>> So, I'd like to be able to test mdadm changes before checking them into
>>> CVS and building them in rawhide. To do that, I'd like to be able to
>>> spin a rescue CD from my local rawhide mirror and boot into it on my
>>> test box. Can someone tell me, in very simple terms a kernel engineer
>>> can understand ;-), how I go about creating my own rescue CD images?
>>>
>>> (Please keep me on the Cc: since I'm not subbed to the list, thanks)
>>
>> So, to not answer your question ;), a better thing to do here is probably
>> for us to make sure that wherever we're calling mdadm checks
>> /tmp/updates correctly (there appear to be a couple of places that
>> don't do this right now) and then for you to make an updates image[1]
>> with the new mdadm in it, and specify a url to the image on the command
>> line.
>
> mdadm (and a bunch of other programs) is run by
> iutil.execWithPulseProgress, which appears to be using os.execvp, which
> in turn uses $PATH to find the command. /tmp/updates should be in the
> $PATH due to loader putting it there. Sounds like as long as the new
> mdadm is in /tmp/updates, everything is already in place.
I was more thinking of:
pjones4:~/devel/hosted.fp.o/anaconda$ git grep '/mdadm' .
70-anaconda.rules:IMPORT{program}="$env{ANACBIN}/mdadm --detail --export $tempnode"
70-anaconda.rules:ENV{ID_FS_TYPE}=="linux_raid_member", IMPORT{program}="$env{ANACBIN}/mdadm --examine --export $tempnode"
70-anaconda.rules:ENV{ID_FS_TYPE}=="isw_raid_member", IMPORT{program}="$env{ANACBIN}/mdadm --examine --export $tempnode"
loader/shutdown.c: ignore = system("/sbin/mdadm --wait-clean --scan");
(lots of other stuff trimmed)
--
Peter
I'd like to start a religion. That's where the money is.
-- L. Ron Hubbard to Lloyd Eshbach, in 1949;
quoted by Eshbach in _Over My Shoulder_.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
