From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII From: dave.l@mac.com In-reply-to: <973562.76924.qm@web30906.mail.mud.yahoo.com> Date: Tue, 21 Jun 2011 23:42:22 +0100 Message-id: References: <973562.76924.qm@web30906.mail.mud.yahoo.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] RFS alternatives (Was: Living with Plan 9) Topicbox-Message-UUID: f37def7e-ead6-11e9-9d60-3106f5b1d025 > Thanks for the info, but the devices encumbered with ioctls are the tricky ones and even if they can be sorted out I'm sure there are some other traps out there. Too bad there are no RFS gurus lurking here to offer their wisdom on remoting devices. I'm no RFS guru, thank deity, but I did RTFC once and "F" was apposite. ioctl was handled by having the client "know" exactly what each ioctl "looked like", i.e. it only worked for known cases. There was a humungous switch which knew the "right stuff" to copy in&out, how to byte swap and align any words, structs etc. After deciding what the "right stuff" was, it copied in the "right stuff" from user space, passed over the call to the server, the server then executed it and passed back the "right stuff" to the client, the client then copied out the "right stuff", then I started losing the will to live. Dave.