Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Billy Holmes <billy@...>
Subject: Re: Now I have a problem with l32 too
Date: Wed, 21 Dec 2005 09:10:32 -0500
Peter Humphrey wrote:
> prh@gentoo32 ~ $ xterm
> prh@wstn ~ $ xhost local:localhost
> prh@wstn ~ $ l32 bash
> prh@gentoo32 ~ $ sh /usr/local/src/install-crossover-standard-5.0.0.sh
> prh@wstn ~ $ xhost local:localhost
> prh@wstn ~ $ l32 bash
> prh@gentoo32 ~ $ sh /usr/local/src/install-crossover-standard-5.0.0.sh 

first, I'm not sure what your prompt means ($PS1). did you create a 
different prompt for your 32-bit? Is that in the 32-bit handbook?

> prh@wstn ~ $ xhost local:localhost && l32 
> /usr/local/src/install-crossover-standard-5.0.0.sh
> non-network local connections being added to access control list
> /bin/bash: /usr/local/src/install-crossover-standard-5.0.0.sh: 
> Permission denied

second, I think your install-crossover-standard-5.0.0.sh doesn't have 
the execute bit set (-rw-r--r-- when you do a ls -l). you should be able 
to still run it as "l32 sh install-crossover-..." (notice the "sh" at 
the beginning). To make it an executable script, you can do "chmod +x 
install-cross-...". However, that's not required.

third, I'm concerned how your environment variables are dissappearing 
when you switch to the new environment. l32 doesn't touch your 
environment, and it should (theoretically) inherit the same environment 
as the parent that ran it.

As a side note, you can force the DISPLAY variable to be set like so:

$ export DISPLAY=:0
$ xterm

I'd try the xterm test using the old method:

[with sudo installed]
$ sudo linux32 chroot /mnt/gentoo32 su - $USER -c xterm

[without sudo install]
$ su -c "linux32 chroot /mnt/gentoo32 su - $USER -c xterm"

I'm thinking that there must be a difference between your /etc/profile, 
/etc/bash/bashrc, ~/.profile, and ~/.bashrc and mine and Mark's.

Is anyone else having issues with the DISPLAY variable not carrying over 
from the 64-bit to the 32-bit environment?
-- 
gentoo-amd64@g.o mailing list


References:
Now I have a problem with l32 too
-- Peter Humphrey
Re: Now I have a problem with l32 too
-- Billy Holmes
Re: Now I have a problem with l32 too
-- Mark Knecht
Re: Now I have a problem with l32 too
-- Peter Humphrey
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Now I have a problem with l32 too
Next by thread:
kdesu
Previous by date:
Re: Problems getting started
Next by date:
Re: firewall


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.