"host name" entry on the vxWorks boot line
Eric S. Zipp
Obviously, my fist cup of coffee has not 'taken' yet.. I need a bit of
clarification..
On the boot parameters list below there are line entries for "inet on
ethernet", which is the IP address assigned to the card, "host inet",
which is the IP address of where the card is going to get it's load.
My question deals with the line "host name", I assume this is the
place on the boot line which you can assign a 'node name' to the
VxWorks card itself.. but I was challenged by someone saying .. "..
no, that's the node name of the server from which the load is received
(ie the node name associated with the 'host inet' IP address".
Enquiring minds want to know.. exactly 'who' is being named in the
"host name" slot??
Thanks,
Eric
*************************************
boot device :
processor number :
host name :
file name :
inet on ethernet (e) :
host inet (h) :
user (u) :
ftp password (pw) :
flags (f) :
target name (tn) :
Christian Gan
The host name field in the boot line refers to the card/machine that
has the host inet address. This hostname will appear on your 'devs'
list so that you can access the host machine through the target.
There's another field called target name that used for the name of the
card/machine that the image is running on.
Look in Section 13 of the VxWorks Networks Programmer's Guide for an
explanation of all the fields.
Hope this helps!
On Fri, 06 Apr 2001 10:06:23 -0500, Eric S. Zipp <eric...@lmco.com>
wrote:
Dave Korn
>Greetings,
>
>Obviously, my fist cup of coffee has not 'taken' yet.. I need a bit of
>clarification..
>
>On the boot parameters list below there are line entries for "inet on
>ethernet", which is the IP address assigned to the card, "host inet",
>which is the IP address of where the card is going to get it's load.
>
>My question deals with the line "host name", I assume this is the
>place on the boot line which you can assign a 'node name' to the
>VxWorks card itself.. but I was challenged by someone saying .. "..
>no, that's the node name of the server from which the load is received
>(ie the node name associated with the 'host inet' IP address".
>
>Enquiring minds want to know.. exactly 'who' is being named in the
>"host name" slot??
"host name" obviously enough goes along wiht "host inet". One is the name
of the host, the other is the inet addr of the host. Similar applies to
target, although for some reason WRS broke the symmetry by referring to what
should have been "host inet" as "inet on enet".
If you don't know the difference between your host and your target, you
shouldn't be working with missiles.... or in any case, I'm not inviting you
to any of my parties :-P
DaveK
--
They laughed at Galileo. They laughed at Copernicus. They laughed at
Columbus. But remember, they also laughed at Bozo the Clown.
vanbaren_gerald
>Greetings,
>Thanks,
>Eric
>*************************************
Your challenger was correct:
"no, that's the node name of the server from which the load is received
(ie the node name associated with the 'host inet' IP address".
My observations:
In the target shell, if you type the "devs" command, it will show the
ethernet device's name as the host name (somewhat odd). If you do a
"ls" command, it will show you the directory on the host. The host
IP address is used for the initial load, however (I've used the wrong
symbolic name and the initial load still works).
gvb
--
+---------------------------------------------------------------------------+
| Jerry Van Baren / vanbare...@si.com / Grand Rapids Mi / 616-241-7973 |
| My employer is a company. Companies are artifacts of a legal system. |
|________________Artifacts are incapable of having opinions.________________|
Eric S. Zipp
Guide)
Eric S. Zipp
... and, oh by the way... I'm devastated that I am to be excluded
from your next party, I was so looking forward to it since your house
was listed in the top-10 "party hearty" pads of VxWorks aficionados
for the year 2000. aaaah well, perhaps another time...
Eric S. Zipp
..thanks for the feedback... this is what I was looking for..
Regards,
Eric
vanb...@falcon.si.com (vanbaren_gerald) wrote:
>Your challenger was correct: