FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-03-17T10:02:59Z 2020-03-17T10:02:59Z Mateusz Piotrowski 0mp@FreeBSD.org 2020-03-17T10:02:59Z urn:sha1:3431172fa862dccb2a8b918161da186cfafc95f0 It turns out that units(1) is not as horrible to use in scripts as I initially thought. When the --terse flag is combined with an appropriate output format (set via --output-format), units(1) is actually capable of producing very nice results. For example: units -o %0.f -t '4 gigabytes' bytes is is just going to print out the expected value of 4294967296. There is no time to waste. People have to know about it. I am adding an example for this at the top of the examples section because this is what users are most likely looking for. Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D24096 2020-02-03T15:22:46Z Mateusz Piotrowski 0mp@FreeBSD.org 2020-02-03T15:22:46Z urn:sha1:4a3b87e295e2149f7a22b41839e5df19f2b836b1 Changes to units.1: - Change the description to a more descriptive "conversion calculator". - Sort options. - Split the description into sections to make it easier to navigate the manual page. - Improve the description of various options. - Document the default value of the output format. - Use more mdoc macros for better readability. - Document the behavior of the PATH environmental variable. - Improve examples. - Add sections: EXIT STATUS, DIAGNOSTICS, and HISTORY. - Document that units(1) cannot convert negative values and it handles long unit lists poorly. - Update the documentation of the -V flag to match the implementation. units(1) prints its version and the units data file instead of its version and usage information. Changes to units.c: - Update usage information. - Sort longopts elements. This commit does not attempts to change the current behavior of units(1). What's left to do is probably defining a better versioning (at the moment units(1) always reports "FreeBSD units" as its version) and changing the behavior of the -V flag to only print version. Reviewed by: allanjude (earlier version), bcr Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D18977 2019-01-21T15:27:58Z Glen Barber gjb@FreeBSD.org 2019-01-21T15:27:58Z urn:sha1:6b27f978f52da937226cf265cd2662b82aeeb79d Submitted by: Larry Hynes MFC after: 3 days Sponsored by: The FreeBSD Foundation 2018-11-04T19:24:49Z Mariusz Zaborski oshogbo@FreeBSD.org 2018-11-04T19:24:49Z urn:sha1:377421df9690cddad7f0c8cba84bd392e62a3b6c Use caph_{rights,ioctls,fcntls}_limit to simplify the code. 2018-06-19T23:43:14Z Mariusz Zaborski oshogbo@FreeBSD.org 2018-06-19T23:43:14Z urn:sha1:7672a0148f79063eac8f8e0beb0db5350d02d5d4 No functional change intended. 2018-06-16T21:07:46Z Eitan Adler eadler@FreeBSD.org 2018-06-16T21:07:46Z urn:sha1:943a127c89801ea40eb3c8417ccc4b931b73d01f - prefer braces to abusing the `,` operator - mark dead function as dead - remove dead break 2018-01-15T17:27:43Z Eitan Adler eadler@FreeBSD.org 2018-01-15T17:27:43Z urn:sha1:9cd768a17735cba98c4fe80ec76e5bbdcda118c5 CID: 978392 Reviewed by: des MFC After: 1 week 2018-01-05T07:24:43Z Eitan Adler eadler@FreeBSD.org 2018-01-05T07:24:43Z urn:sha1:21dc7ae75beea1fbd1571dcf906c215e9e15b690 PR: 209850 MFC After: 3 days 2017-11-27T15:37:16Z Pedro F. Giffuni pfg@FreeBSD.org 2017-11-27T15:37:16Z urn:sha1:1de7b4b805ddbf2429da511c053686ac4591ed89 Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task. The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. No functional change intended. 2017-10-31T00:07:04Z Bryan Drewery bdrewery@FreeBSD.org 2017-10-31T00:07:04Z urn:sha1:ea825d02749f382c3f7e17f28247f20a48733eab Sponsored by: Dell EMC Isilon