Subject: Re: bin/33923: slattach(8) can't attach sl(4) interface
To: Christos Zoulas <>
From: Quentin Garnier <>
List: tech-net
Date: 07/08/2006 19:56:56
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 08, 2006 at 11:49:48AM -0400, Christos Zoulas wrote:
> On Jul 8, 10:35am, (Quentin Garnier) wrote:
> -- Subject: Re: bin/33923: slattach(8) can't attach sl(4) interface
> |  sl(4) does have SLIOCGUNIT, so slattach has a way to tell which sl(4)
> |  device it was bound to.  Having the interface automatically created is
> |  just a matter of having slopen() do it, just like pppopen() calls
> |  pppalloc().
> | =20
> Yes, most of the code can be stolen from ppp. It would be nice if it was
> shared too (since we'll have 3 copies if we fix strip). Why don't you
> take a stab at it?

By the way, as I have never used sl(4) nor strip(4), I wonder what
clonification changed, beside the fact that the user has to create the
interface by hand.  My reading of slattach.c seems to indicate that
currently (and independently from the fact that sl(4) is clonable) there
is no way to tell for sure which interface it has attached to.

Am I correct?

[Moved to tech-net because it's not really related to the PR anymore.]

Quentin Garnier - -
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.3 (NetBSD)