Re: [9fans] cpu/file/terminal server of my dream

[presotto@plan9.bell-labs.com]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

The easiest hackwould be to change /sys/src/9/boot/boopip.c's
connecttcp() to fork off a filter to do what the fcall
module used to.  Look at the funcion filter() in /sys/src/cmd/cpu.c.
It wouldn't necessarily be fast but it would be functional.  If
noone gets to it before I get back to MH (a week or two from now),
I'll do it myself.

[-- Attachment #2: Type: message/rfc822, Size: 1948 bytes --]

From: miller@hamnavoe.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu/file/terminal server of my dream
Date: Wed, 28 Jun 2000 18:34:16 BST
Message-ID: <E137g9C-000A2o-0V@anchor-post-31.mail.demon.net>

I wrote:
> u9fs will not work as root file system for diskless clients without some
> changes to the kernel.  Since u9fs serves via tcp not il protocol, you would
> have to interpose something like aux/fcall to reconstruct 9p message
> boundaries.

And Steve Kotsopoulos <steve@nevex.com> wrote:

> is this something new with the 3rd edition?
> under 2nd edition I'm using a u9fs fileserver just fine

Yes, the old Plan 9 had fcall(3) stream module within the kernel which
the boot process pushed onto a tcp connection.  This is gone, along
with all kernel stream stuff.

-- Richard Miller