[opensuse] About this I know nothing.....
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? :-) 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
On Friday 10 May 2013, 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> ? :'(
Doesn't it work as usual? ln -s -- "libaacs.so.xx" "@libaacs.so" cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/05/13 23:08, Ruediger Meier wrote:
On Friday 10 May 2013, 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> ? :'( Doesn't it work as usual? ln -s -- "libaacs.so.xx" "@libaacs.so"
Thanks for this. It works (at least it looks good :-) ) but the above should read: ln -s "libaacs.so.xx" "libaacs.so" ie, without the '@' because having that '@' then creates 2 '@'; leaving it out creates the single one. Thanks again. 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
Hi, On Fri, May 10, 2013 at 10:13:36PM +1000, 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? :-)
Where did you see the @? With ls or mc? I think it is just a certain way to display a file type. -- Bye, Stephan Barth SUSE MaintenanceSecurity - SUSE LINUX GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2013-05-10 at 15:12 +0200, Stephan Barth wrote:
Where did you see the @? With ls or mc? I think it is just a certain way to display a file type.
Yes, mc uses such symbols, they are not part of the names. An absolute link: ~compilaciones -> /home1/cer/Compilaciones a broken link: !.Xresources -> .Xdefaults I have not seen one with '@' right now, so I can't guess what it means. Perhaps a relative link. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGNRokACgkQtTMYHG2NR9W4/gCfSYO4+B0crtPvpQ+Whg5CbG0j cm8Ani4GDWOGgB4YWM1FwWYqba7HoDjx =Tq3n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/05/13 05:12, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday, 2013-05-10 at 15:12 +0200, Stephan Barth wrote:
Where did you see the @? With ls or mc? I think it is just a certain way to display a file type.
Yes, mc uses such symbols, they are not part of the names.
An absolute link:
~compilaciones -> /home1/cer/Compilaciones
a broken link:
!.Xresources -> .Xdefaults
I have not seen one with '@' right now, so I can't guess what it means. Perhaps a relative link.
Look in /usr/lib64 which is where I messed up that link I mention in my OP. 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-05-11 at 16:34 +1000, Basil Chupin wrote:
On 11/05/13 05:12, Carlos E. R. wrote:
I have not seen one with '@' right now, so I can't guess what it means. Perhaps a relative link.
Look in /usr/lib64 which is where I messed up that link I mention in my OP.
Ah, ok. Yes, I see several: @libBrokenLocale.so -> /lib64/libBrokenLocale.so.1 which in turn is another symlink: /lib64/libBrokenLocale.so.1 -> libBrokenLocale-2.14.1.so It could mean a link to alink. Huh, no, in /lib I see @libBrokenLocale.so.1 -> libBrokenLocale-2.14.1.so I don't know what it means. I think it is is customized as a "skin". The mc help says: extensions_case (make sense only with 'extensions' parameter) make 'extensions' rule case sentitive (true) or not (false). │`type' key may have values │- FILE (all files │ - FILE_EX │- DIR (all directories │ - LINK_DI │- LINK (all links except stale link │ - HARDLIN │ - SYMLIN │- STALE_LIN │- DEVICE (all device files │ - DEVICE_BLOC │ - DEVICE_CHA │- SPECIAL (all special files │ - SPECIAL_SOCKE │ - SPECIAL_FIF │ - SPECIAL_DOO Probably each of those has a symbol assigned. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGOf48ACgkQtTMYHG2NR9U9UACfVRO2uEPpoZXGcWkMZGI+OoQh y3IAmQGLrD+jKEnJ9OXZOMxLrAnET3La =CFBD -----END PGP SIGNATURE-----
On 10/05/13 23:12, Stephan Barth wrote:
Hi,
On Fri, May 10, 2013 at 10:13:36PM +1000, 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? :-) Where did you see the @? With ls or mc? I think it is just a certain way to display a file type.
Yep, I use mc (almost) exclusively as my file manager [it's the Swiss knife of file managers] and look below what it shows. 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
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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 -- 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
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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.....:-) .) 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
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, Mike
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
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-05-11 at 16:43 +1000, Basil Chupin wrote:
On 11/05/13 00:36, Erwin Lam wrote:
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! :-(
That program is safe. It is run automatically each time you add a library to your system, so that the system knows where to find libraries when you start a program. I read in the manual that it updates libraries symlinks, so that's why it may be appropriate for your case. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGOgJAACgkQtTMYHG2NR9XthwCdEdAuoMbtWam9gcSv5SKA6yFE 01oAni2PxlZiv8FaJnaceipuNT3tCraH =IzLG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/05/13 03:32, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2013-05-11 at 16:43 +1000, Basil Chupin wrote:
On 11/05/13 00:36, Erwin Lam wrote:
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! :-(
That program is safe. It is run automatically each time you add a library to your system, so that the system knows where to find libraries when you start a program.
I read in the manual that it updates libraries symlinks, so that's why it may be appropriate for your case.
Thanks, Carlos, for the additional reassurances :-) . But the statement, "That program is safe.", is something which always strikes fear in me. It's like when my wife says to me, "Ummm, this tastes good!" when she is cooking a new recipe! :-D Now that I know what this ldconf does, I'll run it with the "-v" parameter and see what it is doing. 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-05-12 at 16:36 +1000, Basil Chupin wrote:
On 12/05/13 03:32, Carlos E. R. wrote:
Thanks, Carlos, for the additional reassurances :-) .
But the statement, "That program is safe.", is something which always strikes fear in me. It's like when my wife says to me, "Ummm, this tastes good!" when she is cooking a new recipe! :-D
ROTFL! :-) Yeah, there is nothing absolutely safe and sure in computing. There is always a grain of doubt and danger lurking somewhere :-) Like, for example, something having changed the configuration files that ldconfig uses and then it messes the system royally :-p
Now that I know what this ldconf does, I'll run it with the "-v" parameter and see what it is doing.
I have used it many times. It is typical when one is building locally a project that has libraries and applications, that the aplication step fails, says the libraries are not there. What? If I compiled them a minute ago, what is this? Then one remembers, runs "ldconfig" and tries again: success. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGPoukACgkQtTMYHG2NR9UhOwCghDwa2ahxCIqID58FYYebclOV u6UAnjqyUh7tqzyOQoDIkaOSkedkoVJW =JOpv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Basil Chupin -
Carlos E. R. -
Erwin Lam -
michael norman -
Ruediger Meier -
Stephan Barth