From owner-freebsd-current Fri May 14 21:22:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6FD4A14C97 for ; Fri, 14 May 1999 21:22:57 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id VAA18763; Fri, 14 May 1999 21:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA03469; Fri, 14 May 1999 21:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905150241.MAA11478@godzilla.zeta.org.au> Date: Fri, 14 May 1999 21:22:55 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Bruce Evans Subject: Re: Heads up! config(8) changes.. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > In old mail, John Polstra wrote: >> >>What do you do about the "ppc" device? Formerly, it needed to be "net >>irq ..." if the "plip" device was going to be used, but "tty irq ..." >>otherwise. Which one did you pick? > > tty was picked (see isa_compat.h). Also, support for the hack of > setting net_imask = tty_imask if slip is configured went away, so slip > now has the same problems as plip. I think most of these problems can be > avoided by configuring (kernel) ppp. ppp sets net_imask >= tty_imask, > which is sufficient provided slip and plip call splimp() as required. > Only cases where the masks change significantly after ppp is initialised > are necessarily broken. It seems to me that all this spl hackery would be better avoided, through a userland approach that used the tun device or something similar. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message