From: dave.l@mac.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] RFS alternatives (Was: Living with Plan 9)
Date: Tue, 21 Jun 2011 23:42:22 +0100 [thread overview]
Message-ID: <CC391EDE-A712-43F3-9F44-C725F5924D2C@mac.com> (raw)
In-Reply-To: <973562.76924.qm@web30906.mail.mud.yahoo.com>
> 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 "\x10right 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.
next prev parent reply other threads:[~2011-06-21 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 17:35 rbnsw-plan9
2011-06-21 22:42 ` dave.l [this message]
2011-06-22 15:16 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 17:07 rbnsw-plan9
2011-06-27 17:20 ` ron minnich
2011-06-27 17:45 ` Jeff Sickel
2011-06-27 18:18 ` Skip Tavakkolian
2011-06-27 19:13 ` dexen deVries
2011-06-27 20:17 ` erik quanstrom
2011-06-27 21:23 ` dexen deVries
2011-06-30 15:31 ` Yaroslav
2011-06-27 18:26 ` Richard Miller
2011-06-27 17:24 ` erik quanstrom
2011-06-30 17:11 ` rbnsw-plan9
2011-06-30 20:07 ` erik quanstrom
2011-06-11 19:26 rbnsw-plan9
2011-06-21 12:51 ` Eric Van Hensbergen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CC391EDE-A712-43F3-9F44-C725F5924D2C@mac.com \
--to=dave.l@mac.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).