From: <plan9@itic.ca>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] ELNK3 and 3CSOHO100-TX
Date: Thu, 14 Mar 2002 09:41:24 -0600 [thread overview]
Message-ID: <FIEDLHOOAEHBJAPIKGJCKELFCAAA.plan9@itic.ca> (raw)
As we needed more Plan9 machines, we also modified
/sys/srv/boot/pc/9load and /sys/src/9/pc/etherelnk3.c
accordingly to Jim's advices and it works fine :
* Now the 9load `powered' floppy initialized the 3CSOHO100-TX and get a 9pccpudisk via BOOTP
* The 9pccpud also initialize and uses correctly the card
<plan9@itic.ca> a crit dans le message news:<FIEDLHOOAEHBJAPIKGJCCEKPCAAA.plan9@itic.ca>...
Many Thanks Jim,
It now works.
We have modified /sys/src/fs/plan9pc/etherelnk3.c
The 9pcfs serving through 3CSOHO100-TX worked fine while moving 876.15 MB in both directions (pccpud/kfs<->9fs)
----------
next reply other threads:[~2002-03-14 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 15:41 plan9 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-10 1:06 plan9
2002-03-07 4:50 jmk
2002-03-07 4:13 Plan9
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=FIEDLHOOAEHBJAPIKGJCKELFCAAA.plan9@itic.ca \
--to=plan9@itic.ca \
--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).