Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Thanks, David
David Hrbáč wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Personally, I just use the buildinstall process in /usr/lib/anaconda-runtime
However, if you look at that script and follow it through into mkimages (and mk-images.x86 or mk-images-.x86_64) it will tell you how buildinstall issues the commands.
Thanks, Johnny Hughes
On Oct 15, 2007 5:49 AM, Johnny Hughes johnny@centos.org wrote:
David Hrbáč wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Personally, I just use the buildinstall process in /usr/lib/anaconda-runtime
However, if you look at that script and follow it through into mkimages (and mk-images.x86 or mk-images-.x86_64) it will tell you how buildinstall issues the commands.
Thanks, Johnny Hughes
Did you ever figure this command out? I'm stuck doing the same thing for FC4. I'm going crazy reading through mk-images scripts.
- G.
On Oct 15, 2007 2:09 PM, David Hrbáč hrbac.conf@seznam.cz wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Maybe you could extract original initrd image, replace its components with yours and then rebuild the initrd ! gzip, mount -o are your friend
Thanks, David _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Alain Spineux napsal(a):
On Oct 15, 2007 2:09 PM, David Hrbáč hrbac.conf@seznam.cz wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Maybe you could extract original initrd image, replace its components with yours and then rebuild the initrd ! gzip, mount -o are your friend
Not anymore, use buildinstall. D.
On Nov 13, 2007 5:49 AM, David Hrbáč hrbac.conf@seznam.cz wrote:
Alain Spineux napsal(a):
On Oct 15, 2007 2:09 PM, David Hrbáč hrbac.conf@seznam.cz wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Maybe you could extract original initrd image, replace its components with yours and then rebuild the initrd ! gzip, mount -o are your friend
Not anymore, use buildinstall. D.
David is right... Through a series of commands: cpio, mount, g(un)zip, zcat, loopack devices, dd, mkfs.*, etc. I was able to mount, extract and otherwise rebuild the the initrd. Sadly, after almost two months of toying with it, I got to a point where I had my newly built kernel booting, my newly minted initrd loading and a plethora of new drivers loaded and ready for use. BUT, after the kernel finished booting, the hand-off to init (which is symlinked to loader/anaconda) would never happen. Although I was never able to figure-out why, I sent some messages to the Fedora Release Engineering group. Jesse Keating over there pointed me back up the chain to buildinstall as well. Although cooking an _entier_ distro was overkill, using the resulting diskboot.img and stage2.img worked great. Seemingly, you can't shortcut this route either - mk-images/.i386 really does the work I need but taking it out of context is _way_ more trouble then it's worth. In any case, mystery solved!
Thanks for the help guys! - G.
P.S.> It appears that the manual initrd rebuild used to work in FC2, don't know about FC3, and won't work for FC4+... but this is just speculation from my readings.
On Wed, 2007-11-14 at 13:56 -0800, semi linux wrote:
On Nov 13, 2007 5:49 AM, David Hrbáč hrbac.conf@seznam.cz wrote:
Alain Spineux napsal(a):
On Oct 15, 2007 2:09 PM, David Hrbáč hrbac.conf@seznam.cz wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
Maybe you could extract original initrd image, replace its components with yours and then rebuild the initrd ! gzip, mount -o are your friend
Not anymore, use buildinstall. D.
David is right...
Not necessarily. For the changes I make I find the following sufficient:
mkdir initrd; cd initrd gunzip -c --suffix '.img' /boot/initrd-abc.img | cpio -i
and
find . -print | cpio -c -o | gzip -c9 >/boot/initrd-xyz.img
Jim
On Thu, 2007-11-15 at 08:38 +0000, Jim Wight wrote:
On Wed, 2007-11-14 at 13:56 -0800, semi linux wrote:
On Nov 13, 2007 5:49 AM, David Hrbáč hrbac.conf@seznam.cz wrote:
Alain Spineux napsal(a):
On Oct 15, 2007 2:09 PM, David Hrbáč hrbac.conf@seznam.cz wrote:
Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media.
<snip>
Not necessarily. For the changes I make I find the following sufficient:
mkdir initrd; cd initrd gunzip -c --suffix '.img' /boot/initrd-abc.img | cpio -i
and
find . -print | cpio -c -o | gzip -c9 >/boot/initrd-xyz.img
Jim
It's been awhile, but last time I did it, Jim's basic scenario is what I used. I don't recall if my cpio params were exactly the same, but after the unzipping step, "file <filename>" will give you the clues to the parameters to cpio.
<snip sig stuff>
-- Bill
-
Alain Spineux -
David Hrbáč -
Jim Wight -
Johnny Hughes -
semi linux -
William L. Maltby