Robert Himmelmann wrote:
Volker Kuhlmann wrote:
latest libraries. A few "mount --bind"s might do that. I cannot use
sym- or hardlinks for this as they won't work after chrooting.
Hardlinks will work after chrooting, symlinks will obviously not.
In my case hardlinks don't work because each distribu
Volker Kuhlmann wrote:
latest libraries. A few "mount --bind"s might do that. I cannot use sym-
or hardlinks for this as they won't work after chrooting.
Hardlinks will work after chrooting, symlinks will obviously not.
In my case hardlinks don't work because each distribution is on its own
> latest libraries. A few "mount --bind"s might do that. I cannot use sym-
> or hardlinks for this as they won't work after chrooting.
Hardlinks will work after chrooting, symlinks will obviously not.
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http
Nick Rout wrote:
Why are people hacking at all? There is a hole that nobody has filled
yet. Untill now you only run one distribution at the same without using
using vmware and the like.
don't think you have invented something Robert :-) chroot has been round
for ages.
Yes, but I needed
On Fri, 2005-05-06 at 21:18 +1200, Robert Himmelmann wrote:
> Nick Rout wrote:
>
> >On Fri, 2005-05-06 at 16:50 +1200, Robert Himmelmann wrote:
> >
> >
> >>run
> >>three distributions with one X and one kernel at the same time using
> >>chroot and mount --bind. I want to be able to use Yast, e
Nick Rout wrote:
On Fri, 2005-05-06 at 16:50 +1200, Robert Himmelmann wrote:
run
three distributions with one X and one kernel at the same time using
chroot and mount --bind. I want to be able to use Yast, emerge and
apt-get on the same machine without rebooting. I have already
installed
a p
On Fri, 2005-05-06 at 16:50 +1200, Robert Himmelmann wrote:
> run
> three distributions with one X and one kernel at the same time using
> chroot and mount --bind. I want to be able to use Yast, emerge and
> apt-get on the same machine without rebooting. I have already
> installed
> a program i
I forgot: One also has to execute "cp $XAUTHORITY /data/suse$XAUTHORITY".
Robert Himmelmann wrote:
Thanks or all the help. mount --bind /tmp /data/suse/tmp solves the
problem. There was some confusion about my motives in doing this. I am
not trying to access X on a server machine from a client ma
Thanks or all the help. mount --bind /tmp /data/suse/tmp solves the
problem. There was some confusion about my motives in doing this. I am
not trying to access X on a server machine from a client machine but run
three distributions with one X and one kernel at the same time using
chroot and mou
Hi,
emacs -nw
will open up emacs in the console you are using
>From man emacs,
-nw Tells Emacs not to use its special interface to X. If you use
this switch when invoking Emacs from an xterm(1) window, dis-
play is done in that window. This must be the first op
This is NOT remote X11, it is X11 from within a chroot on the same
machine!
On Fri, 06 May 2005 09:35:32 +1200
Michael JasonSmith wrote:
> :)
>
> With my experience with Fedora which I suspect is very similar in its
> X11 setup to SuSE I can say that everyone is right. You have to do
> damn
> 2. Run "xhost +ClientMachine" as a user running an X11 server, to
> allow connections from "ClientMachine".
I would strongly suggest you forget that xhost ever existed. It allows
any user(!) from that machine to connect to your server. Instead, use
the X11 xauth mechanism. It works
On Fri, 2005-05-06 at 07:45 +1200, Robert Himmelmann wrote:
> Now I tried emacs -d 127.0.0.1:0 on Gentoo and it gives about the same
> message as in SuSE. I think I have to enable TCP/IP support in the
> server somewhere. How can I do that?
:)
With my experience with Fedora â which I suspect i
try setting the DISPLAY variable:
DISPLAY=:0 emacs
On Fri, 06 May 2005 07:45:20 +1200
Robert Himmelmann wrote:
> Now I tried emacs -d 127.0.0.1:0 on Gentoo and it gives about the same
With strace xhost I found out that xhost accesses some files in /tmp.
After "mount --bind /tmp /data/suse/tmp" it worked and now I can
natively run SuSE and Gentoo-applications at the same time.
The whole sequence is now:
mount --bind /dev /data/suse/dev/
mount --bind /tmp /data/suse/tmp
mount -
Robert Himmelmann wrote:
Now I tried emacs -d 127.0.0.1:0 on Gentoo and it gives about the same
message as in SuSE. I think I have to enable TCP/IP support in the
server somewhere. How can I do that?
Can you see the "-nolisten TCP" flag in the process listing.
man Xserver will tell you all about
Now I tried emacs -d 127.0.0.1:0 on Gentoo and it gives about the same
message as in SuSE. I think I have to enable TCP/IP support in the
server somewhere. How can I do that?
Hello,
I am running Gentoo/SuSE (soon Gentoo/Debian). After "mount --bind /dev
/data/suse/dev/", "mount -t proc none /da
> xhost (on Gentoo) gives
>
> access control enabled, only authorized clients can connect
>
> I suppose I have to allow anybody to connect to make this work. How do I
> do this?
Try saying
xhost localhost
to give all users on the local machine access to the X server.
Alternatively replace loca
Hello,
I am running Gentoo/SuSE (soon Gentoo/Debian). After "mount --bind /dev
/data/suse/dev/", "mount -t proc none /data/suse/proc" and "chroot
/data/suse /bin/bash" I am in SuSE. Now when I try to run emacs it
prints out
emacs: Cannot connect to X server :0.
Check the DISPLAY environment variabl
19 matches
Mail list logo
