12-11-2006
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
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
pdc(1M) pdc(1M)
NAME
pdc - processor-dependent code (firmware)
DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com-
pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard-
ware as described below.
To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot
Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model.
When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini-
tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con-
sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths.
If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character
on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support
autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium.
If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A
simple menu is then displayed where the user can:
o Boot a specific device, using the abbreviated path identifier, or the full mnemonic.
o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not
check the contents).
o Enter the boot administration level.
o Exit the menu and return to autobooting
o Get help on choices
If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the
Boot Path to use. Any required path components that are not supplied default to zero.
The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via
SEE ALSO
boot(1M), isl(1M).
PA-RISC Systems Only pdc(1M)