From: mike <mike@kevino.org>
To: linux-newbie@vger.kernel.org
Subject: Re: Java and Mozilla problem
Date: Thu, 12 Feb 2004 20:07:46 -0700 [thread overview]
Message-ID: <402C3F82.7020603@kevino.org> (raw)
In-Reply-To: <402B16D6.7030707@vcss.k12.ca.us>
Dave & Kim Howe wrote:
> Thanks for the reply Mike. I checked an I have a link from the
> libjavaplugin_oji.so file to the mozilla/plugins directory. I
> changed the permissions from root to Dave (user) and from root to
> users (group). I have RWX permissions. I made these permission
> changes to the link, the source file and the source file's directory.
> Still no go. Any other tips or suggestions?
>
> Dave
I dont believe there is a need to change permissions. One other thing
you may
check is later mozillas are built with gcc3.x, you can type
about:buildconfig into
the addressbar and see what it says.
If gcc3.x, then link should have been made to-->
/ns610-gcc32/libjavaplugin_oji.so
not--> /ns610/libjavaplugin_oji.so
Heres a link to a mozilla java faq
http://plugindoc.mozdev.org/faqs/java.html#Linux
it will explain it better.
Other than that, I don't think I can help much more. I've been lucky on
the plugins
for mozilla, I guess. (knock on wood) ;-)
Perhaps if someone on this list does not reply, you could try a Suse
list or Mozilla list.
And of course www.google.com is a great search tool.
Good luck
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next parent reply other threads:[~2004-02-13 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <402B16D6.7030707@vcss.k12.ca.us>
2004-02-13 3:07 ` mike [this message]
2004-02-12 2:50 Java and Mozilla problem Dave
2004-02-12 3:42 ` mike
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=402C3F82.7020603@kevino.org \
--to=mike@kevino.org \
--cc=linux-newbie@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.