9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A few questions about plan 9
Date: Mon, 12 Dec 2005 13:39:34 -0800	[thread overview]
Message-ID: <33d3d09d10d03990f1102ffd1b115ebb@9netics.com> (raw)
In-Reply-To: <BFA9DDE1-5FE0-4C6C-B20C-92FFF8FDEA8F@gmail.com>

> First off, I've managed to connect to plan9 using drawterm from my  
> powerbook.  I followed the instructions from http://www.cs.bell- 
> labs.com/wiki/plan9/Drawterm_to_your_terminal/diff.html  which worked  
> very well - I do have a query though, it seems to imply that you have  
> to execute "echo 'key user=glenda dom=drawterm.test proto=p9sk1 ! 
> password=loginpassword' > /mnt/factotum/ctl" each time you reboot the  
> machine - is this true, or is this only required on the first use?

check secstore(1)

> 
> I'm also trying to look at my plan9.ini file, after searching the  
> internet, I have discovered that it's on a separate partition which  
> can be accessed using the 9fat: command, executing this command  
> though gives the error message: "mount: can't open /srv/dos: '/srv/ 
> dos' permission denied" - help?!?

check dossrv(4) and look at the permissions on /srv/dos.  it's most
likey due to being drawterm-ed in with a different id than 'bootes',
who owns things on the cpu.  lastly check /rc/bin/9fat: (and friends)
for more hints

> One final question, what resources are there to learn about  
> development under plan9 - I've found bits & pieces, but I'd like to  
> know what is available.

i find that reading the Plan9 sources is very educational.  after that
the contrib directory on sources is useful.



  reply	other threads:[~2005-12-12 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 19:38 Keith Poole
2005-12-12 21:39 ` Skip Tavakkolian [this message]
2005-12-12 21:55   ` Skip Tavakkolian

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=33d3d09d10d03990f1102ffd1b115ebb@9netics.com \
    --to=9nut@9netics.com \
    --cc=9fans@cse.psu.edu \
    /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).