Thank you Joseph, that is exactly what I wanted to know. If I had been clearer asking the question I might have gotten this kind of answer the first day. My bad! On Wed, Jul 24, 2013 at 10:03 PM, Joseph Sinclair wrote: > Assuming that you don't already have a /usr/lib64, and you're running a > 64-bit arch or don't mind letting 64-bit code think you are, it shouldn't > be an issue. > > What you're doing is creating a link for code that looks specifically for > 64-bit libraries to point them at the default library directory. Some code > that *really* wants to only run 64-bit may be confused and crash, but the > main system, kernel, and core libraries shouldn't have any issues. > > Most likely (this is speculation, though, having not investigated this > particular issue) there's a bug in the Unity system where it's assuming > that only 64-bit architectures exist (bad Ubuntu, bad bad Ubuntu), and has > linked specifically to the lib64 libraries, even when compiled for i686. > > Note, if it somehow causes a problem, merely removing the link would "fix" > the problem; something easily done from the recovery console of Grub2. > > All-in-all this seems pretty safe. > > Hopefully that helps to clarify the effects of creating that particular > link. > > On 07/24/2013 08:52 PM, Dazed_75 wrote: > > I already did the research. I was more referring to the fact that I have > > no clue as to the impact of making that link. Sorry, I should heve been > > clearer in my question. > > > > > > On Wed, Jul 24, 2013 at 6:28 PM, wrote: > > > >> That instruction is creating a soft link that by all accounts should be > >> already there. > >> It is harmless as it is. but you should: > >> man ln > >> and investigate the options for you own sanity. > >> Free advice, can't sue me... :) > >> ET > >> > >> > >> Dazed_75 writes: > >> > >>> I am having some troubles with Ubuntu 12.04.2. After some upgrade > (maybe > >>> to catalyst13), unity no longer runs. I have tried many fixes with no > >>> luck. I actually ran Cinnamon for several weeks, then discovered that > >>> Unity 2D works but has unfortunate appearance issues. The I found: > >>> http://xpressrazor.wordpress.**com/2013/07/22/install-** > >>> catalyst-driver-in-ubuntu-12-**04-2/< > http://xpressrazor.wordpress.com/2013/07/22/install-catalyst-driver-in-ubuntu-12-04-2/ > > > >>> but there is a step that makes me worry: > >>> cd /usr ; sudo ln -svT lib /usr/lib64 > >>> Should I be concerned about that? > >>> -- > >>> Dazed_75 a.k.a. Larry > >>> Please protect my address like I protect yours. When sending messages > to > >>> multiple recipients, use the BCC: (Blind carbon copy). Remove addresses > >>> from a forwarded message body before clicking Send. > >>> > >> ------------------------------**--------------------- > >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.**org< > PLUG-discuss@lists.phxlinux.org> > >> To subscribe, unsubscribe, or to change your mail settings: > >> http://lists.phxlinux.org/**mailman/listinfo/plug-discuss< > http://lists.phxlinux.org/mailman/listinfo/plug-discuss> > >> > > > > > > > > > > > > --------------------------------------------------- > > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > > To subscribe, unsubscribe, or to change your mail settings: > > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > > > > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- Dazed_75 a.k.a. Larry Please protect my address like I protect yours. When sending messages to multiple recipients, use the BCC: (Blind carbon copy). Remove addresses from a forwarded message body before clicking Send.