<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9"> <TITLE>RedHat Linux KickStart HOWTO: Installation itself</TITLE> <LINK HREF="KickStart-HOWTO-8.html" REL=next> <LINK HREF="KickStart-HOWTO-6.html" REL=previous> <LINK HREF="KickStart-HOWTO.html#toc7" REL=contents> </HEAD> <BODY> <A HREF="KickStart-HOWTO-8.html">Next</A> <A HREF="KickStart-HOWTO-6.html">Previous</A> <A HREF="KickStart-HOWTO.html#toc7">Contents</A> <HR> <H2><A NAME="s7">7. Installation itself</A></H2> <P> <P>Boot the to-be-installed machine off your RedHat boot floppy as usual, but instead of pressing <CODE>RETURN</CODE> at the <CODE>SYSLINUX</CODE> prompt, type <CODE>linux ks</CODE>. <P> <P>If you're lucky, this will be all you have to type! <P> <P>If you customised your RedHat boot floppy as outlined above, you won't even need to do this bit :-) <P> <P>Since we're really just automating the normal steps involved in a RedHat installation, the normal dialogs may appear if/when KickStart gets confused about what to do next. The most likely case is that your network interface won't be detected automatically, and you'll be prompted for its IRQ and I/O address space. KickStart tends to need help for ISA bus cards, but detects PCI bus cards automatically. <P> <P>You can keep an eye on what KickStart is doing by by switching virtual consoles as usual: <P> <P> <UL> <LI> Alt-F1 - installation dialog</LI> <LI> Alt-F2 - shell prompt</LI> <LI> Alt-F3 - install log (messages from install program)</LI> <LI> Alt-F4 - system log (messages from kernel, etc.)</LI> <LI> Alt-F5 - other messages</LI> </UL> <P> <P> <P> <HR> <A HREF="KickStart-HOWTO-8.html">Next</A> <A HREF="KickStart-HOWTO-6.html">Previous</A> <A HREF="KickStart-HOWTO.html#toc7">Contents</A> </BODY> </HTML>
