Re: how to 'rip apart' a rpm.

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


On Monday 17 May 2010, Ed Greshko wrote:
>On 05/18/2010 10:42 AM, Gene Heskett wrote:
>> On Monday 17 May 2010, Ed Greshko wrote:
>>> On 05/18/2010 09:09 AM, Tom H wrote:
>>>> On Mon, May 17, 2010 at 7:49 PM, Rick Stevens <[email protected]> wrote:
>>>>> On 05/17/2010 02:12 PM, Gene Heskett wrote:
>>>>>> Clarify here: I can do all that as the user. What I can't do, until
>>>>>> somebody decides to fix mkinitrd, is to run it as the user. That is
>>>>>> my specific bitch. And I think its perfectly valid. mkinitrd simply
>>>>>> will not run for anybody but root.
>>>>> And this is a bad thing? I, for one, don't want some low-level user
>>>>> installing a kernel on my machines. I don't want them installing
>>>>> ANYTHING that's global.
>>>> +1
>>> I get the feeling that Gene isn't talking about the actual installation
>>> of the initrd image.
>> Feeling Ed?  I have written this very plainly, several times.  But W/O
>> exceptions here, everyone is assuming that I am installing a kernel from
>> fedora, which is as yet useless on this machine.  I have an rv610 based
>> ATI video card, and it has been doing an extremely obnoxious fits of self
>> blanking anytime something touches the right edge of the screen since I
>> built this box about 2 years ago now.  ONLY the 2.6.34(-rcN), and now
>> 2.6.34 final have the drm fixes that stop that.  The CCFL's in this
>> monitor have somehow survived all the flashing, but the power supply that
>> drives them has had to be rebuilt, the caps went south.
>Yes <sarcasm>*feeling*<\sarcasm>.   I didn't want to be obnoxious, this
>time, and write something like..."Didn't you morons read what Gene has
>written".  :-)

My next message, if no one had understood, probably would have used similar 
phraseology. ;-)

>> And with 2.6.34 final, I now have a pulseaudio that is 99% usable, not
>> lost in stuttering, clicking and popping.
>>> I think he is wondering why something like...
>>> mkinitrd /tmp/xxx
>> But that kernel will not run my video card well enough to be able to
>> scroll thru an email message and read it.  For every 1 line text scroll
>> attempted, its a good long second to repaint the screen, excruciatingly
>> distracting.
>Which is why I said..."something *like*".  :-)

NP Ed, thanks.

>>> needs root privileges to run.   Is there anything inherently wrong is
>>> expecting that to work?
>> Exactly Ed.  My question precisely.
>I think your answer is covered by the emergence of dracut.
Looks as if that might be the answer, but as usual, the manpage that goes 
with it isn't as clear and concise as I'd like, so at some point I'm going to 
be back asking how to do this mkinitrd command line:

mkinitrd -f initrd-$VER.img $VER

Where $VER is of course a variable local to the script, and used precisely 
because uname -r will not return the kernel version being built, so I have to 
supply the 2.6.34(-rcN) data in my script.

Using dracut.  What would duplicate that exact function shown above in dracut 
syntax?  Do I have to build a directory tree as a text file and feed it via 
some option like the manpage only half discusses?.  mkinitrd does this 

Thanks Ed.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
While anyone can admit to themselves they were wrong, the true test is
admission to someone else.
users mailing list
[email protected]
To unsubscribe or change subscription options:

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux