Judge: TN3270, you are charged with being superfluous to
requirement, and have been found guilty.
Defence, do you have any final words?
Defence lawyer: Yes,..
*!BLAM!*
Judge: Contempt of court!! That blood is disgusting! Sergeant?
Sergeant: Sah!?
Judge: Get that mess out of here.
Sergeant: Sah!!
Judge: Anyone else have anything else to say?
...
Judge: Executioner!
Executioner: My lord?
Judge: Carry out the sentence, forthwith!
Executioner: As my lord wishes...
*!BLAM!* *!BLAM!* *!BLAM!*
Judge: Any more matters for the court today?
...
`opaque', fix reversed description of `nodump', and don't use
`nodump' as an example of adding a `no' prefix since the double
negative would be confusing (it's still confusing -- the implicitly
documented `nonodump' flag doesn't exist).)
recommended option in the manpage, but the - option remains for
backward compatibility and is documented as such.
PR: 13363
Reported by: James Howard <howardjp@wam.umd.edu>
Reviewed by: bde
(emulate the 'd' linker (?)). This was most harmful for the NOSHARED=yes
case since libskey.o isn't linked to libmd.a.
Fixed the usual disorder of DPADD and LDADD, and some tab lossage.
- Sort xrefs
- Be consistent with section names as outlines in mdoc(7).
- Other misc mdoc cleanup.
PR: doc/13144
Submitted by: Alexey M. Zelkin <phantom@cris.net>
u_quad_int instead of u_long for counters. (NetBSD's rev 1.15 - 1.18)
Deprecate register. (NetBSD's rev 1.13)
The diffs from NetBSD were not applied verbatim, because we don't care
about NO_QUAD right now.
PR: 12959
Reported by: Nicholas Barnes <nb@ravenbrook.com>
Obtained from: NetBSD
February.
If you do a web search for "lionheart crowned" you'll get lots of
conflicting information. Some sites say 3rd September, while others
say 27th February. Most of the "27th February" crowd seem to take their
information from other incarnations of this file on other operating
systems.
After a very pleasant afternoon spent lunching with my girlfriend's
parents, I availed myself of their extensive reference library.
You'd be surprised how hard it is to get concrete information about this.
The _Encyclopedia Brittanica_ doesn't mention the date, only the year, as
does _Brewer's Dictionary of Phrase and Fable_, as do all the other printed
sources I tried. One of them even said July 7th 1189! Microsoft's (yeah,
so sue me) Encarta '95 has quite a comprehensive entry, but again, no
day and month information
In desperation, I tried the web once more, and finally stumbled upon
http://www.btinternet.com/~timeref/hsttime2.htm. This revealed that
Henry II died on 6th July 1189 (presumably the source of the 7th July
entry in another reference), and that Richard was crowned on 3rd
September.
Best of all, this site gives references. So if any of you have a copy of
_The Life and Times of Richard I_, John Gillingham, pub. George Weidenfeld
and Nicholson Limited, 1974, then you can confirm this for yourselves.
For completenesses sake, I tried to find an ISBN number for the above
book. But Amazon and Barnes and Noble don't appear to stock it (although
it looks like a revised version, by the same author, is due out in October
1999, in case anyone's interested).
PR: docs/10488
Submitted by: solon@macaulay.demon.co.uk
that -E only operates for a specified variable. Useful since the -e option
will often pull-in many unwanted variable overrides (esp. in a make world
situation). Uses include overriding BINOWN (which cannot be done by normal
methods or through abuses of MAKEFLAGS) or likely for ports to honour CFLAGS
(provided they're running on a system whose make(1) has this option).
I originally coded this myself, and now I realize {Net,Open}BSD had already
coded this. I have tossed my version to reduce diffs between the projects.
Obtained from: OpenBSD 2.5
match with all of them, rather than only supporting a single user.
PR: 11121
Kinda submitted by: James Howard <howardjp@byzantine.student.umd.edu>
Reviewed by: DES
Remove some whitespace
Fix a problem where any event on the Last whatever of the month
was duplicated after the last day of the month (e.g. 32oct.)
PR: 4907
Submitted by: Mikhail Teterin mi@aldan.algebra.com
it also fixes that fact that this file badly needed to be regenerated due
to changes in yacc.
Not done by: pst (in misc/1380)
Almost done by: danny (in ftp.y)
aren't allowed and the right casts can be used for printf() statements.
Document the conversion specifier limitations and the fact that
arithmetic overflow causes a fatal error.
PR: 12611
Reported by: Frode Vatvedt Fjeld <frodef@acm.org>
Reviewed by: bde
the expected size of the magic(5) database agree with the
real world. Also, improve the behavior of the realloc
mechanism when the magic database does exceed expectations.
Reviewed by: Peter Jeremy, Matt Dillon
Obtained from: Peter Edwards <peter.edwards@isocor.ie>
procfs map file when object IDs were eliminated in the mega-commit
that included procfs_map.c revision 1.19.
The map file is a terrible hodge-podge. The fields that are used
mainly for kernel debugging should be moved out of it into a
separate file, so that the interface presented by the map file to
applications can remain stable in the face of VM system changes.
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
doscmd that was affected by the SA_SIGINFO changes (which made many
lines longer).
This application is in need for general code reformatting and warning
fixes.
Submitted by: Warner Losh <imp@village.org>
support. I've been building world with these changes for months w/o
ill effect. I've also managed to build the cross tool chain for MIPS
with these patches.
Please note that the extent to which these patches work is largely
dictated by how well our tool chains support the cross compilation.
Building alpha binaries on i386 doesn't work. Supposedly building
i386 binaries on alpha does work, but I've not verified it with these
patches, however.
EGCS assign weak symbols to inline functions it couldn't inline (e.g. virtual
inline functions), template functions, etc. Omitting them result in quite bogus
profile.
Weak symbols created by __weak_reference are not really problem.
Caught by: Ilya Segalovich <iseg@comptek.ru>
set to `YES' for passive mode to be used by default.
Just setting FTP_PASSIVE_MODE is not sufficient, as
it was before.
Noted by: eivind
Reviewed by: des
(2) Die when there is a problem opening at.allow other then it not existing.
An error other then it not existing might be a trick to somehow
circumvent system security.
Mostly Reviewed By: msmith
intentional, this behaviour is far too obnoxious given the number of
filenames such as rpc.statd we have.
Submitted by: Chris Costello [3]chris@calldei.com (bin/11303)
PR: bin/12070
Submitted by: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Specifically check that FTP_PASSIVE_MODE is set to YES, rather than
just checking if it is defined.
Discussed on: freebsd-current
two characters of $EDITOR. This allows things like "vim" and "vi -G"
(although nvi would fail...oh well).
- Avoid certain cases where the editor is passed an invalid line number.
the new -i option were missing.
Fixed style bugs in previous commit:
(1) initialisation of a local variable in its declaration.
(2) inconsistency of (1) with style of nearby code.
(3) disorder of declaration for (1).
(4) a line longer than 80 characters.
(5) bitrot in the printf() -> err() cleanups to help bloat the line in (4).
local "login" name for rcmd(3). This is particularly useful for things
like portslave and other packages with terminal server functionality
where a login can either run ppp locally or get shunted off to another
box via rlogin depending on radius authentication etc. Quite often the
local box doesn't even have accounts, so a flag such as this is needed.
Obviously this is restricted to callers with uid == 0.
and was also a bit inconsistent: leading blanks, or any double blanks
generated empty arguments, but a trailing blank did not.
PR: bin/2630, bin/10914
Submitted by: Arne Henrik Juul <arnej@imf.unit.no>
of an empty buffer... the output file wasn't readable... also warn that
we can't checksum on stdout and print out the base64 encoded version of the
md5 checksum...
Site to actually return md5 digest: web.golux.com
Verified that fetch was broken: Ken Coar <Ken.Coar@Golux.Com>
This is useful for people who want index their home directory:
$ env LOCATE_CONFIG=$HOME/.locate.rc /usr/libexec/locate.updatedb
Submitted by: Dmitry Morozovsky <marck@rinet.ru>
the magicness of 200. Cleaned up the remaining parts. Circularisation
of the list of malloc types was a kernel bug (now fixed). Interfering
with applications' definitions of pgtok is a system header bug (not
fixed).
changed from a simple list to a circular one. We compensate by only
looping until we see the first address again. Before, things would
terminate because it was limited to 200 iterations. This lead to
bogus statistics and repeating stats for memory types.
This should be merged into 3.2, as the same bug is there.
* if run by root (or root process) drop privs
* ensure output size is not infinate (net finger only)
* ensure output lines are not infinate in length (net finger only)
* do not allow finger client to run longer than 3 minutes (net finger only)
"passwordtime" is what passwd(1) has actually been using. I suspect
passwordperiod was the original intent. I can't figure-out which,
if either, BSDi uses. If anyone knows...
That doesn't work well for tapes over 4G.
I use tcopy a lot to write images of a tape to tape as tape to tape
copying is terribly slow. Slower than it should be. Quickly found out
tcopy can not rewind a file when doing copy/verify.
PR: 11386
Submitted by: David Kelly dkelly@hiwaay.net
Reviewed by: phk
o main returns int not void
o use return 0 at end of main when needed
o use braces to avoid potentially ambiguous else
o don't default to type int
o #ifdef 0 -> #if 0
Reviewed by: obrien and chuckr
(and can be both files or directories). Show white space between
"(", ")", "!" and their corresponding `expression' arguments as
expected by the expression parser inside find(1).
Prompted by: David Honig <David.Honig@idt.com> on freebsd-doc
Message-Id: <199904132055.NAA09432@justinian.Eng.idt.com>
Arguments with whitespaces are easy to fix, but in combination with
shell metachars that should not be evaluated it is very hard, probably
impossible to fix without going to a line-oriented solution.
Next time I will believe Henry Spencer when he says "this looks easy
to fix but isn't".
parameter that has space in it, both in getopt.c and in the manpage
example.
2) Fix the example in the manpage. The set(1) command is required to
return 0 (POSIX 1003.2, section 3.14.11), so you can't test for
getopt's exit status like the example did:
#! /bin/sh
set -- `getopt abo: $*`
if test $? != 0 # wrong, tests for set's exit status, which is
# always zero, no for getopt(1)'s.
Fixes PR bin/5845, which thought it was getopt's fault, but in fact
the manpage was wrong.
I also updated the example to be more useful and updated the BUGS
section.
PR: bin/5845
Updates the manpage as well.
I've rewritten the patch as it was for 2.2.7. It can probably be put
into 3.1-STABLE as well.
PR: bin/10515
Submitted by: Jens Schweikhardt <schweikh@noc.dfn.de>
numbers as chars or use bogus casts in an attempt to unmisrepresnt
them. In top, don't assume that 0xff is the only negative cpu
number when cpu numbers are (mis)represented.
time now.
For whatever reason, the kernel seems to have generated SIGIOs
previously without an initial fcntl(...,F_SETOWN), but does no longer.
This caused window(1) to wait indefinitely for input.
Also, undo rev 1.3 of wwspawn.c, it was not well-thought, and
apparently not even tested at all. The blindly (even in a nonsensical
place like the comment on top of the function) applied replacement of
vfork() by fork() totally ignored that window(1) *does* abuse the
feature of vfork() where a modification of the parent's address space
is possible (in this case, to notify the parent of an erred exec*).
Also, with vfork(), it is guaranteed that the parent is only woken up
after the exec*() happened, where the replacement by fork() made the
parent to almost always become runnable again before the child, in
which case the parent simply told `subprocess died'. Unfortunately,
working around _this_ seems to be a lot more of redesign work compared
to little gained value, so i think relying on the specifics of vfork()
is the simpler way.
Submitted by: Philipp Mergenthaler <un1i@rz.uni-karlsruhe.de>
Instead, treat the inability to retrieve a record from the server as a
match failure and let things take its course.
Part of the problem here is that NIS _is_ turned on, however the master
server is actually not an NIS server: it's an NIS+ server. And the client
is bound to an NIS+ replica server that's running in YP compat mode.
The code which tries to figure out of the user is local or NIS gets
confused by this.
compiled in default in case it isn't defined. This is needed to make
cross compilation work in some edge cases. It also makes cross
compiling on FreeBSD other BSD's easier as well.
Obtained from: NetBSD, OpenBSD (predates the split)
to "Office Location:" to disambiguate what is expected. Add a note
to the man page to indicate that the office location and office phone
fields are concatenated and printed with the heading "Office:" by
finger(1). Swap the order of the home and office phone fields in the
man page to match the order of the fields in the editor.
If any programs interact with chpass(1) and expect "Location:" instead
of "Office Location:" as the prompt, either this change will have to be
reverted or the other programs will have to be changed.
PR: docs/7533
`ld ... <fudged ${LDFLAGS}>' to invoke the linker. This gets the
flags and standard library paths right without complications.
Unfortunately, it doesn't help for the X11 library paths -- cc
only appends /aout for standard library paths.
I'm not sure why we have `mvstat -z'. `sysctl vm.zone' gives more
information. OTOH, `sysctl vm.zone' shouldn't return ASCII data,
and reporting of memory use should be integrated, at least as an
option.
since it means -s (strip), and static linkage is forced correctly
anyway. Other things in ${LDFLAGS} are still bogusly passed to ld.
This only affects the aout case.
the display wrapped around.
This decreases the default maximum number of disks shown to 2, so things
don't wrap around so easily. Also, it fixes the header display issues.
Submitted by: Bruce Evans <bde@FreeBSD.ORG>
peripheral drivers can determine where in the devstat(9) list they are
inserted.
This requires recompilation of libdevstat, systat, vmstat, rpc.rstatd, and
any ports that depend on the devstat code, since the size of the devstat
structure has changed. The devstat version number has been incremented as
well to reflect the change.
This sorts devices in the devstat list in "more interesting" to "less
interesting" order. So, for instance, da devices are now more important
than floppy drives, and so will appear before floppy drives in the default
output from systat, iostat, vmstat, etc.
The order of devices is, for now, kept in a central table in devicestat.h.
If individual drivers were able to make a meaningful decision on what
priority they should be at attach time, we could consider splitting the
priority information out into the various drivers. For now, though, they
have no way of knowing that, so it's easier to put them in an easy to find
table.
Also, move the checkversion() call in vmstat(8) to a more logical place.
Thanks to Bruce and David O'Brien for suggestions, for reviewing this, and
for putting up with the long time it has taken me to commit it. Bruce did
object somewhat to the central priority table (he would rather the
priorities be distributed in each driver), so his objection is duly noted
here.
Reviewed by: bde, obrien
only likely to happen when you have a kernel<>userland mismatch,
but it's really annoying when top dumps core and leaves the terminal
in a mangled state; it's much nicer to print nicely formatted gibberish.
