src/usr.bin/random, branch releng/13.4

Remove $FreeBSD$: one-line nroff pattern

2023-08-23T17:43:32Z

Remove /^\.\\"\s*\$FreeBSD\$$\n/ Similar commit in main: (cherry picked from commit b2c76c41be32)

Remove $FreeBSD$: one-line sh pattern

2023-08-23T17:43:30Z

Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ Similar commit in main: (cherry picked from commit d0b2dbfa0ecf)

Remove $FreeBSD$: one-line .c pattern

2023-08-23T17:43:26Z

Remove /^[\s*]*__FBSDID$"\$FreeBSD\$"$;?\s*\n/ Similar commit in main: (cherry picked from commit 1d386b48a555)

Remove $FreeBSD$: two-line .h pattern

2023-08-23T17:43:21Z

Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ Similar commit in main: (cherry picked from commit b3e7694832e8)

random(6): Re-add undocumented support for floating point denominators

2020-02-15T19:13:37Z

And document it in the manual page. PR: 244139 Submitted by: Keith White (earlier version)

random(6): Fix off-by-one

2020-01-16T21:38:44Z

After r355693, random(6) -f sometimes fail to output all the lines of the input file. This is because the range from which random indices are chosen is too big, so occasionally the random selection doesn't correspond to any line and nothing gets printed. (Ed. note: Mea culpa. Working on r355693, I was confused by the sometime use of 1-indexing, sometimes 0-indexing in randomize_fd().) Submitted by: Ryan Moeller X-MFC-With: r355693 Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D23199

random(6): produce random results

2019-12-13T04:37:39Z

This program is trash and there's no reason to keep it in base. But as long as we're shipping a silly program named 'random', let's actually make it random.

DIRDEPS_BUILD: Update dependencies.

2017-10-31T00:07:04Z

Fix a (false positive?) Argument cannot be negative coverity defect.

2016-06-08T02:14:05Z

Rather than guarding close(fd) with an fd >= 0 test and setting fd to -1 when it is closed to avoid a potential double-close, just move the close() call after the conditional "goto make_token". This moves the close() call totally outside the loop to avoid the possibility of calling it twice. This should also prevent a Coverity warning about checking fd for validity after it was previously passed to read(). Reported by: Coverity CID: 1355335 MFC after: 1 week X-MFC with: r299484

random(6): Fix double-close

2016-05-11T22:04:28Z

In the case where a file lacks a trailing newline, there is some "evil" code to reverse goto the tokenizing code ("make_token") for the final token in the file. In this case, 'fd' is closed more than once. Use a negative sentinel value to guard close(2), preventing the double close. Ideally, this code would be restructured to avoid this ugly construction. Reported by: Coverity CID: 1006123 Sponsored by: EMC / Isilon Storage Division