All, An issue recently came up on StackOverflow.com regarding shell scripts related to the use of 'ls -opts' to populate a loop structure in a shell script. Suffice it to say *in sum*, it is good practice to avoid this use of ls and to search for an alternative solution to fit your needs. That being so, there are some cases where the loop needs data in a sort order fashion, easily provided by ls, but requiring tortured, piped multiple external calls otherwise. The tweenies (those that 'know not' and 'know not' that they 'know not') took the position that simply mentioning ls as a method to feed a loop automatically condemned you to roast in hell for eternity. (despite TLDP BASH HowTo being riddled with examples) Those that 'know', said wait a minute, it is a portability issue, and the problems protected against are just those instances where non-printing control characters are embedded in the filename, such as a newline, carriage-return or null-terminating character inside the filename itself. Taking the position that if you know the set of filenames at issue does not contain any embedded nonsense (like daily server logs, etc.), then there are no other hidden adverse effects from using ls in this capacity. Certainly you would not be condemned to hell or have your eyes plucked out by dragons if you did. So that brings up the question: "Just which files do have embedded control characters (intentionally, and not as the result of some horrible mistake)?" The only example I have uncovered thus far is the OSX 'icon' file that has a 'carriage-return' intentionally embedded as part of the filename. What others have you run across or can think of? I could think of no better or more experienced group to consult that the good old "brain-trust". So just how prevalent are these filenames with embedded control characters? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org