Re: ia32 chroot caveat(s)
This confirms that I was right in reserving the 64bit machine for 64bit
applications and the 32bit machine for 32bit applications. It is easy to
communicate between the two.
Because the calculations at 64bit are long lasting, I use a usb card reader to
exchange files, but nothing prevents intercommunication between the two
machines.
My only worry (or curiosity) in these affairs is the role of the lib32
provided on base installation of amd64 etch. There must be something using
them (i have not investigated) maybe the video, as jame suspected? If used,
this does not appear to be a pure 64bit system. Can lib32 be apt-get remove
without preventing functions? I am not going to investigate.
cheers
francesco pietra
On Friday 16 June 2006 01:09, edwardsa wrote:
> While the chroot has relieved several problems with amd64, two issues
> should be raised:
>
> 1. Using the 32-bit firefox is problematic because it will not serve as
> a useful directory viewer unless one does some significant binding. a
> chrooted application only views the files within the chroot. So, for
> example the directory /usr/share/doc will show the limited documentation
> within the chroot.
>
> 2. I have had very limited success loading a full and satisfying set of
> fonts in the chroot. I have another post on this difficulty but, to
> recapitulate, when I try to install, for example, xfonts-75dpi on the
> chroot, I get the following response:
>
> chalcogenide:/# apt-get install xfonts-75dpi
> Reading package lists... Done
> Building dependency tree... Done
> Suggested packages:
> xfs xserver
> The following NEW packages will be installed:
> xfonts-75dpi
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B/3470kB of archives.
> After unpacking 4645kB of additional disk space will be used.
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = "en_US:en_GB:en",
> LC_ALL = (unset),
> LANG = "en_US"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> Selecting previously deselected package xfonts-75dpi.
> (Reading database ... 26278 files and directories currently installed.)
> Unpacking xfonts-75dpi (from .../xfonts-75dpi_1%3a1.0.0-2_all.deb) ...
> Setting up xfonts-75dpi (1.0.0-2) ...
> warning: /usr/lib/X11/fonts/75dpi does not exist or is not a directory
> warning: /etc/X11/fonts/75dpi does not exist or is not a directory
> warning: /usr/lib/X11/fonts/75dpi does not exist or is not a directory
>
> There is a cryptic statement in the document
>
> https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html
>
> under The quick way about simply installing the ia32-libs package in the
> 64bit space, but no guidance about how to install or run once this has
> been accomplished. It would be useful if this were fleshed out so that
> users could compare the two strategies themselves.
>
> Art Edwards
>
> --
> Arthur H. Edwards
> Senior Research Physicist
> Air Force Research Laboratory
> AFRL/VSSE
> Bldg. 914
> 3550 Aberdeen Ave. SE
> KAFB, NM 87117-5776
>
> (505) 853-6042 (O)
> (505) 463-6722 (C)
> (505) 846-2290 (F)
Reply to: