Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

creating vmlinuz and initrd for distribution media

2 views
Skip to first unread message

Velocity

unread,
Oct 10, 2007, 9:55:41 AM10/10/07
to
I am trying to learn to create the vmlinuz and initrd that are shipped
on installation DVD of Fedora like FC6,FC3 Suse etc etc or any other
linux distribution. Which when loaded by isolinux and after asking for
options starts installation on a system
1) What should I look into any specific documentation
2) how does it work without system.map file
3) how are these kernel and initrd different from the ones found in /
boot
folder of a system in which linux is installed that are specific to a
particular system and load only the specific drivers .

Hugoi please do not reply your replies are out of the subject and
useless.

Velocity

unread,
Oct 24, 2007, 2:19:19 PM10/24/07
to
Ok so I got what was actually I was searching for I am posting this as
a reference if some one by mistake read this and is willing to do same
as I did with some other distribution after reading this link go here
Actually what I did was
#gzip -dc initrd | cpio -id

or you can also do
# mkdir /tmp/init
# zcat /boot/initrd.img > /tmp/initrd.img
# mkdir init
# mount -o loop initrd.img init

Change the files u need inside the init dir ..

# umount init
# gzip -9 initrd.img
# mv initrd.img.gz /boot/initrd.img


you copy the initrd from the distribution DVD and the one on your boot
folder inside the system
and do as root
gzip -dc initrd | cpio -id
you will see a lot of directories and some executables
do this for both the initrd's the one on boot folder and the one in
installation media
the difference comes in
modules which they load
I am not sure about the udev or devfs which the initrd on installation
cd or dvd does .
Actually the difference comes in the init script which you see for
both the initrd's the init extracted from the initrd of installation
cd or dvd
has a linuxrc script which starts installaion by calling the installer
which in my case was yast and in case of fedora is anaconda and debian
has its own.
here is one more link
http://www.mjmwired.net/kernel/Documentation/filesystems/ramfs-rootfs-initramfs.txt#252
I have tried to explain what ever possible now this should help you.

0 new messages