sh scripting question
matthew at FreeBSD.org
Fri Oct 16 11:45:11 UTC 2020
On 16/10/2020 12:25, Ralf Mardorf wrote:
> On the quick I was unable to create a file with a
> in it's name (Linux, login shell bash, just using shell commands, no
> tool explicitly aimed to edit/corrupt file system entries). I guess a
> file name containing a "/" overTRUMPs all other odd file names.
There's only two characters you can't have in a Unix filename, which are
'/' -- because it's the directory separator, and '\0' (Null) because C
language strings. Anything else is fair game.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 963 bytes
Desc: OpenPGP digital signature
More information about the freebsd-questions