From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ideas for a new install procedure
Date: Wed, 14 Nov 2001 21:33:01 +0000 [thread overview]
Message-ID: <20011114213222.E1198199ED@mail.cse.psu.edu> (raw)
actually, i'd say the real problem is writing all the required
drivers in the first place, not the dynamic loading of
the same. no, that's not right. the real problem is getting
the data required to be able to write the drivers.
so, who volunteers to write what?
perhaps a list of need-driver/will-attempt on the wiki?
next reply other threads:[~2001-11-14 21:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 21:33 forsyth [this message]
2001-11-14 22:33 ` Dan Cross
2001-11-14 23:03 ` Jason Gurtz
2001-11-14 23:59 ` Dan Cross
2001-11-15 17:24 ` Jason Gurtz
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 23:20 Russ Cox
2001-11-14 23:18 Russ Cox
2001-11-14 23:04 anothy
2001-11-14 22:35 Russ Cox
2001-11-14 23:57 ` Dan Cross
2001-11-14 21:34 forsyth
2001-11-14 20:03 Russ Cox
2001-11-14 21:22 ` Dan Cross
2001-11-14 14:31 Fco.J.Ballesteros
2001-11-14 10:44 geoff
2001-11-14 14:07 ` William Josephson
2001-11-15 10:41 ` Ralph Corderoy
2001-11-15 14:09 ` Sam Hopkins
2001-11-14 9:18 Fco.J.Ballesteros
2001-11-14 16:09 ` Jason Gurtz
2001-11-14 19:46 ` Dan Cross
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=20011114213222.E1198199ED@mail.cse.psu.edu \
--to=forsyth@vitanuova.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).