Dave Morgan [dave.mor...@coolplaces.ca]
> Still had to deal with spaces in the mount point and filename though. :(
No problem, just use -print0 ...
$ uname -s
SunOS
$ find . -print0
find: bad option -print0
find: [-H | -L] path-list predicate-list
$
so long:
unset LC_ALL LC_COLLATE LANG LC_CTYP
On 28/02/13 01:12 PM, André Warnier wrote:
Randolf Richardson wrote:
In truth, Microsoft is not alone there. An Apache httpd by default installs
under a
(created) directory named "Apache Software Foundation" of all things. One would
think that
/they/ at least would know better. But no. Why ma
Randolf Richardson wrote:
alexander.elg...@external.t-systems.com wrote:
...
I am pretty shure, I tested the capability of filenames on a Linux (ext2) or
Solaris (ufs) filesystem, a long time ago
The outcome was, that you can use 254 different characters, except the '\0' and
the '/'.
Apple's
> alexander.elg...@external.t-systems.com wrote:
> ...
> > I am pretty shure, I tested the capability of filenames on a Linux (ext2)
> > or Solaris (ufs) filesystem, a long time ago
> > The outcome was, that you can use 254 different characters, except the '\0'
> > and the '/'.
Apple's older pre
David Booth wrote:
On 02/28/2013 09:32 AM, Torsten Förtsch wrote:
On 02/28/2013 03:14 PM, demerphq wrote:
A special place in hell is reserved for programmers that write code
that assumes that spaces and other unprintables are illegal in a
filename.
Yes, right next door to another place in hel
On 02/28/2013 09:32 AM, Torsten Förtsch wrote:
On 02/28/2013 03:14 PM, demerphq wrote:
A special place in hell is reserved for programmers that write code
that assumes that spaces and other unprintables are illegal in a
filename.
Yes, right next door to another place in hell that is reserved f
demerphq wrote:
On 28 February 2013 13:29, André Warnier wrote:
alexander.elg...@external.t-systems.com wrote:
...
I am pretty shure, I tested the capability of filenames on a Linux (ext2)
or Solaris (ufs) filesystem, a long time ago
The outcome was, that you can use 254 different characters,
Hi all,
please, please don't forget to restrict yourself
to the 8.3 naming convention. Anything else is
troublesome...
... the executable perl.exe is not named by
accident but follows deep wisdom.
;-)
McA
-Ursprüngliche Nachricht-
Von: demerphq [mailto:demer...@gmail.com]
Gesendet: Do
On 02/28/2013 03:14 PM, demerphq wrote:
> A special place in hell is reserved for programmers that write code
> that assumes that spaces and other unprintables are illegal in a
> filename.
+1
Torsten
On 28 February 2013 13:29, André Warnier wrote:
> alexander.elg...@external.t-systems.com wrote:
> ...
>
>> I am pretty shure, I tested the capability of filenames on a Linux (ext2)
>> or Solaris (ufs) filesystem, a long time ago
>> The outcome was, that you can use 254 different characters, excep
On 2/28/2013 7:29 AM, André Warnier wrote:
The person who invented that spaces and other unprintable characters
were allowed in filenames and paths should be found, his PC and iPhone
should be confiscated, he should be exiled to an isolated island in
the middle of the Arctic Ocean, and he shoul
alexander.elg...@external.t-systems.com wrote:
...
I am pretty shure, I tested the capability of filenames on a Linux (ext2) or
Solaris (ufs) filesystem, a long time ago
The outcome was, that you can use 254 different characters, except the '\0' and
the '/'.
But I agree, it is an annoyance it
On 02/28/2013 12:31 PM, alexander.elg...@external.t-systems.com wrote:
>
>> > [Wed Feb 13 16:27:33 2013] [error] [client 192.168.254.21] Unsuccessful
>> > stat on filename containing newline at
>> > /usr/local/lib64/perl5/ModPerl/RegistryCooker.pm line 787.\
> [Wed Feb 13 16:27:33 2013] [error] [client 192.168.254.21] Unsuccessful
> stat on filename containing newline at
> /usr/local/lib64/perl5/ModPerl/RegistryCooker.pm line 787.\n
I am confused, because a filename is able to contain newlines.
0 Alexander_hel
On 02/14/2013 02:39 AM, Michael A. Capone wrote:
> [Wed Feb 13 16:27:33 2013] [error] [client 192.168.254.21] Unsuccessful
> stat on filename containing newline at
> /usr/local/lib64/perl5/ModPerl/RegistryCooker.pm line 787.\n
>
> ... which in turn results in a 500 Server Error.
The culprit here
15 matches
Mail list logo
