Re: how to 'rip apart' a rpm.

Gene Heskett wrote:
On Monday 17 May 2010, Mikkel wrote:
On 05/17/2010 04: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.
Considering that mkinitrd is part of the install procedure, and not
part of the build procedure, why is that a problem? The initrd is
system specific, so it does not really make sense to run it before
the install stage. And you need to be root to do the install anyway.

Mikkel

Why? In terms of the install, there is no reason why the perms can't be
changed so the user can do it all, except the mkinitrd, which in my scripts
leaves the initrd-version.img sitting it the src tree to be copied as a
separate line in my 'makeit' script.

The kernel and the initrd once it built, can be installed by the user if the
perms had been set to the users ownership because he built them.

Gene, let me say this one more way. mkinitrd is not part of the build, it is
part of the install. The output of the build can be moved to any similarly
configured machine and installed, but the mkinitrd needs to know the hardware
configuration of the machine where it will run.

You building and installing on the same machine is a special case, but in
general the built kernel is portable and the mkinitrd is part of the install and
must match the final machine on which the kernel boots.

And install must be done as root...

--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
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

Relevant Pages

  • Re: Kernel Includes versus Modules and Initrd with SATA on VIA SP13000
    ... >> You do not need it if driver is built in. ... It has an effect on mkinitrd; it was your problem, ... install if you know what you are doing. ...
    (comp.os.linux.setup)
  • Re: f10dvd installs but wont boot
    ... Install the update mkinitrd and remake your initrd ... You would have to get a boot up and into a virtual console. ... yum update <<< will update all installed pkgs ... This would take some time to install all of the updates. ...
    (Fedora)
  • Re: mkinitrd on missing list?
    ... should be able to install yaird. ... My question really attempted to see if you had considered using some other distro for your needs - like openSUSE where everything you need to compile your own kernel is most readily available by simply ticking a box or two to have the necessary files installed (like kernel-source, mkinitrd, etc etc etc). ...
    (Ubuntu)
  • Re: creating custom initrd [solved]
    ... Shucks, <blush> ... I only did what I always do, check whether it's a script, and if it ... A bit weird that a file like this is not present after you install ... mkinitrd though. ...
    (Fedora)
  • Re: how to rip apart a rpm.
    ... to do this mkinitrd command line: ... .old, and then make a new one, right in the source tree. ... Turns out that just to satisfy this, I had to install the dhcp-client ... while because it fixes video problems with the older kernels, ...
    (Fedora)