Scott Ferguson <prettyfly.producti...@gmail.com> writes:

> On 25/06/11 10:16, lee wrote:
>> Scott Ferguson <prettyfly.producti...@gmail.com> writes:
>> 
>>> I don't think the "no white spaces" and "no accented characters"
>>> "rule" is valid in the 21st century. But if some one can put up an
>>> authoritative, and recent, reason I'll reconsider.
>> 
>> Since (unfortunately) there isn't anything preventing users from
>> creating files with names that contain special characters or spaces, you
>> could say that there isn't such a rule anymore.
>
> There is...

Where? :)

>> Nonetheless I advise against it, very un-authoritatively of course,
>> because it can be troublesome to create files with special characters or
>> spaces in their names.
>> 
>> To give a silly example, a file named "-rf *" or "rm -rf *" 
>
> I defy you to create a file with those name ;-p
> NOTE: I've tried. No point in it just being an untested opinion.

You can just rename a file with:

 # mv 1307474391 "rm -rf *"

,----
| lee@yun:~/tmp/naming$ ls -la
| insgesamt 52
| drwxr-xr-x  2 lee lee  4096 25. Jun 15:48 .
| drwx------ 12 lee lee 32768 25. Jun 15:48 ..
| -rw-r--r--  1 lee lee   116  9. Jun 16:35 -rf
| -rw-r--r--  1 lee lee    94  7. Jun 21:19 rm -rf *
| -rw-r--r--  1 lee lee    94  7. Jun 21:17 rm -rf \*
| -rw-r--r--  1 lee lee    94  7. Jun 21:16 rm -rf 1307474137
| lee@yun:~/tmp/naming$ 
`----

I haven't tried touch, it'll probably work the same. A nice application
might be to provide "rm -rf *" as a filename for an attachment to an
email?

Now how to remove these files gives me something to think about very
carefully ... :(

>> could turn
>> out to be disastrous. Using other special characters, for example ä, ü,
>> ö, and ß, can give you trouble when locale settings change and may have
>> effects that I'm even not aware of.
>> 
>> It's only common sense not to create file names that are likely to yield
>> unexpected results.
>> 
>
> Agreed - but *as it's not possible* my agreement is worthless. It also
> belies the point of UTF.

See above, there's no problem in creating files named "rm -rf *". That
makes me think that system administrators should have a way of
specifying for each file system and globally which characters they allow
in file names and which ones not.

Should I send a feature request on the kernel package?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ipru2eue....@yun.yagibdah.de

Reply via email to