How can I initiate kickstart from netinstall.iso 6.0?

reppep · Post by **reppep** » 2011/07/26 20:13:21

Booting from the netinstall ISO, I get a menu with "Welcome to CentOS 6.0!" at the top, and "Press [Tab] to edit options" at the bottom. In CentOS 5 I would have hit [Space] to avoid autorunning the installer, then entered a command line like "linux ks=http://www.centos.cfg/kickstart.cfg" to pick up my Kickstart file.

I hit [Tab] and edit the pre-existing command "Install or upgrade an existing system", which starts with 'vmlinuz'. I can replace it with a line like "vmlinuz ks=http://www.centos.cfg/kickstart.cfg", which fails to open a root device and dies.

When I use a line that starts with 'linux', like "linux ks=http://www.centos.cfg/kickstart.cfg", it does nothing useful and instead simply restarts the 60-second auto-boot timer.

So what's an appropriate kickstart command for this menu? Or how can I use one?

pschaff · Post by **pschaff** » 2011/07/30 17:45:52

Welcome to the CentOS fora. Please see the recommended reading for new users linked in my signature.

Try just appending[code] ks=http://www.centos.cfg/kickstart.cfg[/code] to the end of the line.

floobit · Post by **floobit** » 2011/09/19 23:23:20

I also have the same issue. This solution does not work for the install DVD (CentOS-6.0-x86_64-LiveDVD.iso). Appending this line to the end of an existing command seems to do nothing. I would guess that the pre-existing line codes for a routine associated with the intended purpose. Thus, telling the vmlinuz kernel to go look at a ks file after doing, for instance, a text-install defeats the purpose of using a ks (not having to do a text-install). I have tried deleting some options from the text-install package and appending ks=http://somedomain/myks.ks. These have all failed to even look for a ks file. I also pressed to get to the

[font=Courier]boot: [/font]

prompt, typing

[font=Courier]linux ks=http://somedomain/myks.ks[/font]

here fails as well (unknown kernel "linux").

I'm sure this is something easy; CentOS could not have just disabled kickstart functionality. Additionally, the documentation for Red Hat 6 suggests the same documentation as in RHEL 5 and CentOS 5: "linux ks=http://somedomain/myks.ks. Unfortunately, there is no CentOS 6 documentation yet.

Failing a tested protocol for making kickstart work, does anyone know of an explanation for the iso-based boot options for vmlinuz? I cannot find one, but I wouldn't mind looking through it to solve this.

Thanks

c00p · Post by **c00p** » 2011/09/29 15:17:41

This solution worked for me.

Thanks

CentOS