Newsgroups: gmane.linux.debian.ports.amd64 Date: Tue, 22 Feb 2005 10:25:42 +0100
Ted:
> I'm assuming you are using dchroot to run openoffice in the chroot?
Yes, that's exactly my setup, as described in the howto. But. I did not use the apostrophes. With the filename between apostrophes it does indeed work.
Clive:
> expert and can't guess what the problem may be. Did you install amd64 > and then install the 32bit system in the chroot (as I did) or the other
I have a 64bit system, and a 32bit chroot inside of it. The only tricky business is that this weekend I reinstalled my 64 bit system, but without reinstalling the chroot. The chroot was in my /home which is on its own partition.
So in conclusion, is there any way to tell KDE to put apostrophes around filenames when it calls various programs?
Alex.
> So in conclusion, is there any way to tell KDE to put apostrophes > around filenames when it calls various programs?
Yes, but a better thing is to fix dchroot's / su's stupidity with a script (make this do_chroot):
#!/bin/bash
# Work around dchroot brain-deadness
ARGS=""
for i in "$@" ; do
ARGS="$ARGS '$i'"
done
exec dchroot -c ia32 -d -q "`basename $0`" "$ARGS"Much eaiser.
Adam
>Yes, but a better thing is to fix dchroot's / su's stupidity with a >script (make this do_chroot): > >I don't understand. What should I do with this script?
From the FAQ:
You can make things slightly simpler even than this. Write a small shell script like the following, and place it in your PATH: eg. /usr/local/bin/do_dchroot
Make it executable:
chmod 755 /usr/local/bin/do_dchroot
Now create a symlink to this script from each command you want to run inside the chroot to this shell script:
cd /usr/local/bin ln -s do_dchroot openoffice ln -s do_dchroot oowriter ln -s do_dchroot oocalc
Now you can execute openoffice by simply typing openoffice or oowriter.
Peter