From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org
Subject: Re: PSA: Please update your flash plugin!
Date: Sun, 1 Aug 2010 15:17:21 +0100 [thread overview]
Message-ID: <20100801141721.GA11854@gallifrey> (raw)
In-Reply-To: <4C558237.1040705@panasas.com>
* Boaz Harrosh (bharrosh@panasas.com) wrote:
> On 07/30/2010 07:05 AM, Justin P. Mattock wrote:
> > On 07/29/2010 07:50 PM, Theodore Ts'o wrote:
<snip - warning>
> > biggest problem here is they havn't updated their x86_64(pure64) version
> > yet. hopefully hey release an update soon.
> >
> > Justin P. Mattock
> > --
>
> Here too. How do I run (any) Flash-10.1 on a 64bit system (say FC12) without
> actually reverting to a 32bit browser? Do I still get to install half of my
> system as 32bit duplicates?
nspluginwrapper works well enough for me on Ubuntu, but this
isn't a kernel problem. (It seems to work better for me in Chrome
than ff but hey that's another problem again).
Since there isn't an announced date for if a 64bit version is going
to be available (only a fluffy statement that they intend to do one)
it's a case of having to move back to 32.
See: http://www.theregister.co.uk/2010/06/11/64_bit_flash_for_linux_dead/
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2010-08-01 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 2:50 PSA: Please update your flash plugin! Theodore Ts'o
2010-07-30 4:05 ` Justin P. Mattock
2010-08-01 14:18 ` Boaz Harrosh
2010-08-01 14:17 ` Dr. David Alan Gilbert [this message]
2010-08-01 17:53 ` Justin P. Mattock
2010-09-16 14:19 ` Justin Mattock
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=20100801141721.GA11854@gallifrey \
--to=linux@treblig.org \
--cc=bharrosh@panasas.com \
--cc=justinmattock@gmail.com \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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 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.