03-15-2023, 12:15 PM
"Invalid" on Linux could include whatever ASCII code is less than 32. Could create a "fork bomb" with a control character. It's possible to put a newline as part of a filename which is sick.
The "bash" command processor in particular is very fussy, one could pull his/her hair out trying to program a script toward a list of filenames containing CHR$(32) spaces, apostrophe (needed most of the time to precisely quote stuff), ampersand (one of them launches a process and keeps it going, two of them is like colon in BASIC), colon (path separator), dollar sign (preface environment variables and replaceable parameters), grave accent (needed to fire a second instance of "bash" to then use the "stdout" out of it) and stuff like that.
A programmer might like to employ "bash" sometimes to see if a filename is "legal" on Linux.
The "bash" command processor in particular is very fussy, one could pull his/her hair out trying to program a script toward a list of filenames containing CHR$(32) spaces, apostrophe (needed most of the time to precisely quote stuff), ampersand (one of them launches a process and keeps it going, two of them is like colon in BASIC), colon (path separator), dollar sign (preface environment variables and replaceable parameters), grave accent (needed to fire a second instance of "bash" to then use the "stdout" out of it) and stuff like that.
A programmer might like to employ "bash" sometimes to see if a filename is "legal" on Linux.