Date: Wed, 22 Nov 1995 16:41:57 -0800 (PST) From: Julian Elischer <julian@ref.tfs.com> To: langfod@maui.com (David Langford) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.ORG Subject: Re: iBCS2, socksys and all that jazz... Message-ID: <199511230041.QAA10094@ref.tfs.com> In-Reply-To: <199511222110.LAA11369@ maui.com> from "David Langford" at Nov 22, 95 11:10:49 am
next in thread | previous in thread | raw e-mail | index | archive | help
The socksys device was made for the previous methof of handling it, which was to actually have the device :) > > >> Ok; having just supped and make-worlded -current, I'm hunting the > >> "why doesn't socksys work" problem. > >> > >> There's code in -current for socksys ioctls, but nothing to handle the > >> day-to-day open/close stuff needed for these ioctls. > >> > >> Is this something that's currently under development? > >What you do is link socksys to /dev/null > > If this is true and works, then what is it that MAKEDEV is trying do to? > Or why doesnt "MAKEDEV socksys" make soscksys a link to /dev/null? > > >it just supplies an fd for the ioctl to be done on.. > >the ioctl is recognised by it's ioctl ID on failure > >The iBSC2 code says.. > >"hmm that ioclt failed.. Hey I know that.. it's a SOCKSYS ioctl, > >ok, let's do 'THIS'" and it emulates it. so what file you openned > >only matters in that it needs to FAIL the ioctl with the correct manner. > >> ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > > > -- > /--------------------------------------------------------------------\ > | David Langford - Kihei, Maui, Hawaii - langfod@maui.com | > | Maui Research and Technology Center -- Network Administrator | > \--------------------------------------------------------------------/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511230041.QAA10094>