.TH 9SRVFS 4 "Plan 9".SH NAME9srvfs \- add Inferno service to Plan 9 service registry.SH SYNOPSIS.B 9srvfs[.BI -p " perm"].I srvname.I source.SH DESCRIPTION.I 9srvfsis only usable (or indeed of interest) on Inferno hosted under Plan 9.It uses.IR srv9 (3)to make an Inferno service.I sourceavailable to Plan 9 applications via the Plan 9 service registry..I Srv9 (3)must previously have been bound to.B /srvin the current name space, with.B -cto allow file creation (see.IR bind (1))..PP.I Sourcemay be either a command or the name of a directory.If.I sourceis surrounded by braces.RB ( {and.BR } ),it is invoked as a.IR sh (1)command, and its standard input (sic) is posted as Plan 9 service.BI /srv/ srvnamewith permissions.I perm(default: mode 600).Otherwise,.I sourceis taken to be a directory that is the root of a name space to export to Plan 9,an exporting file service is started (see.IR sys-export (2)),and again posted as Plan 9 service.BI /srv/ srvname,and the export terminates when the Plan 9 service filehas been removed and the last mounted instance goes away in Plan 9..SH EXAMPLEMake the current Inferno environment variables available to Plan 9 applications:.IP.EXbind -c '#₪' /srv   # if not already done9srvfs infenv /env.EE.PPThe name space can then be mounted in Plan 9,allowing variables to be read and written in that Inferno environment:.IP.EXmount -c /srv/infenv /n/ftpls /n/ftpcat /n/ftp/emuargsecho masked man >/n/ftp/zorro.EE.SH SOURCE.B /appl/cmd/9srvfs.b.SH SEE ALSO.IR bind (1),.IR srv9 (3),.IR import (4)