Re (2): What am I doing wrong ?
in [Slackware]
|
Prev: Downloading 13.1?
Next: apache and logrotate
From: Joe Beanfish on 12 Jul 2010 13:21 On 07/09/10 15:01, Kenny McCormack wrote: > In article<89nv0nF6u6U1(a)mid.individual.net>, > Chris F.A. Johnson<cfajohnson(a)gmail.com> wrote: >> On 2010-07-09, Tarkin wrote: >> ... >>> Recent distro's and/or kernels(?) will allow space(s) in filenames. >> >> All *nix filesystems have always accepted spaces in filenames. In >> fact, the only characters *not* permitted in filenames are the NUL >> (ASCII 0) and the slash (/). > > They just have had the good sense not to exploit it. > > Note that Windows is, in fact, quite a bit *more* restrictive than Unix > is, in this regard. The obvious example being that Windows forbids a > line feed in a filename (No flames, please, but I think we can agree > that this is a Good Thing). This makes it funny that some people think > that Windows brought the problem to the table - i.e, that Unix didn't > allow it and never had to deal with the problem until that icky Windows > thing came along and started besmirching our servers. > > But of course (And yes, I'm now arguing against myself), it is true in a > way that Windows (*) caused the problem, since, as I said above, Unix > systems have always had the good sense not to use it (even though they > always had it...) > > (*) And other "friendly GUI" systems, such as Mac. I don't mean to > completely single out Windows here. > Actually I'd have to say it's the friendly UI that brought us spaces in filenames. When you have to type command lines you don't generally put spaces in filenames. When you have a file name input box you type whatever you please.
From: Kenny McCormack on 12 Jul 2010 13:40
In article <i1fiuh$tam(a)news.thunderstone.com>, Joe Beanfish <joe(a)nospam.duh> wrote: >On 07/09/10 15:01, Kenny McCormack wrote: >> In article<89nv0nF6u6U1(a)mid.individual.net>, >> Chris F.A. Johnson<cfajohnson(a)gmail.com> wrote: >>> On 2010-07-09, Tarkin wrote: >>> ... >>>> Recent distro's and/or kernels(?) will allow space(s) in filenames. >>> >>> All *nix filesystems have always accepted spaces in filenames. In >>> fact, the only characters *not* permitted in filenames are the NUL >>> (ASCII 0) and the slash (/). >> >> They just have had the good sense not to exploit it. >> >> Note that Windows is, in fact, quite a bit *more* restrictive than Unix >> is, in this regard. The obvious example being that Windows forbids a >> line feed in a filename (No flames, please, but I think we can agree >> that this is a Good Thing). This makes it funny that some people think >> that Windows brought the problem to the table - i.e, that Unix didn't >> allow it and never had to deal with the problem until that icky Windows >> thing came along and started besmirching our servers. >> >> But of course (And yes, I'm now arguing against myself), it is true in a >> way that Windows (*) caused the problem, since, as I said above, Unix >> systems have always had the good sense not to use it (even though they >> always had it...) >> >> (*) And other "friendly GUI" systems, such as Mac. I don't mean to >> completely single out Windows here. >> > >Actually I'd have to say it's the friendly UI that brought us spaces >in filenames. When you have to type command lines you don't generally >put spaces in filenames. When you have a file name input box you type >whatever you please. Quite so. -- > No, I haven't, that's why I'm asking questions. If you won't help me, > why don't you just go find your lost manhood elsewhere. CLC in a nutshell. |