Carlos E. R. wrote on 2014-10-04 13:46 (UTC+0200):
Felix Miata wrote:
Carlos E. R. wrote on 2014-10-03 23:41 (UTC+0200):
cer@Telcontar:~/tmp/date> l /home/cer-g/.xinitrc.template -rwxr-xr-x 1 cer-g users 1112 May 14 04:12 /home/cer-g/.xinitrc.template* cer@Telcontar:~/tmp/date> cp /home/cer-g/.xinitrc.template . cer@Telcontar:~/tmp/date> l .xinitrc.template -rwxr-xr-x 1 cer users 1112 Oct 3 23:39 .xinitrc.template* cer@Telcontar:~/tmp/date>
It's not clear to me what the above is supposed to demonstrate. Why would any file be given a name that includes a wildcard character (.xinitrc.template*), if even legal?
Wow.
Please, take another cup of coffee, relax, and look again :-)
I go days between cups of coffee, typically 7, sometimes many more. Caffeine is a drug my body is better off without. I looked repeatedly.
That asterisk is displayed by "ls" and means the file is executable. It is not part of the name.
What "ls"? $ l If 'l' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf l $ Thus, I don't know what command you issued. OTOH, ls -l here produces no trailing asterisks, regardless of permissions. And: $ alias alias ll='ls -l ' alias lr='ls -lrt ' $
What you were supposed to look at were the dates of the origin of the copy and the destination.
Obviously, but the context registering in my brain was incomplete for failure to understand the presence of the trailing asterisk. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org