From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] (fwd) Installation problem
Date: Mon, 1 Sep 1997 12:25:31 -0400 [thread overview]
Message-ID: <19970901162531.n6-ERO6XCKrSBFJZ-sh1s1XM4jzWNpD0tfERHPXYoDI@z> (raw)
there's a problem with eide drives > 2Gb due to a sign sign extension bug
in the driver (the 'start' argument of ataxfer() should be of type ulong, not long).
perhaps someone could make a new kernel for you or you could subsitute a smaller
drive to get up then you can make the change yourself.
next reply other threads:[~1997-09-01 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-01 16:25 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-04 14:35 David
1997-09-02 4:19 G.David
1997-09-01 15:14 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=19970901162531.n6-ERO6XCKrSBFJZ-sh1s1XM4jzWNpD0tfERHPXYoDI@z \
--to=jmk@plan9.bell-labs.com \
/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).