wasn't 2.2.6 (or there about) a bit *unstable*. I remember reading
something about filesystem corruption worries on the kernel list. not
sure. Not saying that's the cause of your problems, but it might be
worth your while to go to at least 2.2.10.
later,
Ted Gervais wrote:
>
> Troubles getting this new kernel to go. At the moment I am running 2.0.36
> without a 'hitch' and am very happy with it. HOwever, there comes a time
> when one has to move on. Well I have tried. Here is what happens now that
> I have the new 2.2.6 slackware package installed. I need to bring up the
> following:
>
> echo "Initializing SLIP connection to LINUX/Tnos-230"
> echo "Standby .....MAR 29 1999 "
>
> /usr/sbin/slattach -s 38400 -p slip /dev/ptypf &
> sleep 2
> /sbin/ifconfig sl0 broadcast 44.135.255.255 pointopoint 44.135.34.254 mtu
> 576 44.135.34.201
> /sbin/route add -net 44.135.34.254 netmask 255.255.255.255 sl0
> /sbin/route add -net 44.135.32.0 netmask 255.255.248.0 gw 44.135.34.254
> window 2048 mss 236 irtt 30000
> /sbin/route add -net 44.135.43.0 netmask 255.255.255.0 gw 44.135.34.254
> window 2048 mss 236 irtt 30000
> #
>
> And when I try and do this, here is what comes back:
>
> Initializing SLIP connection to LINUX/Tnos-230
> Standby .....MAR 29 1999
> SIOCADDRT: No such device
> SIOCSIFBRDADDR: Cannot assign requested address
> SIOCSIFDSTADDR: Cannot assign requested address
>
> How do I fix this?
> --
> Ted Gervais <[EMAIL PROTECTED]>
> 44.135.34.254 gw.ve1drg.ampr.org
--
____________________________________________________________
Kervin Pierre.
