Andre Gompel wrote:
Dear colleague:
it looks like a bug... or at least a short comming.
If I use the -n or -g option I cannot sort according to the output format of
the du or ls commands.
Example:
du -chs * |sort -n |more
I am not sure what would be the best approach, but I would
Paul Eggert [EMAIL PROTECTED] wrote:
...
We could get fancier and use fchmod for readable directories and for
readable or writeable regular files, falling back on lchmod for
everything else; but this still suffers from the same race conditions
that lchmod suffers from, and I'm not sure it's
Theodoros V. Kalamatianos wrote:
Personally, whenever I package coreutils for my system I prefer to move
several basic utilities (env included) to /bin and symlink them from
/usr/bin. That way I am safer should I ever have /bin and /usr in separate
partitions, and I am still compatible with
Paul Eggert wrote:
Bob Proulx writes:
On what systems is env located in /bin/env? The normal location is in
/usr/bin/env.
POSIX doesn't specify the location for env, so either location conforms
to POSIX. On Solaris 10, the standard location is /usr/xpg4/bin/env.
(/usr/bin/env doesn't
Shigeru Makino wrote:
But I feel the charm to write follows;
#! /usr/bin/env awk -f
rather then
#! /usr/local/bin/awk -f or #! /usr/bin/awk -f
There is charm in working within the limitations of the system too.
The specification against POSIX requirements.
If I crick doing env hacking, are
* Paul Eggert ([EMAIL PROTECTED]) wrote:
Dr. David Alan Gilbert [EMAIL PROTECTED] writes:
Now as I understand it the Unix time can't represent the
leapsecond in the seconds-since-epoch, but if that is a valid
UTC date then should it really accept it as input ?
Yes, on hosts that
On Solaris 10, the standard location is /usr/xpg4/bin/env.
(/usr/bin/env doesn't conform to POSIX, I guess)
I have a hard time imagining in what way /usr/bin/env would not
conform to POSIX.
On Solaris 10, /usr/bin/env invokes /usr/bin/sh, which does not
conform to POSIX in several
Dr. David Alan Gilbert [EMAIL PROTECTED] writes:
Are you sure that whatever change made date stop taking
the 60 only stopped it on hosts that don't support leap second?
I did verify that it worked on my host, when I configured it for leap
seconds (which I normally don't do):
521-penguin $
