1

Topic: Problem on

There was a problem on  after the first usage of this. The problem such to create a folder with ` * ` characters and `. ` Can even in cygwin or here try: https://www.tutorialspoint.com/execute_bash_online.php (!) the Help: I not the user of Linux, in the Windows core, therefore at me turned out from the first.  It not a problem on first of April though to it becomes.

2

Re: Problem on

Hello, Vain, you wrote: V> There was a problem on  after the first usage of this. V> a problem such to create a folder with ` * ` characters and `. ` mkdir "*" mkdir ".xxx" (and a file) which name consists of one or two points, it is impossible to create the Folder.

3

Re: Problem on

Hello, Pzz, you wrote: Pzz> mkdir "*" Pzz> mkdir ".xxx" V> the Problem such to create a folder with ` * ` characters and `. ` Pzz> (and a file) which name consists of one or two points, it is impossible to create the Folder. It is assured? I here after that feint from  - am not assured.

4

Re: Problem on

Hello, Vain, you wrote: Pzz>> (and a file) which name consists of one or two points, it is impossible to create the Folder. V> It is assured? I here after that feint from  - am not assured. It is assured

5

Re: Problem on

Hello, Pzz, you wrote: Pzz>>> (and a file) which name consists of one or two points, it is impossible to create the Folder. V>> It is assured? I here after that feint from  - am not assured. Pzz> it is assured Whence if it allows to create such folders with the forbidden characters?

6

Re: Problem on

Hello, Vain, you wrote: Pzz>>>> (and a file) which name consists of one or two points, it is impossible to create the Folder. V>>> It is assured? I here after that feint from  - am not assured. Pzz>> it is assured V> Whence if it allows to create such folders with the forbidden characters? In  for names of files like it is forbidden nothing from a word absolutely. There and line feed in file name can be. Simply some shell characters interprets, and to a kernel . In Windows in another way - some characters are explicitly forbidden to usage in file system. It is not assured, truth, or from  it depends on a kernel

7

Re: Problem on

Hello, Vain, you wrote: V> if it allows to create such folders with the forbidden characters? Why you decided, what it is the forbidden characters? In *nix only two characters are forbidden to usage in file names: / and \0 (the character with the code 0). On remaining there are no explicit restrictions at OS: though asterisks use, though all  . (Here only file system something can forbid to create, if, for example, it old and supports only the ASCII-coding, instead of the same arbitrary ). Pzz>>>> (and a file) which name consists of one or two points, it is impossible to create the Folder. V>>> It is assured? I here after that feint from  - am not assured. Pzz>> it is assured V> Whence? And they already and so are created in each directory smile Quite the reason why cannot create them the second time.

8

Re: Problem on

Hello, Marty, you wrote: M> In Windows in another way - some characters are explicitly forbidden to usage in file system. It is not assured, truth, or from  it depends on a kernel So they and in Windows form. Through cygwin.

9

Re: Problem on

Hello, Vain, you wrote: M>> In Windows in another way - some characters are explicitly forbidden to usage in file system. It is not assured, truth, or from  it depends on a kernel V> So they and in Windows form. Through cygwin. ' * ', '? ', ' / ' and ' \'?

10

Re: Problem on

Hello, Marty, you wrote: M>>> In Windows in another way - some characters are explicitly forbidden to usage in file system. It is not assured, truth, or from  it depends on a kernel V>> So they and in Windows form. Through cygwin. M> ' * ', '? ', ' / ' and ' \'? * and? Form

11

Re: Problem on

Hello, Vain, you wrote: M>>>> In Windows in another way - some characters are explicitly forbidden to usage in file system. It is not assured, truth, or from  it depends on a kernel V>>> So they and in Windows form. Through cygwin. M>> ' * ', '? ', ' / ' and ' \'? V> * and? Form Probably, what ' * ' and '? ' subsystem Win32 processes, and ntkernel them does not process, than  and uses

12

Re: Problem on

Hello, Vain, you wrote: Pzz>> It is assured V> Whence if it allows to create such folders with the forbidden characters? In  there are no the forbidden characters. There are exactly two characters which have special value: "/" - the way separator, and the character with the code 0 - completes a line. "." Is a name of a current directory, "." - a name of its "parent", they already are present at each directory and for this reason they cannot be created. In , by the way, too.

13

Re: Problem on

Hello, Marty, you wrote: M> In  for names of files like it is forbidden nothing from a word absolutely. There and line feed in file name can be. Simply some shell characters interprets, and to a kernel . In  it is possible to create the file name containing such ESC-sequence that if at this name to look through ls the terminal in the answer tells "rm-rf /", or any other command, the blessing that almost at all terminals - to some extent clones VT109.

14

Re: Problem on

Hello, Pzz, you wrote: M>> In  for names of files like it is forbidden nothing from a word absolutely. There and line feed in file name can be. Simply some shell characters interprets, and to a kernel . Pzz> In  it is possible to create the file name containing such ESC-sequence that if at this name to look through ls the terminal in the answer tells "rm-rf /", or any other command, the blessing that almost at all terminals - to some extent clones VT109. "It not the bug, is a feature" (c) is lost

15

Re: Problem on

Hello, Marty, you wrote: Pzz>> In  it is possible to create the file name containing such ESC-sequence that if at this name to look through ls the terminal in the answer tells "rm-rf /", or any other command, the blessing that almost at all terminals - to some extent clones VT109. M> "It not the bug, is a feature" (c) is lost "It not truth that UNIX - not a friendly operating system to the user. Simply UNIX very carefully selects to itself friends" (

16

Re: Problem on

17

Re: Problem on

Hello, Vain, you wrote: V> Hello, Pzz, you wrote: Pzz>>>> (and a file) which name consists of one or two points, it is impossible to create the Folder. V>>> It is assured? I here after that feint from  - am not assured. Pzz>> it is assured V> Whence if it allows to create such folders with the forbidden characters? Mix three essentially different things: 1. The forbidden characters in a way - them exactly two: '\0 ' and ' / '. 2. The reserved auxiliary names - them too two: "." And "." In spite of the fact that simply the point is not the forbidden character, and names into which the point, in any real system more than 100500 enters. But: this reserve - business specific FS, instead of a file subsystem as a whole. It is theoretically possible FS where they are not present (though really any madman of the such does not make). 3. Shell meta characters, into which enters ' * ' (start ), but not a point and not a virgule see. They should screen for instructions in names, there are some different methods of screening. Their composition slightly different for different shells: for example, bash and zsh give a special role for ': ', but not idle time sh (including bash in a mode of compatibility with POSIX sh). NB a special case to (2), not changing an overall picture: the remote directory. We do the following experiment: $ cd/tmp $ mkdir b; cd b $ ls-la total 24 drwxr-xr-x 2 netch netch 4096  1 14:28. drwxrwxrwt 33 root root 20480  1 14:28. $ rmdir/tmp/b $ ls-la total 0$ touch 111 touch: cannot touch ' 111 ': No such file or directory the Directory still exists as leaking for the given process, but contents at it are not present also anything in it it is impossible to make already it is simple the phantom were vnode. The Same if it has been opened separately and it was used for openat () or analog.