From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Adding a new user on 9-Front
Date: Mon, 23 Dec 2013 14:03:53 -0600 [thread overview]
Message-ID: <CABwHSOtVxbK-6tt-+w9GE4=MWvtRQ3jndesT5hBfristtCEwZA@mail.gmail.com> (raw)
In-Reply-To: <20131223182840.Horde.HuKfFKF2fZoroKVTFstUiw4@ssl.eumx.net>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Documentation is always clear to people who already know the material but
use the documentation as a reminder. It is difficult for a newbie to
differentiate out-of-date material, branch specific material, and valid
documentation. I am providing feedback from a newbie's perspective. You
can either take advantage of some of the feedback to make it easier for a
newbie (that cannot reason) thus increasing the number of users, or you can
insult them until they leave. I apologize for not being as smart as you.
On Mon, Dec 23, 2013 at 12:28 PM, Kurt H Maier <khm@sciops.net> wrote:
> Quoting Blake McBride <blake@mcbride.name>:
>
> Or perhaps:
>>
>> echo newuser USER-NAME >>/srv/cwfs.cmd
>>
>> replace USER-NAME with the new user's name. If most commands are in
>> lowercase, it might make sense to use uppercase names as things that need
>> to be specified.
>>
>
> Or perhaps we use the documentation as a way to weed out people who cannot
> reason.
>
> khm
>
>
>
[-- Attachment #2: Type: text/html, Size: 2434 bytes --]
next prev parent reply other threads:[~2013-12-23 20:03 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 [this message]
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
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='CABwHSOtVxbK-6tt-+w9GE4=MWvtRQ3jndesT5hBfristtCEwZA@mail.gmail.com' \
--to=blake@mcbride.name \
--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).