Thanks to the help of many people on the debian-user and linux-diald lists,
I seem to have my diald issue resolved! I re-compiled my 2.2.1 kernel with
SLIP support, and it now works like magic. I still have a few minor issues
to work out with it, but on the whole it's fantastic!
(Cross-posted to
Ted> I'm trying to run diald to automate my PPP connection. I don't
Ted> recall the exact sequence of events when I upgraded from kernel
Ted> 2.0.34 to 2.2.1, but it now generates the following lines in
Ted> /var/log/messages:
Feb 8 15:36:22 salsa kernel: diald uses obsolete (PF_INET,SOCK_PACKE
I recently had a problem with ntop along the same lines. Evidently the
new kernel (I was using 2.1.123 at the time) changed the socket() call.
When I upgraded to 2.2.1 and recompiled ntop, the problem went away. You
might try recompiling diald to see if that helps.
Todd Davis
On Fri, 12 Feb 19
On 12 Feb, Ted Behling wrote:
> I'm trying to run diald to automate my PPP connection. I don't recall the
> exact sequence of events when I upgraded from kernel 2.0.34 to 2.2.1, but
> it now generates the following lines in /var/log/messages:
>
> Feb 8 15:36:22 salsa kernel: diald uses obsolete
On 12-Feb-99 Ted Behling wrote:
I just tuned in, but what do you have in your PPP options file? Try a blank
ppp options file. Some of the normal PPP options are incompatible with diald.
--
Andrew
I'm trying to run diald to automate my PPP connection. I don't recall the
exact sequence of events when I upgraded from kernel 2.0.34 to 2.2.1, but
it now generates the following lines in /var/log/messages:
Feb 8 15:36:22 salsa kernel: diald uses obsolete (PF_INET,SOCK_PACKET)
Feb 8 15:36:23 s
6 matches
Mail list logo
