From owner-freebsd-current Wed Nov 22 11:40:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA05546 for current-outgoing; Wed, 22 Nov 1995 11:40:33 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA05541 for ; Wed, 22 Nov 1995 11:40:30 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id LAA09570; Wed, 22 Nov 1995 11:40:18 -0800 From: Julian Elischer Message-Id: <199511221940.LAA09570@ref.tfs.com> Subject: Re: iBCS2, socksys and all that jazz... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 22 Nov 1995 11:40:18 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199511220807.IAA25398@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 22, 95 08:07:58 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1075 Sender: owner-current@freebsd.org Precedence: bulk > > > 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." [[ >