9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john@csplan9.rit.edu
To: 9fans@9fans.net
Subject: Re: [9fans] Adventures of a home user
Date: Tue, 21 Apr 2009 11:26:19 -0400	[thread overview]
Message-ID: <29b5d70baba452f2446d71f0a37f302d@csplan9.rit.edu> (raw)
In-Reply-To: <ea634cc80904210210g425958e8w92b3ca7383bdc0a@mail.gmail.com>

> I tried webfs and got an error message, so I ran webcookies, and then I was
> able to run webfs without an error message. Then I was able to run abaco.
> Now I need to learn how to use it. I thought maybe I could just type in a
> URL and 2-click "Get," but nothing happened.
>

You execute "New", then type the URL INCLUDING http:// in the blank
tag that comes up (below the "Del Snarf Get" commands) and either hit
enter or execute "Get".


> I'll need to learn how to access host and network resources in QEMU before
> I'll be able to mount my fat partition.

Here's a different idea: set up QEMU as a standalone CPU server (per the
instructions on the wiki) and use drawterm to connect. You can then access
host files via drawterm; they'll be in /mnt/term


> I decided not to add the network and web commands to my profile, because I'm
> not sure I'll be wanting to use them every time, while I'm learning to use
> QEMU and Plan 9. I put the network commands in a file. Now I need to learn
> how to write an executable script. For now I cat the file, then I select it
> and send it. For the Web, I'll just type webfs when I need it.

How to write an executable script? Don't you use Unix? It's the same:
1. Put #!/bin/rc at the top of your file
2. chmod +x file

You could have easily looked at something like /rc/bin/sig or whatever to
figure out the same stuff, but I guess it continues to be easier to post on
9fans than to think.


John




  parent reply	other threads:[~2009-04-21 15:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  1:01 Jim Habegger
2009-04-19  1:05 ` john
2009-04-19  1:08 ` erik quanstrom
2009-04-19 10:15 ` yy
2009-04-19 14:16 ` Jim Habegger
2009-04-19 14:34   ` erik quanstrom
2009-04-19 14:43   ` Anthony Sorace
2009-04-19 15:37   ` Jim Habegger
2009-04-20 10:42     ` Balwinder S Dheeman
2009-04-21  7:55       ` Jim Habegger
2009-04-21 22:03         ` blstuart
2009-04-20  5:01 ` Jim Habegger
2009-04-20  5:13   ` andrey mirtchovski
2009-04-20  5:38     ` André Günther
2009-04-20  5:22   ` Federico G. Benavento
2009-04-20  7:14 ` Jim Habegger
2009-04-21  3:38 ` Jim Habegger
2009-04-21  5:14   ` john
2009-04-21  7:05   ` Federico G. Benavento
2009-04-21  3:52 ` Jim Habegger
2009-04-21  3:55   ` Jim Habegger
2009-04-21 12:06     ` erik quanstrom
2009-04-21 22:13       ` blstuart
2009-04-21  6:02 ` Jim Habegger
2009-04-21  6:31   ` Anthony Sorace
2009-04-21  6:59     ` Jim Habegger
2009-04-21  9:10 ` Jim Habegger
2009-04-21 11:26   ` erik quanstrom
2009-04-21 15:26   ` john [this message]
2009-04-21 15:34     ` erik quanstrom
2009-04-21 20:01 ` Jim Habegger
2009-04-21 21:28   ` Karin Willers
2009-04-21 22:23   ` blstuart
2009-04-22  0:29     ` john
2009-04-22  1:07       ` Jim Habegger
2009-04-23  9:12 ` Jim Habegger
2009-04-23 10:23   ` Eris Discordia
2009-04-23 15:55     ` maht

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=29b5d70baba452f2446d71f0a37f302d@csplan9.rit.edu \
    --to=john@csplan9.rit.edu \
    --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).