{"id":1736,"date":"2014-05-29T12:48:53","date_gmt":"2014-05-29T10:48:53","guid":{"rendered":"http:\/\/www.oradba.ch\/?p=1736"},"modified":"2014-06-10T12:50:32","modified_gmt":"2014-06-10T10:50:32","slug":"avdf-installation-iso","status":"publish","type":"post","link":"https:\/\/www.oradba.ch\/wordpress\/2014\/05\/avdf-installation-iso\/","title":{"rendered":"AVDF installation ISO"},"content":{"rendered":"

Due to some problems during the installation of Oracle Audit Vault and Database Firewall 12.1.2 (see AVDF installation fails on HP server with Smart Array Disk Controller<\/a>), I’ve looked at the AVDF ISO image and its kickstart setup.<\/p>\n

AVDF 12.1.2 is based on Oracle Enterprise Linux 5.9. To setup or upgrade AVDF it is required to boot the system from the AVDF ISO. The menu from the ISOLINUX bootloader allows simple selection of installation, upgrade, or memory test.
\n\"AVDF_12.1.2.0.0_setup01\"<\/a>
\nAs you can see in the picture, it is also possible to specify the boot options directly in the prompt.
\nThe boot loader menu itself is configured in the isolinux.cfg<\/em> file. Looking at the file reveals how an installation respectively an upgrade will be started. Both use their own kickstart file. <\/p>\n

\r\ndefault memtest86\r\n\r\nprompt 1\r\ndisplay boot.msg\r\n\r\nF1 boot.msg\r\n\r\nlabel install\r\nkernel vmlinuz\r\nappend noipv6 initrd=initrd.img ramdisk_size=8192 ks=file:\/kickstart\/kickstart.cfg noshell\r\n\r\nlabel upgrade\r\nkernel vmlinuz\r\nappend noipv6 initrd=initrd.img ramdisk_size=8192 ks=file:\/kickstart\/update.cfg noshell\r\n\r\nlabel memtest86\r\nkernel memtest\r\nappend -<\/pre>\n
A special note, Oracle has switched off the shell on console 2 (alt-F2) with noshell<\/em>. If you want to use console 2 during the installation, you have to enter the boot options directly on the prompt. But enabling the shell on console 2 leaves the system vulnerable to root access. It should not be left unattended when such a shell exists. An example can be seen in the picture above.<\/p>\n
The kickstart file is part of the initrd.img which is used during the boot process. But this image needs first to be unpacked. The image is some kind of a gzipped cpio archive.<\/p>\n
Rename and unpack the image:<\/p>\n
\r\nmv initrd.img initrd.gz\r\ngunzip initrd.gz\r\n<\/pre>\n
So extract the files from initrd using cpio:<\/p>\n
\r\nmkdir initrd_work\r\ncd initrd_work\r\ncpio -id < ..\/initrd\r\n31570 blocks\r\n<\/pre>\n
Now we can see the content of the initrd.img file and in particular the kickstart files.<\/p>\n
\r\nls\r\nbin etc kickstart proc selinux tmp\r\ndev init modules sbin sys var\r\n<\/pre>\n
References<\/h3>\n
Further information on this topic.<\/p>\n