| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Reviewed by: M. Warner Losh <imp@bsdimp.com>; John Hay <jhay@freebsd.org>
Approved by: M. Warner Losh <imp@bsdimp.com> (mentor)
|
|
|
|
|
|
|
| |
The c89, c99, lex and yacc subdirectories were bogusly added to the
${MACHINE_ARCH} != "ia64" case.
Pointy hat: phk
|
|
|
|
| |
no a.out toolchain.
|
| |
|
|
|
|
| |
Spotted by: tjr
|
|
|
|
|
|
|
| |
NO_TOOLCHAIN skips Compilers and Binutils
NO_USB skips USB stuff
NO_VINUM skips Vinum stuff
NO_ACPI skips ACPI stuff
|
|
|
|
|
| |
may contain crypto. The days of ITAR paranoia are over, and the simple
macro tests that remain are sufficient.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, there were two copies of telnet; a non-crypto version
that lived in the usual places, and a crypto version that lived in
crypto/telnet/. The latter was built in a broken manner somewhat akin
to other "contribified" sources. This meant that there were 4 telnets
competing with each other at build time - KerberosIV, Kerberos5,
plain-old-secure and base. KerberosIV is no longer in the running, but
the other three took it in turns to jump all over each other during a
"make buildworld".
As the crypto issue has been clarified, and crypto _calls_ are not
a problem, crypto/telnet has been repo-copied to contrib/telnet,
and with this commit, all telnets are now "contribified". The contrib
path was chosen to not destroy history in the repository, and differs
from other contrib/ entries in that it may be worked on as "normal"
BSD code. There is no dangerous crypto in these sources, only a
very weak system less strong than enigma(1).
Kerberos5 telnet and Secure telnet are now selected by using the usual
macros in /etc/make.conf, and the build process is unsurprising and
less treacherous.
|
|
|
|
|
|
| |
there are problems with their Makefiles I wasn't aware of..
Pointed out by: ru@
|
|
|
|
|
|
|
| |
These are probably machine independent, but
there is no way for the developers to test them other than on x86.
They will become MD as testing becomes possible.
|
| |
|
|
|
|
| |
Approved by: re (scottl)
|
|
|
|
| |
Approved by: re (scottl)
|
|
|
|
|
| |
cleanups were necessary in release/Makefile, and the tinderbox code
was syntax checked, not run checked.
|
|
|
|
| |
Submitted by: Marius Strobl <marius@alchemy.franken.de>
|
|
|
|
| |
Submitted by: Marius Strobl <marius@alchemy.franken.de>
|
| |
|
|
|
|
|
|
| |
This allows actions to be bound to HID events.
Obtained from: NetBSD
|
| |
|
|
|
|
| |
List from: benno
|
|
|
|
|
| |
We've been installing chflags(1) into /bin since 2000-11-10, so this
shouldn't cause any problems.
|
|
|
|
| |
Sometimes we need kenv(1) in /etc/rc.diskless*.
|
| |
|
| |
|
|
|
|
| |
a sysadmin tool.
|
|
|
|
|
|
|
|
|
| |
The /usr/bin/perl wrapper isn't solving many of the problems it was
imported to deal with. There are limitations to it that don't have a
clear "fix".
Reviewed by: markm, kris
Extorted approval from: re(jhb)
|
|
|
|
|
| |
o xlint is still excluded from the ia64 build, but now in a way
that doesn't corrupt ordering for other platforms.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't gratuitously pipe thru a cat(1) if NODOCCOMPRESS.
Only create _stamp.extra when necessary.
Get rid of SOELIMPP and OBJS.
Use Groff version of soelim(1); we need its -I option
for the following to work.
Don't needlessly chdir to SRCDIR. Only a few documents
need CD_HACK, and those that need it either use refer(1)
or .PSPIC macro which internally uses the .psbb call.
|
|
|
|
|
|
| |
cc -std=iso9899:1999 -pedantic, and is required by SUSv3.
PR; 36087
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
under way to move the remnants of the a.out toolchain to ports. As the
comment in src/Makefile said, this stuff is deprecated and one should not
expect this to remain beyond 4.0-REL. It has already lasted WAY beyond
that.
Notable exceptions:
gcc - I have not touched the a.out generation stuff there.
ldd/ldconfig - still have some code to interface with a.out rtld.
old as/ld/etc - I have not removed these yet, pending their move to ports.
some includes - necessary for ldd/ldconfig for now.
Tested on: i386 (extensively), alpha
|
|
|
|
| |
Compiled on: alpha, sparc64, ia64
|
|
|
|
| |
Noticed by: ru
|
| |
|
| |
|
|
|
|
|
|
| |
implement any of the useless POSIX-required ``regular shell builtin''
utilities, saving one frag and one inode each. The script moves to
usr.bin/alias which is alphabetically the first of these commands.
|
|
|
|
|
| |
external commands. Since they serve no useful purpose, it's OK that their
implementation is not the most efficient possible.
|
| |
|
|
|
|
| |
Approved by: sheldonh (mentor)
|
|
|
|
| |
Approved by: sheldonh (mentor)
|
|
|
|
|
|
|
|
|
|
| |
projects/sccs/sccs/, to accompany projects/sccs/sccscmds, and help will
be dying shortly.
These programs will not be a part of 5.0-RELEASE, at least not in their
current form. They'll either end up in src/contrib or ports.
Submitted by: obrien
|
|
|
|
| |
of this knob to reflect (-)current reality.
|
|
|
|
| |
Fix a trailing ws nit while I'm here
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
PR: 36190
|
|
|
|
| |
Approved by: jake
|
| |
|
| |
|