From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Re: etherelnk3.c
Date: Mon, 15 Dec 1997 12:14:33 -0600 [thread overview]
Message-ID: <19971215181433.0MBPfMUie8Fn08rJsy-GAKw75EP_JJYvP7bC6PwmlYs@z> (raw)
>From: eld@jewel.ucsd.edu (Eric Dorman)
>> From: "G. David Butler" <gdb@dbSystems.com>
>> To: 9fans@cse.psu.edu
>> Subject: [9fans] Re: etherelnk3.c
>>
> Another thing to consider is how these changes would affect
>the integration of ether drivers between the fs and terminal code.
>Integrating these two trees first allieviates a whole mess of
>existing problems and ensures that this type of effort won't
>have to be done again (perhaps differently, even) for fs.
In fact the problem becomes worse since Blocks don't exist
in the fs. There we would have to use Msgbufs.
next reply other threads:[~1997-12-15 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-15 18:14 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-01-02 21:54 jim
1997-12-31 17:14 Eric
1997-12-31 15:10 jim
1997-12-31 8:54 Nigel
1997-12-31 6:49 G.David
1997-12-31 5:16 jim
1997-12-31 3:51 G.David
1997-12-31 2:41 jim
1997-12-30 19:05 Eric
1997-12-30 1:20 G.David
1997-12-29 20:25 Eric
1997-12-24 4:30 jim
1997-12-15 17:43 Eric
1997-12-14 16:37 G.David
1997-12-13 18:04 G.David
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=19971215181433.0MBPfMUie8Fn08rJsy-GAKw75EP_JJYvP7bC6PwmlYs@z \
--to=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).