Sponsored Content
Full Discussion: Network Installation
Operating Systems Linux Red Hat Network Installation Post 302360910 by pludi on Sunday 11th of October 2009 11:11:59 AM
Old 10-11-2009
You could install 2 additional services for TFTP and and DHCP, and do an PXE install as described here
This User Gave Thanks to pludi For This Post:
 

8 More Discussions You Might Find Interesting

1. Solaris

installation of Solaris: installation bypasses network config.

hello solaris friends, I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url: http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies

2. Debian

debian network installation

we have separate repo for the ftp installation. I copied vmlinuz and initrd from the repo(stable disti) and booted my lapton from it(after modyfing the grub). Now the problem is setup is looking for .iso file (?). Why do i need iso file ? without iso we can start the shell . So can we make use of... (0 Replies)
Discussion started by: yogesh_powar
0 Replies

3. Solaris

Solaris 10.8 installation over network

Hi, I'm very new to Solaris world and istarted my learnign with a Blade T6320 Server. I was trying to install Solaris 10.8 from a DVD image over the network. But from the client(the machine which i want to install Solaris) when i tried boot net , i am getting a message like " cannto find... (5 Replies)
Discussion started by: jerinvjose
5 Replies

4. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

5. Solaris

Network card installation issue

I have installed Solaris 10 in my PC successfully and my system having Intel(R) PRO/100 VE ethernet card. Solaris OS not able to detect the network card. So i checked the driver (INTCGigaE) and reinstalled. Still network card is not detected. bash-3.00# pkgchk INTCGigaE ERROR:... (0 Replies)
Discussion started by: paventhan
0 Replies

6. Red Hat

Network card module installation

Hi, I am using Red Hat 9.0 and it does not have the inbuilt driver module for my onboard lan card (RTL 8169). I downloaded the module (file - r8169-6.017.00.tar.bz2 and even r8169-6.015.00.tar.bz2), but when try to install it it says r8169.h , r8169_n.c , Makefile etc are not ELF formats. ... (0 Replies)
Discussion started by: dextergenious
0 Replies

7. Linux

Network card module installation

Hi, I am using Red Hat 9.0 and it does not have the inbuilt driver module for my onboard lan card (RTL 8169). I downloaded the module (file - r8169-6.017.00.tar.bz2 and even r8169-6.015.00.tar.bz2), but when try to install it it says r8169.h , r8169_n.c , Makefile etc are... (2 Replies)
Discussion started by: dextergenious
2 Replies

8. Red Hat

Network becomes slow and return fast only after restart network

Hi, I have 2 machines in production environment: 1. redhat machine for application 2. DB machine (oracle) The application doing a lot of small read&writes from and to the DB machine. The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
PXE-KEXEC(8)							     PXE-Kexec							      PXE-KEXEC(8)

NAME
pxe-kexec - Read PXE configuration file and kexec entries SYNOPSIS
pxe-kexec [options] [tftp_server] DESCRIPTION
Overview pxe-kexec is a tool that fetches PXE configuration from a TFTP server, reads that PXE configuration file, prompts the user for an boot entry, downloads the specified kernel and initrd and finally tries to boot the kernel. The normal process to boot with kexec(8) is that pxe-kexec loads the kernel and invokes reboot(8). The shutdown script of the Linux distribution then executes "kexec -e" at the very end. That is not implemented everywhere. Therefore, pxe-kexec has a whitelist of Linux distributions that support reboot with kexec. If the distribution is not on that whitelist, the program quits with a warning. To bypass that warning, please use the "--igore-whitelist" parameter. You can also use the "--force" parameter to execute "kexec -e" to immediately boot the selected kernel, without invoking shutdown(8)/reboot(8). pxe-kexec meant to be used in an environment where pre-defined PXE configurations exist but the user wants to use kexec(8) instead of rebooting. Normally, the tftp_server must be specified as first argument. If there's no TFTP server specified, pxe-kexec looks in the DHCP info file for the DHCP server and uses this one as TFTP server. This only works when the TFTP server is running on the same machine as the DHCP server. ==> Please also read the section called "Update Info" <== Whitelist As mentioned previously, a whitelist of Linux distributions that support kexec-based rebooting is maintained. Currently following distributions are on the whitelist: o openSUSE, starting with version 11.0 o Ubuntu, starting with version 9.04 o Red Hat Enterprise Linux and CentOS, starting with version 5.3 o Fedora Linux, starting with version 11 o ARCH Linux Don't hesitate to send the author an email to add the distribution to the whitelist. Please include the output of "pxe-kexec --print-distribution" in that mail. OPTIONS
Following options can be specified: -h | --help Prints a short help. -v | --version Prints the version number to standard output. -f | --force Immediately load the kernel without invoking reboot(8). This does not execute shutdown scripts, i.e. does not terminate daemons, network connections etc. -L | --load-only When that option is specified, the new kernel is only loaded. No reboot is triggered and "kexec -e" is also not executed. -w | --ignore-whitelist Don't check if the detected Linux distribution is on the whitelist of distributions that have kexec(8) in their shutdown script. Please don't use that parameter without letting the author know which distribution you use and how to detect that distribution. Then the distribution can be added to the whitelist and other users profit from that experience. -l label | --label label Specifies the label that should be booted. Use that option if you already know which label you want to boot. This option implies "--quiet". -i | --interface netif Uses netif instead of the first (non-loopback and up) interface that is found. Example: "eth5". -n | --noconfirm Don't ask the user for confirmation before booting an entry. Use that option with care! -Y | --dry-run Don't execute call to kexec and don't switch the virtual console before running "kexec -e". Instead, print the information which program would be executed with which arguments to standard error. -q | --quiet Don't display the PXE messages that are added in the PXE configuration with the say keyword. Also don't display messages which PXE configuration files the downloader tries to fetch. -p | --print-distribution Only prints the detected Linux distribution and exits. For example: Type : Ubuntu Name : Ubuntu Release : 9.04 Codename : jaunty Description : Ubuntu 9.04 This option is very useful if your distribution is not on the whitelist of Linux distributions that support kexec(8) in the reboot scripts and you want to create a bugreport. This command does not require root privileges. -D | --debug Enable debugging output. That's good for finding (and fixing!) bugs. -d | --nodelete Keep downloaded files. -F | --ftp Always use FTP instead of TFTP. Useful for servers that share TFTP root and FTP root. (Passive) FTP has the advantage that it passes firewalls better than TFTP. UPDATE INFO
Updating from 0.1.x to 0.2 Compared to version 0.1.x, the syntax has changed: o The default label must now be set with the -l label option instead of the 2nd argument. Example: % pxe-kexec mydhcp.mydomain.com SLES10-install-auto is now % pxe-kexec -l SLES10-install-auto mydhcp.mydomain.com o pxe-kexec now uses the reboot mechanism by default: The kernel is loaded, then the reboot is triggered and the reboot script of the Linux distribution finally boots the kernel. This has the advantage of a clear shutdown. The program keeps a database of Linux distributions that support kexec-based reboot. If the currently active distribution is not on the whitelist, an error is printed. (That whitelist can be ignored with "--ignore-whitelist".) o To use the previous behaviour, i.e. just execute "kexec -e" in pxe-kexec at the end, you can still use the "--force" parameter. Example: % pxe-kexec mydhcp.mydomain.com is now % pxe-kexec --force mydhcp.mydomain.com o If you want to have the old "dry-run" behaviour back, which in fact only missed the last "kexec -e" step, you can use the option "--load-only". Example: % pxe-kexec --dry-run mydhcp.mydomain.com is now % pxe-kexec --load-only mydhcp.mydomain.com EXAMPLES
pxe-kexec mydhcp.mydomain.com Try to fetch the PXE configuration from mydhcp.mydomain.com, display the say messages from that configuration, prompt for an entry, letting the user confirm that entry and finally load that entry via kexec(8) and reboot via reboot(8). This only works if you distribution supports kexec-based rebooting, i.e. it is in the internal whitelist. pxe-kexec -n mydhcp.mydomain.com Same as the previous example, but omit the final confirmation step. pxe-kexec -l SLES10-install-auto mydhcp.mydomain.com Same as the first example, but don't prompt the user for the label to boot. Directly boot the SLES10-install-auto label, but letting the user confirm that he really wants to boot this! pxe-kexec -n -l SLES10-install-auto mydhcp.mydomain.com Same as the previous example, but without confirmation. pxe-kexec -f mydhcp.mydomain.com Same as the first example, but execute "kexec -e" at the end instead of invoking reboot(8). pxe-kexec -l mydhcp.mydomain.com Same as the first example, but don't trigger a reboot. Instead, the kernel is just loaded. If your distribution supports kexec-based rebooting, the kernel will be loaded on next reboot. You can also run "kexec -e" manually at any time. AUTHOR
The pxe-kexec program and documentation has been written by Bernhard Walle <bernhard@bwalle.de>. BUGS
This program has no bugs. If you find a feature that should be removed, please report to <bernhard@bwalle.de> if you don't want to create an account. SEE ALSO
kexec(8) 0.2.4 2011-03-26 PXE-KEXEC(8)
All times are GMT -4. The time now is 10:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy