Hi…
I have a file system mounted in a DiskOnChip which resides on an Adastra
small embedded computer. The build code is shown bellow, but I can not
telnet to my DOC. I have all the libraries that telnet, login need.
What do I have to have so that I can telnet to an embedded system?
Does any one know about a sample build file that includes the necessary
components so that we can telnet to that system? I guess that I need to
know what are the minimum necessary components or the script combination
such that I can telnet to an embedded system hosting a DOC or a SanDisk
or any other such solid state disks.
Thanks…
Best Regards…
Miguel.
###############################################################
[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] boot = {
startup-bios -Nmachine-name
startup-bios -s 64k
PATH=/proc/boot:/bin:/sbin
LD_LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll procnto
}
[+script] startup-script = {
seedres
These env variables inherited by all the programs which follow
TERM=qansi
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin
LD_LIBRARY_PATH=/proc/boot:/lib:/lib/dll
DL_DEBUG=1
\
Start up some consoles
devc-con -n4 &
reopen /dev/con1
display_msg Welcome to Neutrino on an PC compatible BIOS system
Start the pci server
pci-bios &
waitfor /dev/pci
Network drivers and filesystems
io-net -dpcnet -ptcpip
waitfor /dev/io-net
sleep 2
ifconfig en0 10.2.108.203 netmask 255.255.255.0 up
waitfor /dev/socket
netmanager
sleep 2
mount -Tio-net -o"host=saic3.saic.com" npm-qnet.so
fs-nfs2 10.2:/usr/nto / 10.2:/ /usr/qnx4 &
Disk drivers (The default one and some fun others for your
pleasure…)
devb-doc -w:0xd4000
waitfor /dev/hd0t77
devb-doc blk automount=hd0t77:/ &
Wait for a bin for the rest of the commands (up to 30 secs)
mount /dev/hd0t77 /
waitfor /bin 30
Some common servers
pipe &
mqueue &
devc-pty &
Start some extra shells on other consoles
reopen /dev/con2
[+session pri=10r] fesh &
reopen /dev/con3
[+session pri=10r] fesh &
[+session] fesh &
Start a high priority shell just in case…
reopen /dev/con4
[+session pri=30r] fesh &
[pri=25 +session] fesh &
Start the main shell
reopen /dev/con1
[+session pri=10r] fesh &
[+session] fesh
[+session] login -p
}
Cheat and make the /temp point to the shared memory area…
[type=link] /tmp=/dev/shmem
Redirect console messages for syslog
[type=link] /dev/console=/dev/con1
We use the “c” shared lib (which also contains the runtime linker)
/lib/libc.so.2
Programs require the runtime linker (ldqnx.so) to be at a fixed
location
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so.2
Just incase someone needs floating point…
#fpemu.so.2
Include the socket library
libsocket.so
Include the hard disk files so we can access files on the disk
libcam.so
io-blk.so
filesystem required shared libs
cam-disk.so
fs-qnx4.so
Include the socket library
libsocket.so
Include the network files so we can access files across the net
devn-pcnet.so
npm-tcpip.so
npm-qnet.so
###############################################################
The files above this line can be shared by mutiple processes
###############################################################
[data=c]
seedres
Executables must currently be below this line
devc-con # Include a console driver
devb-doc # Include DiskOnChip driver.
devb-fdc
pci-bios # Include pci server
/bin/mount
/bin/fesh
/sbin/pipe
/sbin/mqueue
Include the network executables.
/sbin/io-net
/usr/sbin/fs-nfs2
/usr/sbin/fs-cifs
/usr/bin/telnet
/bin/netmanager
/bin/df
/bin/slay
/usr/bin/sleep
/usr/bin/ifconfig
/usr/bin/ping
/usr/bin/netstat
###############################################################
\
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com