Per previous discussion, and with Mark's blessing, update the value
of this knob to reflect (-)current reality.

Hook stat into the build
Fix a trailing ws nit while I'm here

Don't build perl if NO_PERL is defined.

Connect perl to the build.

Add uuidgen(2) and uuidgen(1).

The uuidgen command, by means of the uuidgen syscall, generates one
or more Universally Unique Identifiers compatible with OSF/DCE 1.1
version 1 UUIDs.

From the Perfo

Add uuidgen(2) and uuidgen(1).

The uuidgen command, by means of the uuidgen syscall, generates one
or more Universally Unique Identifiers compatible with OSF/DCE 1.1
version 1 UUIDs.

From the Perforce logs (change 11995):

Round of cleanups:
o Give uuidgen() the correct prototype in syscalls.master
o Define struct uuid according to DCE 1.1 in sys/uuid.h
o Use struct uuid instead of uuid_t. The latter is defined
in sys/uuid.h but should not be used in kernel land.
o Add snprintf_uuid(), printf_uuid() and sbuf_printf_uuid()
to kern_uuid.c for use in the kernel (currently geom_gpt.c).
o Rename the non-standard struct uuid in kern/kern_uuid.c
to struct uuid_private and give it a slightly better definition
for better byte-order handling. See below.
o In sys/gpt.h, fix the broken uuid definitions to match the now
compliant struct uuid definition. See below.
o In usr.bin/uuidgen/uuidgen.c catch up with struct uuid change.

A note about byte-order:
The standard failed to provide a non-conflicting and
unambiguous definition for the binary representation. My initial
implementation always wrote the timestamp as a 64-bit little-endian
(2s-complement) integral. The clock sequence was always written
as a 16-bit big-endian (2s-complement) integral. After a good
nights sleep and couple of Pan Galactic Gargle Blasters (not
necessarily in that order :-) I reread the spec and came to the
conclusion that the time fields are always written in the native
by order, provided the the low, mid and hi chopping still occurs.
The spec mentions that you "might need to swap bytes if you talk
to a machine that has a different byte-order". The clock sequence
is always written in big-endian order (as is the IEEE 802 address)
because its division is resulting in bytes, making the ordering
unambiguous.

show more ...

Hook newgrp(1) up to the build.

PR: 36190

Move elf2aout to usr.sbin/.

Approved by: jake

Taking a leap of faith, tie the help command in to the build.

Tie sccs(1) in to the build, as it now does one thing right: sccs what

Remove mention of the GNU version of ptx, it is dead.

Build pathchk(1).

Build the tabs(1) utility.

PR: 36126

elf2aout can be useful to have on all platforms

Don't build getconf if you don't have a full C++ installation.

Add C rewrites of catman and makewhatis. These aren't quite as
the submitter supplied them, as I did some WARNS=n fixups (mostly
const-ification).

Submitted by: John Rochester <john@jrochester.org>

Build the asa(1) utility.

PR: 36130
Reviewed by: mike

Add the csplit(1) utility, which splits files based on context, as specified
by SUSv3.

PR: 36191
Reviewed by: mike

Build elf2aout for sparc64.

Back out the NO_RCMNDS knob.
1. The committer refused to respond to questions over the commit.
2. The servers rlogind, rshd, rexecd were not wrapped.
3. "rcmnds" as an abbreviation gets an order of m

Back out the NO_RCMNDS knob.
1. The committer refused to respond to questions over the commit.
2. The servers rlogind, rshd, rexecd were not wrapped.
3. "rcmnds" as an abbreviation gets an order of magnitude less hits on
Google than the much more well known "rcmds".

show more ...

Revert last change, to be revisited later.

Temporarily unconnect "doscmd" from build until I can fix
its broken Makefile. The breakage is now fatal after the
bsd.prog.mk,v 1.109 change.

Introduce NO_RCMNDS flag so as to not compile rsh, rlogin, and rcp on will,
and document in share/examples/etc/make.conf

Submitted by: Aleksandar Simic <asimic@dsl.pipex.com>
MFC after: 1 week

Disconnect sort

Some things don't compile on ia64 and sparc64 yet.

Exclude xlint for ia64. For the time being, there are enough gcc
dependencies in the machine/* headers to make it explode when -U__GNUC__
is specified by lint. Not to mention that lint is passing u

Exclude xlint for ia64. For the time being, there are enough gcc
dependencies in the machine/* headers to make it explode when -U__GNUC__
is specified by lint. Not to mention that lint is passing undocumented
(illegal?) args to cpp and that seems to upset gcc-3.1 now.
Specifically, -Wp,-CC. -Wp,-C is documented and legal though.

show more ...