From: Balwinder S Dheeman <bdheeman@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Adventures of a home user
Date: Mon, 20 Apr 2009 10:42:14 +0000 [thread overview]
Message-ID: <bm2sb6xdai.ln2@news.homelinux.net> (raw)
In-Reply-To: <ea634cc80904190837j47b7abddh5bb638999b470196@mail.gmail.com>
On 04/19/2009 09:09 PM, Jim Habegger wrote:
> Eric and Anthony, thank you.
>
> I'm stepping through the Plan 9 documentation at
> http://plan9.bell-labs.com/wiki/plan9/documentation/index.html. As you
> noticed, Anthony, I missed a step in adding a new user:
>
> con -l /srv/fscons
>
>
> That didn't work in 9vx either, I imagine for the reasons you explained.
> I'm still way over my head here.
>
> For now I'll use QEMU to step through the Plan 9 documentation, and
> later I might use 9vx for other learning purposes. Now that I've learned
> to change the display dimensions, and use ctrl-alt, it's easy to switch
> between QEMU and my other windows. I've already created a new user.
>
> I won't push my luck tonight. I'll wait until tomorrow to try network
> configuration.
IMHO, you need not switch between your Plan 9 installation under QEMU
and 9vx; Just stick to a real Plan 9 under QEMU and this I hope will
help you better learn, experiment and, or try procedures described on
the wiki and other docs.
I don't who and why one referred you to try 9vx, an abridged version
which is far away from a real or native installation of a Plan 9 under
QEMU, KVM, XEN and, or VMWare. Many a things e.g. page, gs, mail do not
work out of the box as expected under 9vx as yet.
--
Balwinder S "bdheeman" Dheeman Registered Linux User: #229709
Anu'z Linux@HOME (Unix Shoppe) Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP
Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
next prev parent reply other threads:[~2009-04-20 10:42 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 [this message]
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
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=bm2sb6xdai.ln2@news.homelinux.net \
--to=bdheeman@gmail.com \
--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).