From: Harald Hoyer Date: Wed, 22 Sep 2010 12:33:10 +0000 (+0200) Subject: documentation update X-Git-Tag: 008~125 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=90ccb5efe7775e11c312c6ac68ffe5f09d506bf2;p=thirdparty%2Fdracut.git documentation update --- diff --git a/dracut.xml b/dracut.xml index 9381324a8..3532794a8 100644 --- a/dracut.xml +++ b/dracut.xml @@ -250,8 +250,8 @@ overlay/ On a Red Hat Enterprise Linux or Fedora system, this means, you have to install the dracut-network rpm package: # yum install dracut-network The resulting initramfs image can be served by a boot manager residing on your local hard drive or it can be served by a PXE/TFTP server. - How to setup your PXE/TFTP server can be read here: - blah, blub.... + How to setup your PXE/TFTP server can be found in the Red Hat Enterprise Linux Storage Administration Guide http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ + If you specify rd.ip=auto on the kernel command line, then dracut asks a dhcp server about the ip adress for the machine. The dhcp server can also serve an additional root-path, which will set the root device for dracut. With this mechanism, you have static configuration on your client machine and a centralized boot configuration on your TFTP/dhcp server. If you can't pass a kernel command line, then you can inject /etc/cmdline, with a method described in the section "Injecting custom files".