| 1 |
> |
| 2 |
> I do find it surprising/curious/mystifying that I can run, for |
| 3 |
> instance, a 32-bit Firefox with 32-bit helper apps, all running from |
| 4 |
> the chrooted environment, but as far as I can tell, you are saying it |
| 5 |
> will be using a 64-bit version of X, along with 64-bit ATI drivers, |
| 6 |
> 64-bit Alsa and a 64-bit kernel, etc., to display the web pages and do |
| 7 |
> the audio. |
| 8 |
> |
| 9 |
> I'm sure I don't have this quite right in my mind yet. I presume that |
| 10 |
> to build FIrefox and mplayer in the chrooted environemnt I will end up |
| 11 |
> building a 32-bit version of X, etc., but I guess it's not used? |
| 12 |
> |
| 13 |
|
| 14 |
That is correct, your 32 bit chroot will need all 32 bit apps built for |
| 15 |
the required libraries. This means you will have another full compile of X |
| 16 |
and other dependencies (thats why you need lots of diskspace). |
| 17 |
|
| 18 |
When the actual 32 bit X app starts up, it will use sockets to talk |
| 19 |
directly to your 64 bit X server. |
| 20 |
|
| 21 |
This is the same as starting a X application on a remote system with X |
| 22 |
forwarding. The actual code is executed on the remote system (what ever |
| 23 |
the platform is) and the display is sent of the network and displayed on |
| 24 |
your local X server. |
| 25 |
|
| 26 |
|
| 27 |
Random Thought: |
| 28 |
--------------- |
| 29 |
Once is happenstance, |
| 30 |
Twice is coincidence, |
| 31 |
Three times is enemy action. |
| 32 |
-- Auric Goldfinger |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
Archives