9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /net different from sockets, but better?
Date: Sun,  8 Feb 2009 13:46:44 -0500	[thread overview]
Message-ID: <3aaafc130902081046r6fc2797du3490eee4580ff660@mail.gmail.com> (raw)
In-Reply-To: <9511f83e0902061913t2ff2c26bvd446ffe7ed8c30a0@mail.gmail.com>

Since I'm new here, hi everyone!

On Fri, Feb 6, 2009 at 10:13 PM, Rahul Murmuria <rahul.is.also@gmail.com> wrote:
> I am planning on porting the /net concept of Plan9 to Linux.
>

I've been thinking about this for a few months. If you'd like help,
let me know, I'd be more than happy to pitch in.

> My Plan:
> Use libfs[1] to write a synthetic filesystem in Linux, much like
> securityfs[2], or /proc. This libfs based code will make calls to the TCP/IP
> stack on the linux, and basically be an alternative to the Linux kernel
> sockets. As a result I will expose networking using /net, instead of POSIX
> to the applications.
>
> My Motivation:
> Glendix[3]
>
> My Question:
> I know that using /net instead of sockets is very different. But is it
> better? Specially from the networking side of things, not from application
> development point of view (which we have already established is simpler, by
> example).
>
> [1] http://lwn.net/Articles/57369/
> [2] http://lwn.net/Articles/153366/
> [3] http://glendix.org/   and   http://glendix.org/glendix_iwp9_2008.pdf
> and    http://www.osnews.com/story/20588/
>
> Regards,
>
> --
> Rahul Murmuria
>
>



      parent reply	other threads:[~2009-02-08 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  3:13 Rahul Murmuria
2009-02-07 13:47 ` Eric Van Hensbergen
2009-02-08 19:03   ` Rahul Murmuria
2009-02-08 18:46 ` J.R. Mauro [this message]

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=3aaafc130902081046r6fc2797du3490eee4580ff660@mail.gmail.com \
    --to=jrm8005@gmail.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).