04-28-2008
in short words:
PXE boot is booting via network... and bare metal is a server without an operating system.
Last edited by DukeNuke2; 04-28-2008 at 06:42 AM..
9 More Discussions You Might Find Interesting
1. HP-UX
Hi,all:
I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed !
It says : Client MAC Address: 00 18 FE 28 91 82 .....-
PXE-E16: Valid PXE offer not received.
Load of Core LAN Gb A failed: Not Found
I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies
2. UNIX for Advanced & Expert Users
I've set up a PXE boot server and I'm having a slight snag in the booting process. On the client machine, DHCP renders fine and TFTP seems to begin but then the system hangs. On the server, the error message "Client does not accept options" occurs -- which from reading online is a common message... (2 Replies)
Discussion started by: Colton
2 Replies
3. HP-UX
How can i make a dvd image ( bare metal backup ) for HP-UX 11i v3 installation on integrity servers , for quick recovery for the os and installed software in case of disaster (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am trying to setup a server for a diskless boot of a computer class (with ubuntu)
I followed the guidelines in https://help.ubuntu.com/community/DisklessUbuntuHowto
I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine... (8 Replies)
Discussion started by: yotamhc
8 Replies
5. Solaris
Hi folks, I was trying to setup Network based NFS installation with PXE.
I'm using virtual box for this purpose. I have one redhat (DHCP) server and Solaris 10 (Install server - Source) and on the other one am trying to install solaris using PXE. As in, dhcp address and boot file can be fetched... (2 Replies)
Discussion started by: vijaytrendz
2 Replies
6. Red Hat
I have been asked to modify our PXE server such that there will be only one entry in the pxelinux.cfg/default file, where the same kernel and initrd.img will be used regardless of what operating system is to be installed, and the user will type in the path to the kickstart file that will be used. ... (7 Replies)
Discussion started by: ceb
7 Replies
7. Red Hat
Hi
Hoping someone can help ove setup a pxe/dhcp boot server for auto installs on centos My server seems to be providing dhcp fine but the installation fails to progress when it reaches the pxe boot menu. I make my selection and nothing happens. I am serving the media via http from the same... (3 Replies)
Discussion started by: duckeggs01
3 Replies
8. Red Hat
Hi all,
I am working on Linux Bare Metal Restore in which i have few things to be discussed with a person who has his/her hands on in that process.
If anyone kindly give a reply post in this thread.. :) :)
Thanks
Selva (3 Replies)
Discussion started by: selvarajvs
3 Replies
9. SCO
Hello,
We have a SCO Open Server 6 running on bare metal hardware, this is used for a legacy application that we continue to need.
I would like to migrate/virtualize the SCO server into VMware so that I can do VM level backups, etc.
I did test to make sure SCO 6.0 can run in VMware/ESXi... (11 Replies)
Discussion started by: c3rb3rus
11 Replies
PHSEG(3) MBK PHYSICAL STRUCTURE DEFINITIONS PHSEG(3)
NAME
phseg - mbk physical segment
DESCRIPTION
The phseg structure is used to describe a segment belonging to a symbolic layout model, see phfig(3) for details. Transistors are segments
of a particular layer.
The declarations needed to work on phseg are available in the header file "/labo/include/mph402.h", where '402' is the actual mbk version.
The following C structure supports the description of the segment :
typedef struct phseg {
struct phseg *NEXT;
char *NAME;
long X1,Y1,X2,Y2;
long WIDTH;
char TYPE;
char LAYER;
struct ptype *USER;
} phseg_list;
NEXT Pointer to the next segment in the list.
NAME Name of the segment. The name is not an identifier, and a name is present only if the designer used one for debug pur-
poses.
X1, Y1, X2, Y2 Coordinates of each end of the segment. Since it's a symbolic segment, one alway has either X1 = X2 or Y1 = Y2. Fur-
thermore, by construction, it is warranty, if one accesses the data structure through the legal functions, that X1 <=
X2 and Y1 <= Y2.
TYPE This caracter can take four values :
LEFT or RIGHT if Y1 = Y2. The exact value is chosen by addphseg, depending upon X1 and X2 relations.
UP or DOWN if X1 = X2
LAYER Symbolic layer used for the segment. The legal values are :
NWELL N bulk
PWELL P bulk
NTIE N implant in P bulk
PTIE P implant in N bulk
NDIF N diffusion
PDIF P diffusion
NTRANS N transistor
PTRANS P transistor
POLY polysilicium
ALU1 first metal
ALU2 second metal
ALU3 third metal
TPOLY polysilicum through route
TALU1 first metal through route
TALU2 second metal through route
TALU3 third metal through route
WIDTH Width of the segment. The physical extension of a segment is perpendicular to its direction.
USER Pointer to a ptype list, see ptype for details, that is a general purpose pointer used to share informations on the
segment.
SEE ALSO
mbk(1), addphseg(3), getphseg(3), delphseg(3), phfig(3), ptype(3).
BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory.
We need your feedback to improve documentation and tools.
ASIM
/LIP6 October 1, 1997 PHSEG(3)