screwy kernel messages about (AF_INET,SOCK_PACKET,..) being obsolete

Sergei Viznyuk (sviznyuk@columbus.rr.com)
Tue, 20 Jan 1998 23:38:44 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01BD25FC.8BEB93A0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Hi again

While testing dhcpcd
which I rewrote to work with new kernels
(as prescribed by Alan Cox - with SOCK_PACKET)
I'm getting strange kernel messages in my /var/log/debug
file:

<time stamp> kernel: dhcpcd uses obsolete (AF_INET,SOCK_PACKET..

Well, that's exactly what I'm using: socket(AF_INET,SOCK_PACKET,..)
So why is it obsolete now?
Also, that message shows up only once: when I start dhcpcd
with unconfigured eth0 interface.
Subsequent runs of dhcpcd with eth0 already up
do not cause that message.

Thanks,
Sergei

------=_NextPart_000_0006_01BD25FC.8BEB93A0
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

Hi again
 
While testing dhcpcd
which I rewrote to work with new = kernels
(as prescribed by Alan Cox - with = SOCK_PACKET)
I'm getting strange kernel messages in my=20 /var/log/debug 
file: 
 
<time stamp> kernel: dhcpcd uses obsolete=20 (AF_INET,SOCK_PACKET..
 
Well, that's exactly what I'm using: =20 socket(AF_INET,SOCK_PACKET,..)
So why is it obsolete now? 
Also, that message shows up only = once: when I=20 start dhcpcd
with unconfigured eth0 interface.
Subsequent runs of dhcpcd with eth0 already = up
do not cause that message.
 
Thanks,
Sergei
 
------=_NextPart_000_0006_01BD25FC.8BEB93A0--