Date: Thu, 6 Mar 2003 13:38:54 -0500 From: Hiten Pandya <hiten@unixdaemons.com> To: current@FreeBSD.ORG Subject: Loopback device dillema Message-ID: <20030306183854.GA47557@unixdaemons.com>
next in thread | raw e-mail | index | archive | help
Hi gang. As I was playing around with the mbuf code, and came across the loopback device code (if_loop.c). Despite it's ugliness and shoddy code which came with the KAME stuff. Well, the problem is that it's not possible to compile the kernel when you remove the loop device from your config, because of the if_simloop changes that julian made some time ago (revision 1.33 of if_loop.c). So, shall we make if_loop.c the default, and not have a 'device loop' option, or does someone want to take the time of cleaning up the mess in the case when 'device loop' is not in the config? I have cleaned up the if_simloop case in my local tree by moving it into if.c as it's a pretty generic routine used in various files, but now the problem comes in how 'loif' is used in netinet/if_ether.c and netinet/igmp.c. To conclude, I would like to see the loopback device made default, and if this is not agreed upon, then someone needs to fix case when loopback device is not in the kernel config, and is going to be loaded as a module. Cheers. -- Hiten Pandya (hiten@unixdaemons.com, hiten@uk.FreeBSD.org) http://www.unixdaemons.com/~hiten/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030306183854.GA47557>