Re: how to 'rip apart' a rpm.

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

 



On 05/17/2010 02:12 PM, Gene Heskett wrote:
> On Monday 17 May 2010, Bill Davidsen wrote:
>> Gene Heskett wrote:
>>> On Saturday 15 May 2010, Kevin J. Cummings wrote:
>>>> On 05/15/2010 11:22 AM, reg@xxxxxxx wrote:
>>>>> I want to look at the individual files in a src rpm.
>>>>> How do I 'rip it apart' ??
>>>>
>>>> rpm -qpl src.rpm
>>>>
>>>> should show you a list of the files in the RPM.  When you "install" it,
>>>> they get installed in your rpmbuild sandbox under:  SPECS and SOURCES
>>>> subdirectories.
>>>>
>>>>> Doing an install doesnt seem to be the answer, It does something, but I
>>>>> have no idea where the bits and pieces are going.
>>>>> They are NOT in /usr/src/redhat nor in /root/rpmbuild.
>>>>
>>>> You really shouldn't be playing with source RPMs as root.  Look in your
>>>> user RPM sandbox:
>>>
>>> Then I'd suggest that doing so as a user be made possible.  I think its
>>> asinine that I am prevented from building my kernels as a user, simply
>>> because mkinird cannot be made to run if you are not root.
>>
>> You don't need mkinitrd to build a kernel, you need it to *install* a
>> kernel, two different operations. After you do the make you can make
>> modules_install and install with the -n option (if you wish) to inspect
>> what they will do, or just "su -c "make modules_install modules"
>> after the build is done.
>
> 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.

When you get to the point where you're installing something that will
affect all the users on the machine or the operation of the machine
itself, only an administrator (e.g. "root") should be permitted to do
so.  This is the whole point of system security and tools such as "su"
and "sudo".
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, C2 Hosting          ricks@xxxxxxxx -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-           If it's stupid and it works...it ain't stupid!           -
----------------------------------------------------------------------
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux