From: wonge@fraser.sfu.ca (Edmund Wong) Subject: sockets and kernels? <yummy for breakfasts! NOT!> Date: Sat, 2 Jan 1993 17:03:46 GMT
After a VERY frustrating and fruitless duel with these stupid
socket problems, I had to revert to my SECRET weapon. Here.
The problem that I'm having with Linux is that when the system
boots up, and /etc/inet/rc.net is executed, the following three
commands give me a "socket: Invalid argument":-
# in /etc/inet/rc.net
.
.
HOSTS=/usr/etc/inet/hosts
CONFIG=/usr/etc/inet/config
INETD=/usr/etc/inet/inetd
NAMED=/usr/etc/inet/named
PORTMAP=/usr/etc/inet/portmap
NFSD=/usr/etc/inet/nfsd
MOUNTD=/usr/etc/inet/mountd
#
HOSTNAME=`hostname`
#
echo "$HOSTNAME -> $IPADDR"
#
ROUTER=0.0.0.0
NET=142.101.245.0
#
$CONFIG loopback $IPADDR
$CONFIG loopback 127.0.0.1
$CONFIG -n $NET -r $ROUTER eth0 $IPADDR
#
....<the normal 'if [...' stuff..>
Now, of course, being quite an experimental young lad, I changed
'$CONFIG loopback $IPADDR' to '$CONFIG $HOSTNAME $IPADDR', still
it gives me 'socket: Invalid argument'.
So I figured. Hey, maybe it's something wrong with config*,
so I back'ed up the old config, and compiled config.c and
ran it. (since I did a 'cc config.c' I had to rename the a.out
to config) Then I re-ran rc.net. But to still no avail.
Someone suggested I get rid of 'eth0' and change it to 'loopback',
so I did. Still the same ugly result.
So, if possible, can someone please enlighten me on what is
going on? The hostname IS defined as 'eagles'. No, I'm not in
a network. Does that mean I won't be needing TCP/IP to work?
Secondly, an easy question about kernels. I've downloaded
the Linux 0.99pl0 kernel from tsx, and did the neccessary stuff
to compile it. After I did a 'make dep;make clean' and sync'd
and rebooted the system, it still displays '.98pl5-3?' right
before (root@softland). Why?
Any help appreciated....thanks
--
InterNet: wonge@fraser.sfu.ca | "Fail not; Learn Not.
| It is with failing, that one learns,
| So by Learning, one must fail." - Edmund Wong