You need to add

alias net-pf-4 off
alias net-pf-5 off

to /etc/conf.modules.... As far as I know this is just the appeltalk and ipx
stuff. It doesn't hurt to ignore it, but changing the conf.modules makes all
look pretty :-)

***********************************************************************
Wayne Pascoe                       TEL: +27-11-888-1869
Datrix Solutions                   FAX: +27-11-782-0704
[EMAIL PROTECTED]                CELL: 082-336-2556

-----Original Message-----
From: Kenneth Stephen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, January 04, 1999 1:49 PM
Subject: Whats with net-pf-5? (fwd)


>My previous sending has obviously been chewed up by some malevolent server
>on the 'net. Hence the repost...
>
>There is no such thing as luck. 'Luck' is nothing but an absence of bad
luck.
>
>---------- Forwarded message ----------
>Date: Sat, 2 Jan 1999 21:09:59 -0600 (CST)
>From: Kenneth Stephen <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Whats with net-pf-5?
>
>Hi,
>
>    I must be missing something obvious. Here is a boot script that is
>part of the Debian boot process :
>
>#! /bin/sh
>ifconfig lo 127.0.0.1
>route add -net 127.0.0.0
>IPADDR=192.168.0.1
>NETMASK=255.255.255.0
>NETWORK=192.168.0.0
>BROADCAST=192.168.0.255
>GATEWAY=192.168.0.1
>ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
>route add -net ${NETWORK}
>[ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
> Right after the two 'ifconfig' statements, I get a message saying
>that modprobe was unable to find the module net-pf-5. This is after a
>fresh build of 2.0.36 (make config; make dep; make clean; make bzImage;
>make modules; make modules_install).
>
> Kerneld is configured to autoload. I looked at the source code,
>and here is where the error occurs : (from /usr/src/linux/net/socket.c)
>
>/*
> *      Perform the socket system call. we locate the appropriate
> *      family, then create a fresh socket.
> */
>
>static int find_protocol_family(int family)
>{
>        register int i;
>        for (i = 0; i < NPROTO; i++)
>        {
>                if (pops[i] == NULL)
>                        continue;
>                if (pops[i]->family == family)
>                        return i;
>        }
>        return -1;
>}
>
>asmlinkage int sys_socket(int family, int type, int protocol)
>{
>        int i, fd;
>        struct socket *sock;
>        struct proto_ops *ops;
>
>        /* Locate the correct protocol family. */
>        i = find_protocol_family(family);
>
>#ifdef CONFIG_KERNELD
>        /* Attempt to load a protocol module if the find failed. */
>        if (i < 0)
>        {
>                char module_name[30];
>                sprintf(module_name,"net-pf-%d",family);
>                request_module(module_name);
>                i = find_protocol_family(family);
>        }
>#endif
>
> Can anyone enlighten me?
>
>Kenneth
>
>There is no such thing as luck. 'Luck' is nothing but an absence of bad
luck.
>

Reply via email to