Jonas Karlsson wrote: > On Mon, 02 Apr 2007 13:32:15 +0200, Jonatan Liljedahl > <[EMAIL PROTECTED]> wrote: > >> Nick Matteo wrote: >>> On 3/31/07, teique <[EMAIL PROTECTED]> wrote: >>>> !! /lib/libGL.so.1 -> libGL.so.1.5.060500 *mmm*, the beggining >>>> of my Konsole history is lost by now :/ as I remember, I did $ >>>> link -sf libGL.so.1.0.9755 /lib/libGL.so.1 so it was towards >>>> nvidia, and then, by curiosity and to let ldconfig happen thru >>>> SymlinkProgram, I run $ SymlinkProgram nvidia and it symlinked >>>> back again to mesa one... $ /lib/libGL.so.1 -> >>>> libGL.so.1.5.060500 (offtopic: I wonder if there is a way to >>>> default Konsole to unlimited history on new sessions...) >>> There certainly is, just set the history to unlimited, then >>> choose "settings->save as default" >>> >>> SymlinkProgram nvidia shouldn't point anything towards mesa, >>> unless the libGL.so.1 in the nvidia directory is pointing at >>> libGL.so.1.5.060500? >> I think there's some problem with symlinkprogram... I have the same >> problem here, and though symlinking NVidia with -c overwrite says: >> >> >> SymlinkProgram: Conflict: /Programs/Mesa/6.5/lib/libGL.so.1.2 >> SymlinkProgram: Replaced with: >> /Programs/Nvidia/x86-1.0-9746-pkg1/lib/libGL.so.1.0.9746 >> >> I still have in /lib: >> >> libGL.so.1 -> libGL.so.1.2 libGL.so.1.2 -> >> /Programs/Mesa/6.5/lib/libGL.so.1.2 >> > This is the problem. The relative link "libGL.so.1 -> libGL.so.1.2" > shouldn't exist in /lib. Could you try to run DisableProgram on both > Mesa and Nvidia and make sure that you have no libGL.so links in > /lib? Then try to resymlink them again.
I'm not sure I want to try that, last two times I ran DisableProgram it rendered my machine unbootable! (had to boot the liveCD and chroot into my root and symlinkprogram the bootscripts and stuff...) >> While in /Programs/NVidia/Current/lib I have: >> >> libGL.so -> libGL.so.1 libGL.so.1 -> libGL.so.1.0.9746 >> libGL.so.1.0.9746 >> >> So, it seems SymlinkProgram doesn't handle symlinking symlinks >> correctly? >> > It doesn't handle relative symlinks in the /System/Links directory. I > have tried to reproduce this bug forcing conflicts in all ways I can > think of and having relative symlinks in the /System/Links directory > produced this exact problem. So you mean if /P/Foo/Current/lib has a -> b then /S/L/L/a should point to /P/Foo/Current/lib/b and not to b directly? But then how did that symlink got there? -- /Jonatan -=( http://kymatica.com )=- _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
