9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Adding a new user on 9-Front
Date: Mon, 23 Dec 2013 16:42:57 +0100	[thread overview]
Message-ID: <1130bb1f67914598d4d0139db63c74ad@felloff.net> (raw)
In-Reply-To: <CABwHSOsoOST_Eh0PyFaybQGTHu8vfzrmVMsWvnG-g4L2L2RHcQ@mail.gmail.com>

that command file is really a bidirectional pipe. you didnt
read the pipe so you do not see the command response.

to get in a interactive dialog with the fileserver, you can run:

con -Cl /srv/cwfs.cmd

to leave this dialog, enter <Ctrl>+\<enter> and on cons >>>
prompt, type q

the fileserver console commands for cwfs are described in fs(8).

note, this is for the cwfs fileserver. the standard labs plan9
uses a the fossil fileserver which has different set of commands
and uses /srv/fscons command file by convention.

please take your time. read nemos book, the manuals and the
the wiki. do some exploration before you want to setup everything
to your liking. this is the 2nd step before the first.

--
cinap



  parent reply	other threads:[~2013-12-23 15:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  2:37 Blake McBride
2013-12-23  5:19 ` Sergey Zhilkin
2013-12-23  6:15   ` Matthew Veety
2013-12-23 13:34     ` erik quanstrom
2013-12-23 13:46       ` Richard Miller
2013-12-23 13:55         ` erik quanstrom
2013-12-23 14:36   ` Blake McBride
2013-12-23 15:10   ` Blake McBride
2013-12-23 15:32     ` Bence Fábián
2013-12-23 17:13       ` sl
2013-12-23 18:00       ` Blake McBride
2013-12-23 18:03         ` Blake McBride
2013-12-23 18:28           ` Kurt H Maier
2013-12-23 20:03             ` Blake McBride
2013-12-23 20:18               ` erik quanstrom
2013-12-23 20:23               ` Rubén Berenguel
2013-12-23 20:48                 ` Blake McBride
2013-12-23 21:20                   ` Steve Simon
2013-12-23 20:51               ` Kurt H Maier
2013-12-23 21:45                 ` Blake McBride
2013-12-23 22:00                   ` Matthew Veety
2013-12-23 22:07                   ` sl
2013-12-23 22:45                     ` erik quanstrom
2013-12-23 23:47                       ` sl
2013-12-23 23:54                       ` Kurt H Maier
2013-12-24 12:06                         ` Steffen Daode Nurpmeso
2013-12-24 12:24                           ` lucio
2013-12-24 17:47                             ` Steffen Daode Nurpmeso
2013-12-25  5:30                               ` lucio
2013-12-25  5:58                         ` Federico G. Benavento
2013-12-24  0:16                   ` Kurt H Maier
2013-12-24  0:57                     ` andrey mirtchovski
2013-12-24  2:49                       ` Skip Tavakkolian
2013-12-24  3:03                         ` Bruce Ellis
2013-12-23 19:18           ` Richard Miller
2013-12-23 19:30             ` cinap_lenrek
2013-12-23 19:37               ` erik quanstrom
2013-12-23 20:29                 ` cinap_lenrek
2013-12-23 15:42     ` cinap_lenrek [this message]
2013-12-23  9:38 ` Richard Miller

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=1130bb1f67914598d4d0139db63c74ad@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --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).