Is trying to develop a test system using QNX RTP. I have gotten far
enough to
build a boot image and get it booted across a network to
my target platform. The DHCP server is providing more information than
just the name of the boot image and the IP address and I need this
information
after starting the image.
I had to use the same trick as QNX uses to boot into QNX from a MSDos
prompt
in the image “Device=loadqnx.sys image.ifs”
I know that the shell variables are available prior to starting the
image.
Is there a way to pass shell variables through to the image?
Or the other way, can I get the same information from dhcp.client as I
have
to run that to get the IP address that was lost during the image
startup?
Another question:
What is special about the floppy.144 image that is installed in Windows?
I was able to use that image unmodified to boot from across a network
via bootp. Nothing else has been able to do that.
Larry Brigman <lbrigman@fcpa.fujitsu.com> wrote:
Is trying to develop a test system using QNX RTP. I have gotten far
enough to
build a boot image and get it booted across a network to
my target platform. The DHCP server is providing more information than
just the name of the boot image and the IP address and I need this
information
after starting the image.
Can’t you juse run the dhcp.client in the boot image to re-request this
information?
Another question:
What is special about the floppy.144 image that is installed in Windows?
I was able to use that image unmodified to boot from across a network
via bootp. Nothing else has been able to do that.
I am a little confused about this statement. In my test/development
setup I use dhcp/bootp and tftp to load images produced with mkifs
all the time - nothing fancy. How are you building your image?
chris
–
cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Chris McKillop wrote:
Larry Brigman <> lbrigman@fcpa.fujitsu.com> > wrote:
Is trying to develop a test system using QNX RTP. I have gotten far
enough to
build a boot image and get it booted across a network to
my target platform. The DHCP server is providing more information than
just the name of the boot image and the IP address and I need this
information
after starting the image.
Can’t you juse run the dhcp.client in the boot image to re-request this
information?
I can but I don’t know how to get the additional information out of the
dhcp.client
app.
Another question:
What is special about the floppy.144 image that is installed in Windows?
I was able to use that image unmodified to boot from across a network
via bootp. Nothing else has been able to do that.
I am a little confused about this statement. In my test/development
setup I use dhcp/bootp and tftp to load images produced with mkifs
all the time - nothing fancy. How are you building your image?
chris
I’m using a modified file from the QTP install in /boot/build/qnxbase.build.
The only things that are changed are the start-up script and some of
the embedded files. This image when placed on a floppy does boot the device
I am testing. The build is simple “mkifs qnxfloppy.build floppy.ifs”
I copy this over to my bootp directory and make it the default boot image
and it doesn’t start after being downloaded to the node. If I put it in
a dos image and started it like “device=loadqnx.sys floppy.ifs” everything
works.
Larry Brigman <lbrigman@fcpa.fujitsu.com> wrote:
Chris McKillop wrote:
Larry Brigman <> lbrigman@fcpa.fujitsu.com> > wrote:
Is trying to develop a test system using QNX RTP. I have gotten far
enough to
build a boot image and get it booted across a network to
my target platform. The DHCP server is providing more information than
just the name of the boot image and the IP address and I need this
information
after starting the image.
Can’t you juse run the dhcp.client in the boot image to re-request this
information?
Hello,
I can but I don’t know how to get the additional information out of the
dhcp.client
app.
Hello,
I might be off the topic, but how about if you use -d option “dhcp.client -d &”.
This option Write debugging info to the system log. Fore more info on dhcp.client
please goto:
http://qdn.qnx.com/support/docs/neutrino_qrp/utilities/d/dhcp.client.html
Regards,
Marcin
Another question:
What is special about the floppy.144 image that is installed in Windows?
I was able to use that image unmodified to boot from across a network
via bootp. Nothing else has been able to do that.
I am a little confused about this statement. In my test/development
setup I use dhcp/bootp and tftp to load images produced with mkifs
all the time - nothing fancy. How are you building your image?
chris
I’m using a modified file from the QTP install in /boot/build/qnxbase.build.
The only things that are changed are the start-up script and some of
the embedded files. This image when placed on a floppy does boot the device
I am testing. The build is simple “mkifs qnxfloppy.build floppy.ifs”
I copy this over to my bootp directory and make it the default boot image
and it doesn’t start after being downloaded to the node. If I put it in
a dos image and started it like “device=loadqnx.sys floppy.ifs” everything
works.
Marcin Dzieciol wrote:
Larry Brigman <> lbrigman@fcpa.fujitsu.com> > wrote:
Chris McKillop wrote:
Larry Brigman <> lbrigman@fcpa.fujitsu.com> > wrote:
Is trying to develop a test system using QNX RTP. I have gotten far
enough to
build a boot image and get it booted across a network to
my target platform. The DHCP server is providing more information than
just the name of the boot image and the IP address and I need this
information
after starting the image.
Can’t you juse run the dhcp.client in the boot image to re-request this
information?
Hello,
I can but I don’t know how to get the additional information out of the
dhcp.client
app.
Hello,
I might be off the topic, but how about if you use -d option “dhcp.client -d &”.
This option Write debugging info to the system log. Fore more info on dhcp.client
please goto:
http://qdn.qnx.com/support/docs/neutrino_qrp/utilities/d/dhcp.client.html
Regards,
Marcin
I thought I had looked at the docs before. That would mean that I would have to
write a parser to retrive the info from the syslog file but it would also require that
I start syslogd from the boot image. After looking at the docs again it refered
me to confstr() which would work if I could dhcp.client would not toss info
from the bootp packet it does not need.