From: David Bulkow dbul@earthlink.net
Subject: [9fans] plan9 on vmware
Date: Sat, 25 Dec 1999 15:37:12 -0500 [thread overview]
Message-ID: <19991225203712.xTzgvNa1cKsfYe6DvEe8yF2BD9yY5ez1egOtdJIYrHA@z> (raw)
I don't believe this is a VMware bug. According to the draft ATAPI spec the proper
response to a feature request - when the feature is not available - it is put the
controller into an Abort error state. It is the driver's responsibility to dig its
way out of this condition.
I may dig into the code and make the error handling more robust, but I would rather
wait and see what sort of SCSI support VMware cooks up.
Has anybody made any headway on the ethernet support?
John Orthoefer wrote:
> Coolness dude!
>
> I tried it once it wouldn't boot. So I put it on the back burner. Did
> you report the problem to the VMWare people?
>
> johno
next reply other threads:[~1999-12-25 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-25 20:37 David [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-24 15:19 jmk
1999-12-23 23:54 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=19991225203712.xTzgvNa1cKsfYe6DvEe8yF2BD9yY5ez1egOtdJIYrHA@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).