Minumum TCP files needed

QNX Newsgroups (Archives) comp.os.qnx
1

I need to install a subset of TCP/IP onto a system with only a 4MB
DiskOnChip, which is already 50% full.

What are the minimum files needed out of the TCP/IP installation that
are needed to allow for setting up the network, pinging other machines,
and for socket support?

I’ve been trying the old hunt-n-peck method but always seem to uncover
more files that I need each time I try to fix the last batch!

TIA

Gregory A. Fedor - gfedor@grc.nasa.gov - (216) 977-0317


Sent via Deja.com http://www.deja.com/
Before you buy.

2

All depends on what you want to do.

I have a script that starts my TCP/IP using a 3com 905 pci network card.

Net
Net.ether905
Socket
ifconfig

You may want to use Socklet if you are not using NFS.
If you’re worried about space why have ping on that system, why not
ping it from “other” side?

Depending on network you may need the route cmd.
Useful diagnostic utilities are ping & netstat.
You may want ftp, telnet to access other systems.

If you are serial you may might need pppd or slip (slattach, sliplogin).

If you are trying to access the system you probably want inetd
& /etc/inetd.conf (and maybe a few other configuration files,
like /etc/rpc, /etc/protocols, /etc/services )
Remote file copy: ftpd. ftpusers
Remote login: telnetd, Dev.pty.

To simplify testing, why don’t you mount a ramdrive on a normal system
the same size as your disk-on-chip and then change your path so system
only knows about what’s on ramdrive.

Vince

In article <8kvlv2$761$1@nnrp1.deja.com>,
gfedor@grc.nasa.gov wrote:

I need to install a subset of TCP/IP onto a system with only a 4MB
DiskOnChip, which is already 50% full.

What are the minimum files needed out of the TCP/IP installation that
are needed to allow for setting up the network, pinging other
machines,
and for socket support?

I’ve been trying the old hunt-n-peck method but always seem to uncover
more files that I need each time I try to fix the last batch!

TIA

Gregory A. Fedor - > gfedor@grc.nasa.gov > - (216) 977-0317

Sent via Deja.com > http://www.deja.com/
Before you buy.

Sent via Deja.com http://www.deja.com/
Before you buy.

3

you need only Socket or Socklet for tcpip4 and Tcpip for tcpip5.
supposed, that you have already started required network interface i.e. Net
and Net.* servers. all another utilites are optional. also to configure your
tcpip network you need ifconfig for manual configuration or dhcp.client if
you configure tcpip host through dhcp server. if you use ppp connection you
need also pppd server.

–

Thanks for your attention,
Ian M. Zagorskih, Software Developer, Novosoft Ltd.
E-Mail: ianzag@pochta.net ICQ 28632525
Web: http://www.novosoft.ru

// wbr

“Gregory Fedor” <gfedor@grc.nasa.gov> wrote in message
news:8kvlv2$761$1@nnrp1.deja.com…

I need to install a subset of TCP/IP onto a system with only a 4MB
DiskOnChip, which is already 50% full.

What are the minimum files needed out of the TCP/IP installation that
are needed to allow for setting up the network, pinging other machines,
and for socket support?

I’ve been trying the old hunt-n-peck method but always seem to uncover
more files that I need each time I try to fix the last batch!

TIA

Gregory A. Fedor - > gfedor@grc.nasa.gov > - (216) 977-0317


Sent via Deja.com > http://www.deja.com/
Before you buy.

4

Depending on the utility you include you might need
to include the library. I think ifconfig needs
one share library (don’t recall the name)

<vboyko@my-deja.com> wrote in message news:8kvrlk$boj$1@nnrp1.deja.com…

All depends on what you want to do.

I have a script that starts my TCP/IP using a 3com 905 pci network card.

Net
Net.ether905
Socket
ifconfig

You may want to use Socklet if you are not using NFS.
If you’re worried about space why have ping on that system, why not
ping it from “other” side?

Depending on network you may need the route cmd.
Useful diagnostic utilities are ping & netstat.
You may want ftp, telnet to access other systems.

If you are serial you may might need pppd or slip (slattach, sliplogin).

If you are trying to access the system you probably want inetd
& /etc/inetd.conf (and maybe a few other configuration files,
like /etc/rpc, /etc/protocols, /etc/services )
Remote file copy: ftpd. ftpusers
Remote login: telnetd, Dev.pty.

To simplify testing, why don’t you mount a ramdrive on a normal system
the same size as your disk-on-chip and then change your path so system
only knows about what’s on ramdrive.

Vince

In article <8kvlv2$761$> 1@nnrp1.deja.com> >,
gfedor@grc.nasa.gov > wrote:
I need to install a subset of TCP/IP onto a system with only a 4MB
DiskOnChip, which is already 50% full.

What are the minimum files needed out of the TCP/IP installation that
are needed to allow for setting up the network, pinging other
machines,
and for socket support?

I’ve been trying the old hunt-n-peck method but always seem to uncover
more files that I need each time I try to fix the last batch!

TIA

Gregory A. Fedor - > gfedor@grc.nasa.gov > - (216) 977-0317

Sent via Deja.com > http://www.deja.com/
Before you buy.



Sent via Deja.com > http://www.deja.com/
Before you buy.