Date: Wed, 22 Nov 1995 11:40:18 -0800 (PST) From: Julian Elischer <julian@ref.tfs.com> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: current@freebsd.org Subject: Re: iBCS2, socksys and all that jazz... Message-ID: <199511221940.LAA09570@ref.tfs.com> In-Reply-To: <199511220807.IAA25398@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 22, 95 08:07:58 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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 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 [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] "Who does BSD?" "We do Chucky, we do." [[ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511221940.LAA09570>