From: David Riley <happyoscar42@usa.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.3.whatever and hfs
Date: Mon, 20 Sep 1999 21:54:11 -0400 [thread overview]
Message-ID: <37E6E543.EB733942@usa.net> (raw)
The current vger 2.3 kernel (whatever it is, maybe 2.3.18) compiles
without a hitch, except at the end when it's linking it all up and it
dies with an unresolved symbol "update_vm_chache" in hfs.o. I'd like to
be able to use hfs with my 2.3 kernel; is there a fix for this?
Also, I noticed that the duplicate Mach64 entry in the console drivers
config bit has been removed. Thanks so much to whomever did that!
--
--"Your mouse has been moved. Windows 95 must be restarted for change
to take effect."
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-21 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-21 1:54 David Riley [this message]
1999-09-21 3:23 ` 2.3.whatever and hfs David D. Kilzer
1999-09-21 6:05 ` Sriranga Veeraraghavan
1999-09-21 6:17 ` Martin Costabel
1999-09-22 12:28 ` Brad Boyer
-- strict thread matches above, loose matches on Subject: below --
1999-10-15 6:55 Lou Langholtz
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=37E6E543.EB733942@usa.net \
--to=happyoscar42@usa.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).