#
296373 |
|
04-Mar-2016 |
marius |
- Copy stable/10@296371 to releng/10.3 in preparation for 10.3-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.3. - Update default pkg(8) configuration to use the quarterly branch.
Approved by: re (implicit) |
#
289965 |
|
25-Oct-2015 |
ngie |
MFC r288330,r288423,r288678,r288905,r288906,r288907,r289102:
r288330:
Add initial testcases for bin/ls
Sponsored by: EMC / Isilon Storage Division
r288423:
Skip the B_flag testcase to stop blowing up freebsd-current@ with "test failure emails" because kyua report-jenkins doesn't properly escape non-printable chars
r288678:
Merge additional testcases and improvements to bin/ls/ls_tests from ^/user/ngie/more-tests.
- Additional testcases added: -- ls -D -- ls -F -- ls -H -- ls -L -- ls -R -- ls -S -- ls -T -- ls -b -- ls -d -- ls -f -- ls -g -- ls -h -- ls -i -- ls -k -- ls -l -- ls -m -- ls -n -- ls -o -- ls -p -- ls -q/ls -w -- ls -r -- ls -s -- ls -t -- ls -u -- ls -y - Socket file creation is limited to the ls -F testcase, greatly speeding up the test process - The ls -C testcase was made more robust by limiting the number of columns via COLUMNS and by dynamically formulating the columns/lines. - Add `atf_test_case` before all testcase `head` functions.
Sponsored by: EMC / Isilon Storage Division
r288905:
Add some more syncs to quiesce the filesystem after creating the files to see if this fixes deterministic Jenkin failures
r288906:
Explicitly set BLOCKSIZE to 512 in the environment
r288907:
Call sync consistently using atf_check
Remove superfluous sync's
r289102:
Remove all of the syncs
They're unnecessary as shown by further testing on my VM
Requested by: jhb
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
235655 |
|
19-May-2012 |
marcel |
Add build opton MK_LS_COLORS to control whether ls(1) supports colors (and thus needs to depend on libtermcap). Embedded systems may not want or need colors.
Obtained from: Juniper Networks, Inc.
|
#
129719 |
|
25-May-2004 |
pjd |
Use humanize_number(3).
Reminded by: jhb
|
#
116282 |
|
13-Jun-2003 |
markm |
Get this area compiling with the highest WARNS= that it works with. Obsolete WFORMAT= junk also removed where possible.
OK'ed by: obrien Tested on: sparc64, alpha, i386
|
#
105832 |
|
24-Oct-2002 |
rwatson |
Teach "ls -Z" to use the policy-agnostic MAC label interfaces rather than the LOMAC-specific interfaces for listing MAC labels. This permits ls to view MAC labels in a manner similar to getfmac, when ls is used with the -l argument. Next generation LOMAC will use the MAC Framework so should "just" work with this and other policies. Not the prettiest code in the world, but then, neither is ls(1).
Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
|
#
90167 |
|
04-Feb-2002 |
kris |
Correct inadvertent style botches in previous commit.
|
#
90166 |
|
04-Feb-2002 |
kris |
Lock down with WFORMAT=1 except those directories with unfixed warnings. Tested on i386 and alpha.
|
#
90150 |
|
03-Feb-2002 |
markm |
WARNS=4 fixes, plus a healthy dose of fixes inspired by lint.
|
#
88672 |
|
29-Dec-2001 |
bde |
Fixed style bug (unsorting of SRCS) in rev.1.15.
|
#
88671 |
|
29-Dec-2001 |
bde |
Fixed style bugs in revs. 1.6, 1.10 and 1.12.
|
#
88670 |
|
29-Dec-2001 |
bde |
Fixed missing DPADD and disordered LDADD in rev.1.17
Fixed setting of WARNS in rev.1.16. Options should normally be set using using "?=", not using "=", so that the setting is easy to override on the command line, and setting WARNS to 0 should not be an exception.
|
#
88591 |
|
28-Dec-2001 |
joe |
Add a new flag, -h which when combined with the -l option causes file sizes to be displayed with unit suffixes; Byte, Kilobyte, Megabyte, Gigabyte, Terabyte and Petabyte in order to reduce the number of digits to three or less.
Submitted by: nik
|
#
87323 |
|
04-Dec-2001 |
obrien |
Default to WARNS=2. Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
#
86922 |
|
26-Nov-2001 |
green |
Add LOMAC options (the "Z" flag in both cases) to display extra information in ls(1) and ps(1).
Sponsored by: DARPA, NAI Labs
|
#
75126 |
|
03-Apr-2001 |
ru |
Drop support for -DRELEASE_BUILD_FIXIT and -DCRUNCHED_BINARY in ${CFLAGS}. The only supported method thus is -DRELEASE_CRUNCH.
|
#
61749 |
|
17-Jun-2000 |
joe |
Switch over to using the new fflagstostr and strtofflags library calls.
|
#
61288 |
|
05-Jun-2000 |
ache |
Don't use ncurses, use termcap Add DPADD
|
#
61269 |
|
05-Jun-2000 |
joe |
Disable colour support in ls when building the fixit floppy, and make a note of it in the release Makefile.
|
#
61268 |
|
05-Jun-2000 |
joe |
* Re-implement colour support using termcap's AF and AB capabilities to manage the ANSI colour sequences. Colour support is disabled unless the TERM environment variable references a valid termcap.
* Allow optional compilation of the colour support in the Makefile, defaulting to yes. This allows us to switch it off for fixit floppies and other mediums where space is an issue and the extra bloat of statically linking with ncurses isn't acceptable.
* Display a warning if colour is requested with '-G' but support for it isn't compiled in.
|
#
57003 |
|
05-Feb-2000 |
joe |
Revert part of the last commit, remove {g|s}etflags from the libc interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function.
Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem.
There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls).
It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner.
Approved: jkh
|
#
56692 |
|
27-Jan-2000 |
joe |
Historically file flags (schg, uschg, etc) have been converted from string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags.
Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc.
There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags.
The manual page could probably be improved upon ;)
|
#
55302 |
|
01-Jan-2000 |
joe |
Added missing DPADD's. Removed unrequired SRCS's.
Obtained from: bde
|
#
55270 |
|
30-Dec-1999 |
joe |
Moved flags_to_string and string_to_flags into libutil. It's used in many places nowadays.
|
#
50471 |
|
27-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
22988 |
|
22-Feb-1997 |
peter |
Revert $FreeBSD$ to $Id$
|
#
21673 |
|
14-Jan-1997 |
jkh |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
|
#
3044 |
|
24-Sep-1994 |
dg |
Added $Id$
|
#
1557 |
|
26-May-1994 |
rgrimes |
This commit was generated by cvs2svn to compensate for changes in r1556, which included commits to RCS files with non-trunk default branches.
|
#
1556 |
|
26-May-1994 |
rgrimes |
BSD 4.4 Lite bin Sources
|