9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Michael Andronov" <michael_andronov@sd-kyber.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 wireless how-to...
Date: Mon,  4 Feb 2008 23:23:18 -0500	[thread overview]
Message-ID: <46721ee70802042023v42febbfdxf1b9e2af4807cf1@mail.gmail.com> (raw)
In-Reply-To: <9EF96B73-BCE6-482E-9768-695368E9FC61@mac.com>

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

First, thanks a lot for the advices and help;

However, the theory to practice step seems  to be a bit longer :)

1. about network:
   - following your advice, found plan9.ini
   - i managed to modify it with sam, ( for some strange reason, when I'm
editing the file in ACME, the 'Put' option appears as soon as I modify the
file - and that is expected; but after I select 'Put' and press button2-
nothing happens.... Actually seems like commands within ACME toolsbar do not
want to react to button2 (?) ).
   - no matter what I put inside,  while booting Plan9 I can see the card
was detected, elkn3 was used, and media was set to 10Base... (And the card
is working fine after...) But the card is 100Base, and my intention was to
set it to be 100BaseTX...
   The line I added at the end of the plan9.ini reads:
   ether0=type=elnk3 media=100BaseTX  force100 fullduplex

So, that configuration step is still won by Plan9 :)

2.  I followed your advice on USB...
( By the way, the card I am trying to use - "Belkin Components/eTek Labs,
Model #F54220" ).

I put the lines you told me just above switch($services){...
The idea was to see the mouse connected to USB operational...

But I do not even see detection of USB card during start up...

So, that configuration step is also won by Plan9 :)

So, the current score is 2:0... But I still have a hope to win it one day.

Thanks for your attention to this matter.

Michael.


On Feb 4, 2008 8:46 PM, Pietro Gagliardi <pietro10@mac.com> wrote:

> On Feb 4, 2008, at 8:44 PM, Pietro Gagliardi wrote:
>
> For USB, add this to the TOP of /usr/$user/lib/profile, above the switch
> but below the other bind lines:
>
> bind -a '#U' /dev
> usbd
>
>
> Scratch that. There is a line in /usr/$user/lib/profile that reads
>
> switch($terminal){
>
> Above that, add
>
> bind -a '#U' /dev
> usbstart
>
> usbstart sets up everything, including USB-based audio and the mouse.
>
>

[-- Attachment #2: Type: text/html, Size: 3146 bytes --]

  reply	other threads:[~2008-02-05  4:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  0:12 Michael Andronov
2008-02-05  0:14 ` Pietro Gagliardi
2008-02-05  1:23   ` Michael Andronov
2008-02-05  1:44     ` Pietro Gagliardi
2008-02-05  1:46       ` Pietro Gagliardi
2008-02-05  4:23         ` Michael Andronov [this message]
2008-02-05  6:47           ` Eris Discordia
2008-02-05 12:39             ` erik quanstrom
2008-02-05 16:58             ` Michael Andronov
2008-02-05 17:35               ` Uriel
2008-02-05  1:48     ` Christopher Nielsen

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=46721ee70802042023v42febbfdxf1b9e2af4807cf1@mail.gmail.com \
    --to=michael_andronov@sd-kyber.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).