History log of /dragonfly/bin/ls/ls.c (Results 1 – 25 of 32)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0
# 5ca0a96d 28-Dec-2020 Sascha Wildner <saw@online.de>

Remove last remains of FSMID support from userland.

The kernel side was added in 2005 (7d15906a7a159575b1983f7c1fadde4b)
and removed again in 2009 (d98152a8b8a4b368ca0e08b84302f2f2).

Approved-by: d

Remove last remains of FSMID support from userland.

The kernel side was added in 2005 (7d15906a7a159575b1983f7c1fadde4b)
and removed again in 2009 (d98152a8b8a4b368ca0e08b84302f2f2).

Approved-by: dillon

show more ...


# d50f9ae3 27-Sep-2020 Sascha Wildner <saw@online.de>

world: Staticize various variables and also remove a couple of unused ones.


Revision tags: v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc
# 4c605ac6 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Add -_ option to include nanotime in ls -l.

Very useful when debugging Makefile races in rules with
vfs.timestamp_precision=1 set.
Yes, ls -l_ seems strage, but we are running out of letters

ls(1): Add -_ option to include nanotime in ls -l.

Very useful when debugging Makefile races in rules with
vfs.timestamp_precision=1 set.
Yes, ls -l_ seems strage, but we are running out of letters and
FreeBSD already has the "-," flag in their ls(1).

show more ...


# dc3f655c 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Add -D option to set date-time format in ls -l.

Taken-from: FreeBSD


# 6a6a7e62 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Sort flags by order in usage() and manpage.

Add missing 'S' in SYNOPSIS.

While there, move out trailing space separator handling to caller.


# 9e5de6b5 25-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Minor cleanup.

No functional change.


Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2
# c9868806 08-Dec-2015 John Marino <draco@marino.st>

ls(1): Fix sort-by-size bug

For a reason that escapes me, in order to sort files by size using ls(1),
one had to pass both the size sort switch (-S) and the time sort switch
(-t), otherwise the -S f

ls(1): Fix sort-by-size bug

For a reason that escapes me, in order to sort files by size using ls(1),
one had to pass both the size sort switch (-S) and the time sort switch
(-t), otherwise the -S flag would be ignored. This hacky workaround was
documented in the man page as well.

Let's fix this with code taken from FreeBSD. The -t and -S switches are
now mutually exclusive. If someone uses them together, then the last
one wins (e.g. ls -st sorts by mod. time and -ts sorts by file size)

show more ...


Revision tags: v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2
# 5f97f1a2 03-Apr-2014 Sascha Wildner <saw@online.de>

ls(1): Restore the traditional behavior of -f implying -a.

OpenBSD's commit msg:

------
restore the traditional behavior of -f implying -a; apparently Keith Bostic
forgot to restore it when the -f

ls(1): Restore the traditional behavior of -f implying -a.

OpenBSD's commit msg:

------
restore the traditional behavior of -f implying -a; apparently Keith Bostic
forgot to restore it when the -f flag was put back on 2nd of September 1989,
after being removed on 16th of August as a consequence of issues getting it
working over NFS, so deviation from traditional UNIX behavior in all BSDs
looks like an historical accident; as a side effect, this change accommodates
behavior of this option to IEEE Std 1003.1-2008 (``POSIX.1'').

joint work with jmc@ (who found the inaccuracy in our implementation),
schwarze@ (who provided a detailed tracking of historical facts) and millert@

ok millert@, schwarze@
------

The same patch has been pushed to NetBSD and FreeBSD too.

Submitted-by: Igor Sobrado
Taken-from: OpenBSD

show more ...


Revision tags: v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3
# dc71b7ab 31-May-2013 Justin C. Sherrill <justin@shiningsilence.com>

Correct BSD License clause numbering from 1-2-4 to 1-2-3.

Apparently everyone's doing it:
http://svnweb.freebsd.org/base?view=revision&revision=251069

Submitted-by: "Eitan Adler" <lists at eitanadl

Correct BSD License clause numbering from 1-2-4 to 1-2-3.

Apparently everyone's doing it:
http://svnweb.freebsd.org/base?view=revision&revision=251069

Submitted-by: "Eitan Adler" <lists at eitanadler.com>

show more ...


Revision tags: v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0
# ff1f883e 14-Sep-2012 Matthew Dillon <dillon@apollo.backplane.com>

ls - Add -I to reverse -A

* ls implies -A when run as root. Add the -I option
which disables this behavior.

* Note that -A and -I will override each other on the
command line.


Revision tags: v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0
# e084722f 24-Oct-2009 Sascha Wildner <saw@online.de>

ls(1): Remove dead initialization.


Revision tags: v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1
# 59b616d3 27-Feb-2009 Peter Avalos <pavalos@theshell.com>

Sync fts(3) with FreeBSD.

Here's some of the relevant commit logs from FreeBSD:

FTSENT now avoids the use of the struct hack, thereby allowing future
extensions to the structure (e.g., for extended

Sync fts(3) with FreeBSD.

Here's some of the relevant commit logs from FreeBSD:

FTSENT now avoids the use of the struct hack, thereby allowing future
extensions to the structure (e.g., for extended attributes) without
rebreaking the ABI. FTSENT now contains a pointer to the parent stream,
which fts_compar() can then take advantage of, avoiding the undefined
behavior previously warned about. As a consequence of this change, the
prototype of the comparison function passed to fts_open() has changed
to reflect the required amount of constness for its use. All callers
in the tree are updated to use the correct prototype.

Comparison functions can now make use of the new parent pointer to
access the new stream-specific private data pointer, which is intended
to assist creation of reentrant library routines which use fts(3)
internally.

The FTS_NOSTAT option is an optimisation that reduces the number
of stat(2) calls by keeping an eye of the number of links a directory
has. It assumes that each subdirectory will have a hard link to its
parent, to represent the ".." node, and stops calling stat(2) when
all links are accounted for in a given directory.

This assumption is really only valid for UNIX-like filesystems: A
concrete example is NTFS. The NTFS "i-node" does contain a link
count, but most/all directories have a link count between 0 and 2
inclusive. The end result is that find on an NTFS volume won't
actually traverse the entire hierarchy of the directories passed
to it. (Those with a link count of two are not traversed at all)

The fix checks the "UFSness" of the filesystem before enabling the
optimisation.

In fts_build(), if we try to chdir and fail (e.g. due to lack of search
permission), try to continue in FTS_DONTCHDIR mode. Of course this
won't work for long paths, but we can't descend more than one pathname
component beyond the directory anyway if we lack search permission.

Our fts(3) API, as inherited from 4.4BSD, suffers from integer
fields in FTS and FTSENT structs being too narrow. In addition,
the narrow types creep from there into fts.c. As a result, fts(3)
consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary
user can create, which can have security implications.

Fix a file descriptor leak.

show more ...


# 76dc7fb4 26-Feb-2009 Sascha Wildner <saw@online.de>

ls(1): Fix amd64 warnings.


Revision tags: v2.2.0, v2.3.0, v2.1.1, v2.0.1
# 36860a8b 19-Jan-2008 Matthias Schmidt <matthias@dragonflybsd.org>

Introduce a new option -S to use the size of a file for sorting (-t). This
is handy to find fat files and brings us in line with all the other BSDs.


# 86a99984 19-Jun-2006 Simon Schubert <corecode@dragonflybsd.org>

Coverity CID 1755: Add fts_close() in traverse.

Taken from: NetBSD via Coverity Prevent
Submitted by: Gary <gary@velocity-servers.net>


# 6fb88001 12-Jan-2006 Simon Schubert <corecode@dragonflybsd.org>

Check for setenv/putenv's success

Submitted-by: Alexey Slynko <slynko@tronet.ru>


# 20d719bf 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD:

Bump Id where needed.

Constify parameters that do not get touched.

Do something sensible if both -h and -k are given.

If we are asked to print the total number of blocks

Synchronise with FreeBSD:

Bump Id where needed.

Constify parameters that do not get touched.

Do something sensible if both -h and -k are given.

If we are asked to print the total number of blocks, do so even if we
have no entries to print (either due to an empty directory or an
error). This makes the -l and -s options more consistent, like
Solaris and (Debian) Linux. To make this happen, tweak two
optimizations on the second call to display():

- Don't skip display() altogether, even if list == NULL.
- Don't skip the call to the printfn in display() if we
need to print the total.

Small clean ups and casts.

show more ...


# dbea5896 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Partial synch with FreeBSD 1.74:

Make the first parameter to display() const.

Move the initmax2 assignment a bit down, after jinitmax's malloc() succeeds.

Update the maxblock, maxinode, and maxnli

Partial synch with FreeBSD 1.74:

Make the first parameter to display() const.

Move the initmax2 assignment a bit down, after jinitmax's malloc() succeeds.

Update the maxblock, maxinode, and maxnlink variables to the current types
and reflect this in the format specifiers.

show more ...


# a65d909f 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Add inttypes.h for intmax_t.


# 495d2386 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Partial synch with FreeBSD v1.74:

convert makenines() to a macro.


# 788f761f 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD v1.65:

Use FALLTHROUGH instead of some hand-rolled alternative.
This allows us to use lint.


# 6a1086b2 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Make sure err() does not use a NULL format string, this way we at least
know what part is failing.

Synchronises with FreeBSD, apparently GCC can complain about it.


# 75fed8fd 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Get rid of the third clause from the UCB license.


# d20227c1 17-Sep-2005 Matthew Dillon <dillon@dragonflybsd.org>

Add an option, -y, which displays the 64 bit FSMID for a file or directory.


12