PPP and SLIP as loadable modules
Hello.
I recently acquired a system with Debian 1.3.1 pre-installed (kernel
2.0.29). I have a couple of years' experience using an older Slackware
distribution (kernel 1.2.0).
I'm more than happy in general with the Debian distribution, but I was
surprised and annoyed to discover that the shippers had failed to compile
PPP or SLIP support into the kernel.
I've never (re)compiled a kernel. I know I'm supposed to learn how to
do it, and I will, but I'm nervous about having to do it so soon. A
kind soul suggested that, since both SLIP and PPP were modules, they
could be loaded by hand or during the boot process using modprobe or
insmod. I tried that, and got back the following:
marvin# modprobe ppp.o
/lib/modules/2.0.29/net/ppp.o: unresolved symbol kill_fasync_Rf99c4230
/lib/modules/2.0.29/net/ppp.o: unresolved symbol register_netdev_R24876de2
/lib/modules/2.0.29/net/ppp.o: unresolved symbol netif_rx_R578c179c
/lib/modules/2.0.29/net/ppp.o: unresolved symbol dev_kfree_skb_R44b132be
/lib/modules/2.0.29/net/ppp.o: unresolved symbol tty_register_ldisc_Rbc2419d2
/lib/modules/2.0.29/net/ppp.o: unresolved symbol n_tty_ioctl_Ra07e8b74
/lib/modules/2.0.29/net/ppp.o: unresolved symbol dev_alloc_skb_R8587f622
/lib/modules/2.0.29/net/ppp.o: unresolved symbol unregister_netdev_Rc260075b
/lib/modules/2.0.29/net/ppp.o: unresolved symbol dev_close_R391db8f6
marvin#
I can make no sense of this, but I'm pretty sure that it means that
support for PPP and SLIP hasn't even been built into the kernel as a
loadable module. Which means that I have no option but to recompile
the kernel, right? Tell me it isn't so.
Any and all advice gratefully received,
Jim
======================================================================
Jim McCloskey (mcclosk@cats.ucsc.edu)
======================================================================
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: