9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Federico G. Benavento" <benavento@gmail.com>
To: 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 20:28:35 -0300	[thread overview]
Message-ID: <32d987d50907191628l4feb3ab4l43162a816b83923c@mail.gmail.com> (raw)
In-Reply-To: <200907191619.20170.corey@bitworthy.net>

cp plan9.ini plan9.ini.old

acme didn't see /n/9fat/plan9.ini because the 9fat partition wasn't
mounted in its namespace.


On Sun, Jul 19, 2009 at 8:19 PM, Corey<corey@bitworthy.net> wrote:
> On Sunday 19 July 2009 16:02:20 John Floren wrote:
>> On Sun, Jul 19, 2009 at 3:51 PM, Corey<corey@bitworthy.net> wrote:
> <snip>
>> > Can someone give me just the bare minimal sam command/info that I need
>> > to:
>> >
>> > edit a couple lines
>> > close and save properly
>> >
>> You can use acme if you want.
>>
>
> That was my first effort (though it suffered similar issue: must acclimate to
> acme before you can configure your new installation) - however, when I
> tried to traverse /n/9fat/plan9.ini, acme complained that there was no
> such file; so, being completely new to plan 9, my progress at that point
> came to a complete standstill.
>
>
>> Otherwise:
>>
>> % 9fat:
>> % sam /n/9fat/plan9.ini
>> right click and select the filename, then midclick in the white area
>> of the sam window. This should bring up the file.
>> Make your changes, then click in the light blue part of the sam
>> window. Type 'w' and hit enter, then type 'q' and hit enter. This
>> should write and quit.
>>
>
> Thanks - I'll try this.
>
>
> Another quick question:
>
> Just to be safe, I would like to copy the org plan9.ini before I try to modify
> it; so if I hose it, I can move it back; how would I do this?
>
>
> Cheers
>
>
>
>
>



--
Federico G. Benavento



  parent reply	other threads:[~2009-07-19 23:28 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 [this message]
2009-07-19 23:30       ` erik quanstrom
2009-07-19 23:04 ` Brantley Coile
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=32d987d50907191628l4feb3ab4l43162a816b83923c@mail.gmail.com \
    --to=benavento@gmail.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).