On 11/05/13 18:20, michael norman wrote:
On 11/05/13 08:52, Basil Chupin wrote:
On 11/05/13 17:26, michael norman wrote:
On 11/05/13 07:43, Basil Chupin wrote:
On 11/05/13 00:36, Erwin Lam wrote:
On Friday 10 May 2013 22:13:36 Basil Chupin wrote:
In one of the directories I accidentally deleted a symlink which was pointing to a file within the same directory.
The only trouble is that this symlink was of this format: "@libaacs.so" which pointed to another libaacs.so.xx file immediately following the link.
What I don't know is how to create this "@" symlink :-( . I know about the "~" symlink which is very easily created using mc, but how does one create the "@" link <sob> ? :'(
Someone please educate me? :-) I think running ldconfig as root may solve your issue.
Jesus, in a moment of pure mental instability and contrary to my normal behaviour I ran this command 'ldconfig' and it did something - but I haven't a clue what it is supposed to do! And therefore don't know what it did! :-(
Tell me that it hasn't reconfigured some vital parts of my perfectly functioning 12.3 system which will come and bite me in the bum at any time. Please.
BC
man ldconfig tells you what its purpose is, looks to me that as Erwin said it might/should have fixed your problem.
Mike
Thanks. I didn't know there was a 'man' entry for ldconf :-) . I looked in YaST but couldn't see anything there which is what gave me heart palpitations :-) .
I still don't know if it worked but at least I now feel easier that it didn't do damage to my system (I theeeenk.....:-) .)
I only looked up the man page out of curiosity, just ran man ldconfig in a terminal.
Being wise after the event I think if you had run ldconfig in verbose mode it would have told you what it was doing.
Others more versed in these things than me will no doubt be able to tell you what system logs to look at to tell you what it did. I suppose if in the meantime your system falls over you'll know the worst has happened,
Well, so far so good and all is still working :-) . To be quite specific, the reason I messed up the symlink I mentioned was because I could not play BluRay DVDs on the system and the link I mentioned, libaacs.so, was involved. Not knowing what I was doing (and I still don't know) I zapped that link by replacing it with a file (of the same name) I found in a blog on the 'net suggesting how to be able to play BR DVDs on Linux. When I tried to play BR discs I would get error messages from vlc 'telling' me that some codec was not available to play them - hence my experimentation with that symlink et al. Now that I *can* play BR discs - and *after* doing the ldconf command I find that I get a couple of error messages from vlc but which do not prevent me from watching the DVDs. Meaning that I don't know if the ldconf restored the symlink or not, or there is still another "missing link" which continues to produce the 2 (ignorable) error messages in vlc. But now that I feel more confident about what ldconf does I will use it with the '-v' parameter to see what it does :-) . Most grateful for your help. BC -- Using openSUSE 12.3 x86_64 KDE 4.10.3 & kernel 3.9.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org