9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Lluís Batlle" <viriketo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] Porting to plan9 / PF_UNIX
Date: Sat, 14 Apr 2007 17:34:54 +0200	[thread overview]
Message-ID: <45219fb00704140834u155a34d6gf757105eab8ce4e0@mail.gmail.com> (raw)

I'm the developer of a Unix program that may be useful in plan9, and
as an exercise, I'd like it to build in plan9 native.

Now, I've written it assuming POSIX (int signals, PF_UNIX available,
BSD sockets API, ...). I know more or less some details on plan9 (per
process namespaces, network not in a library to link with, notes,
...), but I barely know the 'common' use of the environment.

My concern is that I need some local processes to communicate to a
local server. Now I use a SOCK_STREAM PF_UNIX in a path in /tmp, where
I suppose I can write. I think it's something I can suppose in a POSIX
system, but not in plan9.
How would you connect local processes (which can be launched at any
time) with a central server in plan9? Making that central server serve
a filesystem, where the clients write/read?
If I knew what's the path I should follow, I could think more easily
on a proper API for POSIX and Plan9 for my program.

I may not have not worked in plan9 enough to deserve your attention,
but I hope a quick answer (even in the form of "man ___") will not
take much time.

btw, the program I'd like to be able to run in plan9 is
http://vicerveza.homeunix.net/~viric/soft/ts/ . I wrote it because I
couldn't find anything similar to fit my needs, and maybe in plan9 you
already have something quick-and-useful for that purpose, and 'ts'
would not make any sense in p9 now. That's also something I'd be glad
to know.

Thanks in advance,
Lluís.


             reply	other threads:[~2007-04-14 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-14 15:34 Lluís Batlle [this message]
2007-04-14 15:55 ` W B Hacker
2007-04-14 17:15   ` Lluís Batlle
2007-04-14 17:28     ` Russ Cox
2007-04-14 17:44       ` Lluís Batlle
2007-04-14 21:17         ` ron minnich
2007-04-15 17:41           ` Lluís Batlle
2007-04-14 19:29     ` W B Hacker
2007-04-14 16:13 ` Francisco J Ballesteros
2007-04-14 17:01 ` Uriel
2007-04-14 21:28 ` John Stalker

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=45219fb00704140834u155a34d6gf757105eab8ce4e0@mail.gmail.com \
    --to=viriketo@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).