9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexandru Gheorghe <alghe.global@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Welcome Plan 9 community
Date: Tue,  4 Mar 2014 00:19:11 +0200	[thread overview]
Message-ID: <5314FFDF.20108@gmail.com> (raw)
In-Reply-To: <5AFC3B27-E0C4-4D74-91B2-BBBA28FAD3B4@orthanc.ca>

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

On 03/03/2014 10:53 PM, Lyndon Nerenberg wrote:
> 
> On Mar 3, 2014, at 12:52, Alexandru Gheorghe <alghe.global@gmail.com> wrote:
> 
>> should we gather some configuration steps/examples for known stable
>> builds of vbox and post them in a wiki somewhere(?)
> 
> Yes!  That's what the wiki is for.
> 

sure, I agree. I am only enquiring so as to brainstorm if we should
actually (and be better of) providing a sort of how-to in debugging
network setup on plan9 (besides what is already on the net).

i.e., even if somebody runs into trouble (ultimately), it is better off
posting his output of:

cat /net/ndb

ls /net | grep ether (optional)
ls /net/ether*

ip/ipconfig -DGP


in case he/she is running in recv timeout for 15 secs; shortcut:

ppid=`{ps | grep ipconfig | awk '{print $2}'}
echo kill > /proc/$ppid/note

sorry for the `   as I am writing from GNU/Linux


this may not fully represent what is needed, but this is what I could
gather in few minutes of man pages and some trial and error, after only
30 minutes of Plan9 experience. so I am sure far more experienced users
from the mailinglist can contribute to the article

I will try to tackle it this weekend from this approach/point of view,
maybe I can come up with something rather useful, if not, at least
networking setup for the build I use of vbox/os/version etc.
-- 
; Alexandru Gheorghe
; alghe.global {at} gmail {dot} com
; OpenPGP key ID 0xCAF985D2


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  reply	other threads:[~2014-03-03 22:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 22:16 Szymon Olewniczak
2014-03-03  1:05 ` erik quanstrom
2014-03-03  5:54 ` Grant Mather
2014-03-03 18:05 ` Peter Hull
2014-03-03 19:32   ` Lyndon Nerenberg
2014-03-03 20:28     ` Alexandru Gheorghe
2014-03-03 20:37       ` erik quanstrom
2014-03-03 20:52         ` Alexandru Gheorghe
2014-03-03 20:53           ` Lyndon Nerenberg
2014-03-03 22:19             ` Alexandru Gheorghe [this message]
2014-03-05 20:23               ` Alexandru Gheorghe
2014-03-05 20:43                 ` Peter Hull
2014-03-05 20:48                   ` Alexandru Gheorghe
2014-03-05 20:45                 ` Alexandru Gheorghe
2014-03-05 20:46                 ` Peter Hull
2014-03-03 21:50           ` Peter Hull
2014-03-03 21:06         ` Lyndon Nerenberg
2014-03-03 17:15 Szymon Olewniczak
2014-03-03 17:23 ` Szymon Olewniczak

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=5314FFDF.20108@gmail.com \
    --to=alghe.global@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).