Gilles Espinasse wrote:
...
Insecure directory in $ENV{PATH} while running with -T switch at -
...
Is some directory in your $PATH group- or world-writable?
It is insecure also if a parent of one of those directories is
group- or world-writable.
should not
find `echo $PATH | sed 's/:/
I've just pushed a few changes:
build: do use AM_GNU_GETTEXT's need-formatstring-macros option
Already discussed. Reverts my s/need-formatstring-macros/ngettext/
change and adds this comment:
# As long as grep 'PRI[diouxX]' po/*.pot reports matches in
#
Dear http://www.dict.cc/englisch-deutsch/Dear.html Sir
http://www.dict.cc/englisch-deutsch/Sir.html or
http://www.dict.cc/englisch-deutsch/or.html Madam
http://www.dict.cc/englisch-deutsch/Madam.html ,
I am a user of Teamcenter engineering V9.02. now I have a problem about
On Mon, 16 Nov 2009, Feng Jin wrote:
I am a user of Teamcenter engineering V9.02. now I have a problem about
-regen_schema_file.
[snip]
c:\temp\tcenginstall -regen_schema_file -u=infodba -p=infodba -g=dba
install: invalid option -- r
Try `install --help' for more information.
You have
Hello,
The Commands ls (and others) and mkdir interpret Wildcard in different
ways:
- lsfil*/te*/file
is ok, but
- mkdir fi*/te*/directory
doesn't work (only mkdir file/text/directory)
I think, mkdir is an internal command, but wildcards should be allowed
too.
Greetings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Stefan Menne on 11/16/2009 7:10 AM:
Hello,
The Commands ls (and others) and mkdir interpret Wildcard in different
ways:
No, they don't interpret wildcards at all. Globbing is a function of the
shell, performed prior to ls or
I expect this to be very similar to coreutils-8.1.
Please give it a spin and report back that you did.
This release inherits many portability improvements
from gnulib (thanks mostly to Eric Blake), so if you can
test on *BSD or Solaris, you should see fewer failed tests.
The main change in
Hello,
Eric Blake writes:
By the way, if you want to be portable to Solaris /bin/sh, you have to use:
export POSIXLY_CORRECT
POSIXLY_CORRECT=
(the two lines can appear in either order).
FWIW, you need to re-export a variable each time you change it; otherwise,
it is possible that the
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
export POSIXLY_CORRECT
POSIXLY_CORRECT=
(the two lines can appear in either order).
FWIW, you need to re-export a variable each time you change it; otherwise,
it is possible that the variable has the new value, but the environment
Eric Blake writes:
| Therefore you should `export' again each environment variable that
| you update; the export can occur before or after the assignment.
You only have to do the export once for the life of the shell, not once per
assignment.
Yep, you're right. Sorry for the confusion,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 11/9/2009 6:56 AM:
FeeBSD 6 failures
misc/env
+ env -u a=b true
+ fail=1
Hmm, I'll take a look at that. Sounds like we need rpl_unsetenv to reject
invalid arguments.
gnulib should work around this now.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 11/14/2009 12:48 PM:
However, I'm now seeing a failure on OpenBSD, where chown refuses to
change ctime on files if there is no change to ownership:
$ touch a
$ gstat -c %z a
2009-11-14 20:06:35.175893000 +0100
$
12 matches
Mail list logo
