From: Brantley Coile <brantley@coraid.com>
To: "corey@bitworthy.net" <corey@bitworthy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] first timer - editing plan9.ini
Date: Sun, 19 Jul 2009 19:04:05 -0400 [thread overview]
Message-ID: <EAF943AE-FA33-4CB6-8645-588440750ADE@coraid.com> (raw)
In-Reply-To: <200907191551.26219.corey@bitworthy.net>
The few minutes spent learning ed(1) will be well repaid. You'll be
one of the smartest guys on your block.
iPhone email
On Jul 19, 2009, at 6:51 PM, Corey <corey@bitworthy.net> wrote:
>
> Ok, so I have my fossil+venti and hopefully soon-to-be cpu and auth-
> server
> booted up for the first time, and I'm in rio as user glenda.
>
> I'm continuing to follow the docs, which is prompting me to edit
> plan9.ini for
> various things.
>
> sam is completely opaque to the uninitiated. (I'm a mere vi fanatic)
>
> Before I go into sitting down and learning sam, it would be nice to
> simply be
> able get the machine running in a minimally satisfactory way, i.e.:
> network
> online, display running at reasonable depth, venti finished, and
> auth-serv
> working.
>
> Can someone give me just the bare minimal sam command/info that I
> need to:
>
> edit a couple lines
> close and save properly
>
>
> ... better yet: is there a simple/minimal editor that doesn't require
> learning a command language to begin using it first?
>
> I began by beginning to read through sam_tut.pdf, and I look forward
> to
> gaining proficiency with it... but not at this moment - I just want
> to get my
> new plan9 box running so I can access it remotely.
>
> As it is, I'm guessing I'm just going to hose my plan9.ini if I try
> editing it
> before I'm well familiar with sam...
>
>
> THanks!
>
>
>
>
next prev parent reply other threads:[~2009-07-19 23:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 22:51 Corey
2009-07-19 22:58 ` hiro
2009-07-19 23:02 ` John Floren
2009-07-19 23:19 ` Corey
2009-07-19 23:25 ` John Floren
2009-07-19 23:35 ` erik quanstrom
2009-07-20 0:08 ` Corey
2009-07-19 23:28 ` Federico G. Benavento
2009-07-19 23:30 ` erik quanstrom
2009-07-19 23:04 ` Brantley Coile [this message]
2009-07-19 23:18 ` Corey
2009-07-20 2:12 ` Skip Tavakkolian
2009-07-20 2:29 ` Corey
2009-07-22 18:09 ` J. R. Mauro
2009-07-24 10:49 ` maht
[not found] ` <4B03FCAB-BFF1-483F-BCF8-369F0E6711C9@gmail.com>
2009-07-24 18:05 ` Rodolfo (kix)
2009-07-24 19:18 ` David Leimbach
2009-07-25 9:56 ` Ethan Grammatikidis
2009-07-20 14:40 ` David Leimbach
2009-07-20 2:50 ` Jason Catena
2009-07-20 3:10 ` Lyndon Nerenberg
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=EAF943AE-FA33-4CB6-8645-588440750ADE@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.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).