Could you help me what the easiest way is to convert these hashes on terminal with commands?

From this format:
oAZkAse75vY3DUyTwXhW*K$wqoWNvN,ae6a26879f684db2737173fecf6b9199ac5ed5ec0d1b66ac9474ec5fb794fc55
3ZIdz2V538b@L36c@Ces%MWKvkyXri,27aa7b56ecf8f93f72961bddc4a121ce4f251dc3a3ece660f351a88d777ec43d

to his format:
ae6a26879f684db2737173fecf6b9199ac5ed5ec0d1b66ac9474ec5fb794fc55AZkAse75vY3DUyTwXhW*K$wqoWNvN
27aa7b56ecf8f93f72961bddc4a121ce4f251dc3a3ece660f351a88d777ec43d:3ZIdz2V538b@L36c@Ces%MWKvkyXri

So the separator will be ":"

Thanks in advance.

not sure i am following but maybe man tr will help ?

1 members found this post helpful.

Thanks. I will try....

"tr" will translate or delete characters but not swap blocks of them. "perl" does that easily, but a step simpler is "awk"

Look up FS and OFS in the manual page for "awk" for details.

1 members found this post helpful.

Sorry, could somebody please explain to me how one can convert the output of one has routine to another? Or is this a mark-up problem?

@Turbocapitalist

Thank you for your help.
It works....

You're welcome. The important thing is that "awk" becomes more familiar. It will over time. What did you think of the "awk" manual page regarding FS and OFS? And about $1 and $2 and how they relate to FS and OFS?

1 members found this post helpful.

Thanks. I like awk. FS= file separator of input data, OFS= file separator of output data, changing FS to OFS. Is it correct?

I got another tip:
sed -n "s/\(.*\),\([a-f0-9]*\)/\2:\1/p" input.txt >> output.txt

What is the difference between awk and sed?
I know tr, uniq, sort, cat, tac and other easy commands. awk and sed more complex....But until this time I didn't need these commands. So which is the most familar? Which is easier to learn?

Not a case of easiest to learn but rather right tool for the job.

Here is sed manual / tutorial to help compare :- http://www.grymoire.com/Unix/Sed.html

2 members found this post helpful.

They each lend themselves to somewhat different tasks. It's useful to find what you find each is good for and then use them for that. There is often an optimal zone where a task will lend itself more to one than another. So it's more of the idea of the right tool for the job. As to what is more familiar, that depends on which one you use most. For me it is "perl". You should find all three on any system you encounter. They're all pretty easy to get the hang of, again the one you use most will become most familiar and thus easiest.

One thing to remember is maintainability and much of that depends on code that clear to understand. You can do weird or overly clever things in "sed" that might be easier for another person to follow if you use "awk". Same for "perl" over "awk". But anyone can write clear or unclear code in most any language, since a good portion of that choice is up to the coder. Make the computer do the work. That's what it's for.

1 members found this post helpful.