---------- Forwarded Message ----------
Return-Path: <[EMAIL PROTECTED]>
Received: from fencepost.gnu.org ([199.232.76.164]) by mailin00.sul.t-online.de
with esmtp id 156tMg-0sjpc8a; Mon, 4 Jun 2001 14:21:46 +0200
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156tJD-0007H6-00; Mon, 04 Jun 2001 08:18:11 -0400
Received: from mailout02.sul.t-online.com ([194.25.134.17]
helo=mailout02.sul.t-online.de)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156tIy-0007G3-00
for <[EMAIL PROTECTED]>; Mon, 04 Jun 2001 08:17:56 -0400
Received: from fwd05.sul.t-online.de
by mailout02.sul.t-online.de with smtp
id 156tIt-000318-08; Mon, 04 Jun 2001 14:17:51 +0200
Received: from odin (320068295437-0001@[217.81.139.166]) by fwd05.sul.t-online.com
with smtp id 156tIi-2KlhNwC; Mon, 4 Jun 2001 14:17:40 +0200
Content-Type: text/plain;
charset="iso-8859-1"
From: [EMAIL PROTECTED] (Anselm Garbe)
To: [EMAIL PROTECTED]
Subject: Fwd: Re: named ports <-> trivfs translator!
X-Mailer: KMail [version 1.2]
MIME-Version: 1.0
Message-Id: <01060414204203.00328@odin>
Content-Transfer-Encoding: 8bit
X-Sender: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.3
Precedence: bulk
List-Help: <mailto:[EMAIL PROTECTED]?subject=help>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=subscribe>
List-Id: Users list for the GNU Hurd <help-hurd.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/help-hurd/>
Date: Mon, 4 Jun 2001 14:20:42 +0200
UNSUBSCRIBE
---------- Forwarded Message ----------
Return-Path: <[EMAIL PROTECTED]>
Received: from fencepost.gnu.org ([199.232.76.164]) by
mailin00.sul.t-online.de
with esmtp id 156csx-0hVIjQa; Sun, 3 Jun 2001 20:45:59 +0200
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156cda-0005at-00; Sun, 03 Jun 2001 14:30:06 -0400
Received: from [212.23.136.22] (helo=localhost)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156cbC-0005W2-00
for <[EMAIL PROTECTED]>; Sun, 03 Jun 2001 14:27:38 -0400
Received: from marcus by localhost with local (Exim 3.22 #1 (Debian))
id 156cb3-00017X-00; Sun, 03 Jun 2001 20:27:29 +0200
From: Marcus Brinkmann <[EMAIL PROTECTED]>
To: Johan Rydberg <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: named ports <-> trivfs translator!
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.18i
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.3
Precedence: bulk
List-Help: <mailto:[EMAIL PROTECTED]?subject=help>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=subscribe>
List-Id: Users list for the GNU Hurd <help-hurd.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/help-hurd/>
Date: Sun, 3 Jun 2001 20:27:29 +0200
Status: RO
X-Status: O
On Sat, Jun 02, 2001 at 06:43:37PM +0200, Johan Rydberg wrote:
>
> Hi!
>
> I'm thinking about implementing a small server. What is
> the easiest way for a client to get the mach-port for the
> server?
You can advertise your msg port to the proc server with the proc_setmsgport
RPC (send it to the port you get with getproc() from libc). Then a client
can get the port with the proc_getmsgport RPC (requires the PID of the
server process). This is a bit like the Mach nameserver, except you access
by PID rather than some name.
The canonical way to do it on the Hurd is to attach the server to some node
in the filesystem, that means, you write a translator which you attach with
settrans, or you write a program that installs itself as a translator
somewhere. libtrivfs helps a lot for that. (For the latter, see how pfinet
installs the tunnel "device" in pfinet/tunnel.c (setup_tunnel_device).
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
On Sat, Jun 02, 2001 at 06:43:37PM +0200, Johan Rydberg wrote:
> Hi!
>
> I'm thinking about implementing a small server. What is
> the easiest way for a client to get the mach-port for the
> server?
You can advertise your msg port to the proc server with the proc_setmsgport
RPC (send it to the port you get with getproc() from libc). Then a client
can get the port with the proc_getmsgport RPC (requires the PID of the
server process). This is a bit like the Mach nameserver, except you access
by PID rather than some name.
The canonical way to do it on the Hurd is to attach the server to some node
in the filesystem, that means, you write a translator which you attach with
settrans, or you write a program that installs itself as a translator
somewhere. libtrivfs helps a lot for that. (For the latter, see how pfinet
installs the tunnel "device" in pfinet/tunnel.c (setup_tunnel_device).
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
-------------------------------------------------------
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
UNSUBSCRIBE
---------- Forwarded Message ----------
Return-Path: <[EMAIL PROTECTED]>
Received: from fencepost.gnu.org ([199.232.76.164]) by
mailin00.sul.t-online.de
with esmtp id 156csx-0hVIjQa; Sun, 3 Jun 2001 20:45:59 +0200
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156cda-0005at-00; Sun, 03 Jun 2001 14:30:06 -0400
Received: from [212.23.136.22] (helo=localhost)
by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
id 156cbC-0005W2-00
for <[EMAIL PROTECTED]>; Sun, 03 Jun 2001 14:27:38 -0400
Received: from marcus by localhost with local (Exim 3.22 #1 (Debian))
id 156cb3-00017X-00; Sun, 03 Jun 2001 20:27:29 +0200
From: Marcus Brinkmann <[EMAIL PROTECTED]>
To: Johan Rydberg <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: named ports <-> trivfs translator!
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.18i
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.3
Precedence: bulk
List-Help: <mailto:[EMAIL PROTECTED]?subject=help>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=subscribe>
List-Id: Users list for the GNU Hurd <help-hurd.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/help-hurd>,
<mailto:[EMAIL PROTECTED]?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/help-hurd/>
Date: Sun, 3 Jun 2001 20:27:29 +0200
Status: RO
X-Status: O
On Sat, Jun 02, 2001 at 06:43:37PM +0200, Johan Rydberg wrote:
> Hi!
>
> I'm thinking about implementing a small server. What is
> the easiest way for a client to get the mach-port for the
> server?
You can advertise your msg port to the proc server with the proc_setmsgport
RPC (send it to the port you get with getproc() from libc). Then a client
can get the port with the proc_getmsgport RPC (requires the PID of the
server process). This is a bit like the Mach nameserver, except you access
by PID rather than some name.
The canonical way to do it on the Hurd is to attach the server to some node
in the filesystem, that means, you write a translator which you attach with
settrans, or you write a program that installs itself as a translator
somewhere. libtrivfs helps a lot for that. (For the latter, see how pfinet
installs the tunnel "device" in pfinet/tunnel.c (setup_tunnel_device).
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
On Sat, Jun 02, 2001 at 06:43:37PM +0200, Johan Rydberg wrote:
> Hi!
>
> I'm thinking about implementing a small server. What is
> the easiest way for a client to get the mach-port for the
> server?
You can advertise your msg port to the proc server with the proc_setmsgport
RPC (send it to the port you get with getproc() from libc). Then a client
can get the port with the proc_getmsgport RPC (requires the PID of the
server process). This is a bit like the Mach nameserver, except you access
by PID rather than some name.
The canonical way to do it on the Hurd is to attach the server to some node
in the filesystem, that means, you write a translator which you attach with
settrans, or you write a program that installs itself as a translator
somewhere. libtrivfs helps a lot for that. (For the latter, see how pfinet
installs the tunnel "device" in pfinet/tunnel.c (setup_tunnel_device).
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
-------------------------------------------------------
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
-------------------------------------------------------
_______________________________________________
Help-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-hurd
