From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] /tmp dissappearance
Date: Sun, 20 May 2012 22:33:14 +0100 [thread overview]
Message-ID: <20120520223314.52aa428d@inari.ethans.dre.am> (raw)
In-Reply-To: <CAM8pOuPi+_EOGm8DGWUvUiC7gViRsgT+H2j8vVeHLh5tmi=xig@mail.gmail.com>
On Sun, 20 May 2012 15:21:48 -0600
Burton Samograd <burton.samograd@gmail.com> wrote:
> Another noob question; how do you start the fs console on cwfs64x? I
> tried 'con /srv/cwfs.cmd' but get nothing back. The docs I can find
> all relate to fossil and which doesn't look to work the same.
I'm doing this today too. I found I have to type blind, I don't see the prompt or my typing until I press return. You might want to compose your commands in another window and paste. The commands are somewhat different to fossil, 'help' on the console gives a list with very terse explanations; I couldn't find a man page. The least clear command, 'duallow name' allows name to mount with rw permission.
I also don't see a chown or chgrp equivalent on the console (which might be my bad eyes), but after reading the previous thread I decided not to worry about it.
next prev parent reply other threads:[~2012-05-20 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 16:56 Burton Samograd
2012-05-20 20:36 ` Rudolf Sykora
2012-05-20 20:49 ` andrew zerger
2012-05-20 20:59 ` Charles Forsyth
2012-05-20 21:16 ` Burton Samograd
2012-05-20 21:21 ` Burton Samograd
2012-05-20 21:33 ` Ethan Grammatikidis [this message]
2012-05-20 21:42 ` cinap_lenrek
2012-05-21 5:05 ` kokamoto
[not found] <CAM8pOuNE-CK41emPuCngMPRqye194i8C-tbDZRK0vSXZHfDe7Q@mail.gmail.c>
2012-05-20 16:59 ` erik quanstrom
2012-05-20 17:10 ` Burton Samograd
2012-05-20 17:15 ` Burton Samograd
2012-05-20 17:21 ` andrew zerger
2012-05-20 17:31 ` Burton Samograd
2012-05-20 17:29 ` David du Colombier
2012-05-20 18:04 ` Anthony Sorace
2012-05-20 18:27 ` David du Colombier
2012-05-20 20:34 ` steve
2012-05-21 0:46 ` erik quanstrom
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=20120520223314.52aa428d@inari.ethans.dre.am \
--to=eekee57@fastmail.fm \
--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).