One day I was approached by a fellow 2nd year computer and tell me if he could help with a Linux installation. I am still a rookie, I have 2 years using Linux as a workstation, but I can share as little experience with students of lower classes. I decided to help, installation was a total ... I did not know was that ....
... The installation had the following conditions:
- LAN Boot Install or REDHAT FEDORA (the same grass ...)
Basically, they wanted a PC serve as a source of installing a fedora or redhat-one (or more PCs) could be installed from that computer.
First, never in my life had done an installation of an operating system for LAN boteandolo, also red-hat industry is not to my liking (personal preference, nothing more ...).
Well, I had committed so ... to be documented. Reading some blogs, the solution was to perform an installation by PXE. I will not explain in detail that is PXE, since management is not the issue, but I will explain the steps I took to make this possible.
server machine: Compaq running Zenwalk v3117la serve
Distribution: Fedora (DVD)
First prepare the site containing the files that will allow the boot, thus create a folder called "tftpboot" in the root directory:
# cd /
# mkdir tftpboot
Now , mounted DVD and copy the files initrd.img and vmlinuz found in the images folder in the folder you just created. For my case, the DVD will assign a / dev / dvd and will ride on the folder / media / dvd
# mount / dev / dvd / media / dvd
# cd / media / dvd / images
# cp initrd.img / tftpboot
# cp vmlinuz / tftpboot
Ready, Copiapo pxelinux.0 file folder / tftpboot. This file can be found in the / usr / lib / syslinux / (if you have installed) or you can download it from here:
http://www.kernel.org/pub/linux/utils/b oot / syslinux/syslinux-3.11.tar.gz
I had installed, so, I copy:
# cd / usr / lib / syslinux pxelinux.0
# cp / tftpboot
Then create a folder called pxelinux.cfg within the tftpboot folder. Later in the folder just created a file called default add and write in some instructions:
# cd / tftpboot # mkdir pxelinux.cfg
# cd # vim default
pxelinux.cfg
The instructions are:
default prompt 1 timeout 1000
fedora fedora label
kernel vmlinuz append initrd = initrd.img ramdisk_size = 9216 noapic acpi = off
Then, you must configure some services on the server machine that will . One is DHCP (remember that the client machine will boot over the network and this service will assist in the configuration of the network) with this dynamic IP will give the client machine. Obviously, they must ensure that packets for dhcp (dhcpd) are installed. Editarmeos To configure the dhcpd.conf file that (in most distributions) is in the folder / etc. Use the editor that best suits them, I use vim.
vim / etc / dhcpd.conf
The configuration file for this service shall contain the following lines:
default-lease-time 2592000;
max-lease-time 2592000;
ddns -update-style ad-hoc;
ddns-updates on;
allow bootp;
allow booting;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.2 192.168.2.5;
option routers 192.168.2.1;
option broadcast-address 192.168.2.255;
option domain-name-servers 192.168.2.1;
option root-path "/ tftpboot";
filename "pxelinux.0"}
DVD
As we have already assembled, we can create a symbolic link from the DVD to the folder / tftpboot. The other would create a DVD ISO and create a symbolic link to the ISO, so the disc drive will thank you = P.
# cd / media
DVD # ln-s / tftpboot / DVD
and simplify life, share the DVD with http. Nomas need to install the apache web server and edit its configuration file located in / etc / apache / httpd.conf and is called by adding the following lines:
Options Indexes FollowSymLinks AllowOverride none
Allow from all
Alias \u200b\u200b/ fedora / / tftpboot / DVD /
Ready, start all services: http, dhcpd, etc.
With this, should to view DVD files accessed via web to the machine. In this case, was configured with the IP 192.168.2.1 and writing files should be viewed in a browser " http://192.168.2.1/fedora/ "
Well, for me it worked by trying a crossover cable between Servicor and the client machine where the latter should be enabled for network boot.
I hope they can, otherwise, the links are where I found the information:
http://p0ns.org/blog/2006/05/09/instalar-fedora-core-5-por -red-local-not-use-the-cds /
http://www.uberum.com/informatica/instalacion-remota-de-un-fedora-via-dhcpd-tftp-apache
http://www.opensourcehowto.org/how-to/tftp/tftp--pxe--syslinux--fedora-install.html
's all for today, take care atte
Ker
EDITED!: Today I just did the same configuration on a machine that ran fedora, and there was no case that would serve the facility. The machine was connected to the server but the installation could not start due to "a tftp configuration problem" ... weird ...
0 comments:
Post a Comment