From owner-freebsd-current Wed Oct 7 06:13:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15681 for freebsd-current-outgoing; Wed, 7 Oct 1998 06:13:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15675 for ; Wed, 7 Oct 1998 06:13:39 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA07366; Wed, 7 Oct 1998 09:08:55 -0400 (EDT) Date: Wed, 7 Oct 1998 09:08:55 -0400 (EDT) From: Brian Feldman To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: Broken PLIP code? In-Reply-To: <199810070651.IAA22465@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I notice this too :/ Strangely, this is with iijppp, using /dev/{tun0,cuaa1} as its devices, but I understand it could scroll through all the devices to find the tuns, or something like that. I'm pretty sure the ioctl that causes this is SIOCSIFFLAGS. Cheers, Brian Feldman On Wed, 7 Oct 1998, Mark Murray wrote: > Hi > > I put the new parallel port drivers into my kernel: > > > controller ppc0 at isa? port ? tty irq 7 vector ppcintr > controller ppbus0 > device nlpt0 at ppbus? > device plip0 at ppbus? > > ... and the PLIP device acts funny: > > # ifconfig -a > : > lp0: flags=8810 mtu 1500 > : > Oct 7 08:49:33 greenpeace /kernel: LP:ioctl(0xc0286938) > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message