9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Van Jacobsen's network stack restructure
Date: Wed,  1 Feb 2006 16:49:03 -0800	[thread overview]
Message-ID: <3e1162e60602011649y2896f4baxf30b9b4db82268e6@mail.gmail.com> (raw)
In-Reply-To: <ce472274c492c634c644c4040ebfe091@quanstro.net>

On 2/1/06, quanstro@quanstro.net <quanstro@quanstro.net> wrote:
> c'mon. linux has consistently gone the other way on this issue.
> linux doesn't even have a device node for network interfaces.
>
> i don't know anything about the reasoning for this. efficiency?
> support for a static /dev? i don't know.
>

The bash shell supports /dev/tcp.... kind of evil but you can make
connections and send strings via file redirection with it.

Dave

>
> - erik
>
> On Wed Feb  1 11:50:33 CST 2006, uriel@cat-v.org wrote:
> > > anyone seen this?
> > >
> > > http://www.lemis.com/grog/Documentation/vj/
> > Yes quite interesting, and here is a nice writeup:
> > http://vger.kernel.org/~davem/cgi-bin/blog.cgi/2006/01/27
> >
> > > i don't know if his methods have any application to Plan 9, since the
> > > Plan 9 IP stack doesn't seem to have the lineage of the linux and bsd
> > > stacks. i am not intimate with the IP stack code, but it might bear a
> > > lookover.
> > >From the very little I know about our IP stack(which comes from reading Nemo's
> > excellent commentary on the 3rd edition kernel source), we might be not too
> > far from a design similar to what is described there, but I might be completely
> > wrong.
> >
> > And even if it's not, /net makes it easy to put the IP stack in user space without
> > having to change a single line of application code. Ah, the more I deal with
> > Plan 9, the more I love it :)
> >
> > Maybe we should try to convince those lunix people to replace sockets with
> > something like /net? ;)
>


  parent reply	other threads:[~2006-02-02  0:49 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 18:20 quanstro
2006-02-02  0:48 ` David Leimbach
2006-02-02  0:49 ` David Leimbach [this message]
2006-02-02  2:12   ` Ronald G Minnich
2006-02-02  2:22     ` Christopher Nielsen
2006-02-02  8:24     ` uriel
2006-02-02 10:35       ` Charles Forsyth
2006-02-02 11:40         ` ems
     [not found]         ` <000001c627ee$35f3aee0$14aaa8c0@utelsystems.local>
2006-02-02 12:33           ` "Nils O. Selåsdal"
2006-02-03  3:36         ` Ronald G Minnich
2006-02-03  3:44           ` erik quanstrom
2006-02-03  3:48           ` Christopher Nielsen
2006-02-02 14:36       ` jmk
2006-02-02 16:48         ` Brantley Coile
2006-02-02 18:20           ` ems
2006-02-02 18:24             ` andrey mirtchovski
2006-02-02 19:23               ` Brantley Coile
2006-02-02 19:39               ` jmk
2006-02-02 23:28                 ` Dan Cross
2006-02-02 19:16             ` David Leimbach
2006-02-02 21:28           ` Andy Newman
2006-02-03  3:38       ` ems
2006-02-02 16:59     ` David Leimbach
2006-02-02 17:21       ` C H Forsyth
2006-02-02 19:14         ` David Leimbach
2006-02-02 20:46           ` Charles Forsyth
2006-02-02 20:57             ` Charles Forsyth
2006-02-03  3:55           ` Ronald G Minnich
2006-02-03  4:06             ` erik quanstrom
2006-02-03  4:07             ` andrey mirtchovski
2006-02-03  4:12               ` ems
2006-02-03  4:25                 ` andrey mirtchovski
2006-02-06  4:25             ` Dave Eckhardt
2006-02-10 19:15               ` rog
2006-02-11  1:20                 ` geoff
2006-02-11  1:59                   ` jmk
2006-02-20 20:37                   ` Paweł Lasek
2006-02-20 20:54                     ` jmk
2006-02-20 23:11                       ` Ronald G Minnich
2006-02-20 23:30                         ` Charles Forsyth
2006-02-02  2:11 ` Ronald G Minnich
     [not found] <000101c6285f$54291320$14aaa8c0@utelsystems.local>
2006-02-03  7:20 ` "Nils O. Selåsdal"
     [not found] <6.0.2.0.0.20060203132930.01c25178@pop.monitorbm.co.nz>
2006-02-03  3:30 ` Andrew Simmons
2006-02-03  3:35   ` jmk
2006-02-03  3:41     ` Andrew Simmons
2006-02-03  3:45       ` ems
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03  2:09 quanstro
2006-02-03  1:00 quanstro
2006-02-03  1:11 ` Christopher Nielsen
2006-02-03  0:39 quanstro
2006-02-02 17:43 quanstro
2006-02-03  0:24 ` geoff
2006-02-03  0:31   ` George Michaelson
2006-02-03  0:30 ` Russ Cox
2006-02-03  1:42 ` Aki M Nyrhinen
2006-02-03  3:33   ` Marina Brown
2006-02-02 17:14 quanstro
2006-02-01 20:50 quanstro
2006-02-02 19:29 ` Derek Fawcus
2006-02-01 20:35 quanstro
2006-02-01 19:13 quanstro
2006-02-02  1:27 ` Russ Cox
2006-02-02  2:01   ` ems
2006-02-02  2:44     ` George Michaelson
2006-02-01 18:55 quanstro
2006-02-01  4:28 Christopher Nielsen
2006-02-01  5:57 ` ems
2006-02-01  6:00   ` Christopher Nielsen
2006-02-01  6:06     ` ems
2006-02-01  6:03   ` Federico G. Benavento
2006-02-01 17:46 ` uriel
2006-02-01 18:10   ` Skip Tavakkolian
2006-02-02 13:37 ` Charles Forsyth
2006-02-02 17:40   ` Bakul Shah
2006-02-02 18:01     ` C H Forsyth
2006-02-02 18:16       ` Bakul Shah
2006-02-02 19:21         ` David Leimbach
2006-02-03  3:44           ` Ronald G Minnich

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