I was not asking for where you got the information, just pointing out there were at least two threads that already gave it. The important part is that we have a sticky now though, the rest does not matter.
I used the picket fence style in sed because that was what the original command used:
Code:
sudo ln -s /usr/lib32 /usr/l32
sudo sed -i -e 's:usr/lib/:usr/l32/:g' /usr/lib32/gtk-2.0/2.10.0/loader-files.d/libgtk2.0-0.loaders
sudo sed -i -e 's:usr/lib/:usr/l32/:g' /usr/lib32/libgdk_pixbuf-2.0.so.0.1200.9
Will do the same thing. If you do a search for "l3232" on the virtualization forum you will see a number of hits where the original command was used on a loader already pointing to lib32. It is more important that the command not be used unless needed than the particulars of the syntax. I am just trying to mitigate the risk with a command that should not actively break the loader should it be run when not needed.
Bookmarks