12-11-2006
Quote:
Originally Posted by gubten
the only 'remote boot' i'm aware of is with a remote access card, ie.. DRAC for a dell . remote install is totally different.
g'day
Almost any modern x86/x64 can be remote booted using PXE. Remote installation is basically just the application that runs by default after a remote boot.
9 More Discussions You Might Find Interesting
1. Red Hat
my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot.
The machine come up to grub prompt.
I tried the following from grub prompt
root (hd0, then press tab key
partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies
2. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
3. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
4. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
5. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
6. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
7. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
8. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
9. Red Hat
Hi guys,
I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies
LEARN ABOUT CENTOS
kernel-install
KERNEL-INSTALL(8) kernel-install KERNEL-INSTALL(8)
NAME
kernel-install - Add and remove kernel and initramfs images to and from /boot
SYNOPSIS
kernel-install COMMAND KERNEL-VERSION [KERNEL-IMAGE]
DESCRIPTION
kernel-install is used to install and remove kernel and initramfs images to and from /boot.
kernel-install will execute the files located in the directory /usr/lib/kernel/install.d/ and the local administration directory
/etc/kernel/install.d/. All files are collectively sorted and executed in lexical order, regardless of the directory in which they live.
However, files with identical filenames replace each other. Files in /etc/kernel/install.d/ take precedence over files with the same name
in /usr/lib/kernel/install.d/. This can be used to override a system-supplied executables with a local file if needed; a symbolic link in
/etc/kernel/install.d/ with the same name as an executable in /usr/lib/kernel/install.d/, pointing to /dev/null, disables the executable
entirely. Executables must have the extension ".install"; other extensions are ignored.
COMMANDS
The following commands are understood:
add KERNEL-VERSION KERNEL-IMAGE
kernel-install creates the directory /boot/MACHINE-ID/KERNEL-VERSION/ and calls every executable /usr/lib/kernel/install.d/*.install
and /etc/kernel/install.d/*.install with the arguments
add KERNEL-VERSION /boot/MACHINE-ID/KERNEL-VERSION/
The kernel-install plugin 50-depmod.install runs depmod for the KERNEL-VERSION.
The kernel-install plugin 90-loaderentry.install copies KERNEL-IMAGE to /boot/MACHINE-ID/KERNEL-VERSION/linux. It also creates a boot
loader entry according to the boot loader specification in /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf. The title of the entry
is the PRETTY_NAME parameter specified in /etc/os-release, or "Linux KERNEL-VERSION", if unset. If the file initrd is found next to the
linux file, the initrd will be added to the configuration.
remove KERNEL-VERSION
Calls every executable /usr/lib/kernel/install.d/*.install and /etc/kernel/install.d/*.install with the arguments
remove KERNEL-VERSION /boot/MACHINE-ID/KERNEL-VERSION/
kernel-install removes the entire directory /boot/MACHINE-ID/KERNEL-VERSION/ afterwards.
The kernel-install plugin 90-loaderentry.install removes the file /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf.
EXIT STATUS
If every executable returns with 0, 0 is returned, a non-zero failure code otherwise.
FILES
/usr/lib/kernel/install.d/*.install /etc/kernel/install.d/*.install
Drop-in files which are executed by kernel-install.
/etc/kernel/cmdline /proc/cmdline
The content of the file /etc/kernel/cmdline specifies the kernel command line to use. If that file does not exist, /proc/cmdline is
used.
/etc/machine-id
The content of the file specifies the machine identification MACHINE-ID.
/etc/os-release
The content of the file specifies the operating system title PRETTY_NAME.
SEE ALSO
machine-id(5), os-release(5), Boot loader specification[1]
NOTES
1. Boot loader specification
http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
systemd 208 KERNEL-INSTALL(8)