Fixes bug introduced in rev 1.15, and reported in PR 39710 from Juan RP.
Don't display various warnings in delete if -q.
Suggested in PR 39710.
Add some sanity enforcing abort()s.
bmake_malloc and friends. Implement them via macros for the native case
and provide fallback implementations otherwise. Avoid polluting the
namespace by not defining enomem globally. Don't bother to provide
strdup and strndup, they were only used for the estrdup and estrndup
comapt code.
This addresses the presence of emalloc in system libraries on A/UX and
resulted strange issues as reported by Timothy E. Larson.
Major changes are:
- better detection of double applied patches
- rejects remain unified diffs for unified patches
- far less limitations, e.g. patch lines may be arbitrary long
This addresses PR standards/11220 by changing patch -b behavior to be
POSIX compliant. Old behavior can be obtained using --suffix, which
works since NetBSD 1.4. pkgsrc has been adjusted accordingly.
i386 "unsigned long x = 0x800000000UL;" passed lint and gcc complains
(rightfully). Validate quad as well to allow using a potentially larger
type to store the value.
first year that NetBSD 5.0 is out)
- add release date of NetBSD 4.0
XXX There are several UK "Bank Holidays" in calendar.holiday. Could
somebody update those and give an indication of when they are, please?
(I found a script which tries to figure out the byteorder of a box
by "od -An | grep", but it is POSIX anyway.)
There is a little behavioural change: The whitespace without any arguments
is like "-to2" now; before it was custom. It's not worse imho.
1. Don't add changelog and other implementation specific nvi files because
this have changed from 1.79 and are probably not relevant in 1.81
2. Put back virecover.
3. Descend regularly to subdirs instead of Makefile hacks
4. Use USD.doc stuff from the 1.81 docs except for vi.ref which has
unfortunately been converted to texinfo. For that, we preserve
the original documents because we want to still be able to make
section 13 (building texinfo is not acceptable because it will not
have the same look and feel as the rest of the book)
5. Since the texinfo reference is probably better maintained, build
that too as a texinfo document.
* define NOfoo before .including <bsd.own.mk> or anything else that
might (indirectly) .include it, not after.
* defining MKfoo=no isn't what Makefiles are supposed to do
(yes, both mistakes were present :)
in "vmstat -s" output when run on the active kernel.
The reason we can't easily provide these values out of a crash
dump, is that these fields are no longer proper members of
struct uvmexp, but rather are estimated by and dependent on
the currently active page replacement policy in the kernel.
temprorary directory. Previously, fputs was used without checking the
return value, leading to silent truncation when the temporary
filesystem was full (such as can easily happen when migrating to
tmpfs).
1. long a; int i; a = i * i;
suggests casting i to long, so that we gain precision in the multiplication.
2. warns about magnitude comparisons in enums.
3. warns about possible sign extension issues when integer types become widened.
rare and skipping over normal characters with strcspn is therefore
faster. Further simplify logic by always setting newline and precompute
the size of the string.
OK christos@
Simplify the change (adding -d<depth>) that broke it by noting that
-d0 is supposed to be the same as -s.
Calling fts_set(fts,p,FTS_SKIP) here is also pointless.
if we're reducing a rule that has an empty
right hand side and the yacc stackpointer is pointing at the very
end of the allocated stack, we end up accessing the stack out of
bounds by the implicit $$ = $1 action
do it a bit differently than in Openbsd: avoid pulling in <string.h>
because this is not compatible with wacky namespace games we do in libc
-use AUMODE_PLAY_ALL, from Sergey Svishchev -- this might cause
stuttering if the write to audio can't keep up, but it avoids pauses
if the audio buffer drains out on stop/resume
-The timeout for the raw SCSI command to read audio data
was too small, causing complete failure for me.
-Since the itimer can't do faster than HZ, a too small buffer doesn't
work. Try to calculate a sensible buffer size.
-While it makes sense to deliver data a bit faster than necessary,
it should be not that much that the blocking in the signal handler
hurts interactive response. Allow for 50ms.
-Comment out a sched_yield() in the signal handler - this doesn't
look right.
This is far from being perfect, but it makes digital mode usable for me.
And for Jeremy C. Reed, the author of PR bin/38493.
There are some formatting errors, someone with mandoc clue please correct.
Also, this man page assumes familiarity with the concepts uesd.
While fully describing these concepts is outside the scope of this
man page, a pointer to such a description should be included.
Someone who knows of such a description, please provide pointers.
Finally, we should have a companion tool to create the peaces needed
to use this tool: set up a CA, create a certificate chain and a
private key/certificate pair for signing.
(the utmpentry.c code), specifically with respect to who owns them and
when to free them. Now they're owned by utmpentry.c, only. Abolish the
freeutentries() function, which was the wrong abstraction; add instead
endutentries(), which flushes out the internally managed memory.
Update callers as necessary. Some (e.g. talkd) had been leaking memory;
others (e.g. syslogd) had been accidentally freeing and reloading utmp
more often than necessary. There are a couple untidy bits in users and
rwhod that someone should look after sometime, maybe.
Fixes PR bin/35131, which was about talkd's memory leak.
previous versions, when we know we're working on an old file. That way,
a -current config(1) works on a 4.0 source tree (or older) without
warning. Pointed out by Christos Zoulas.
XXX We should set up way to note compatibility code we can get rid of
XXX the day we choose to bump CONFIG_MINVERSION.
o Make "prop dictionary" fit in the "Type" coloumn
o Ensure that fields don't run into each other (adds a space between fields)
o Ensure that a Limit of >100000K fits in the field width
The rule is, if you change scan.l or gram.y, you bump the config(5)
version. If you implement the changes under sys/conf/files or affiliate,
you bump the required version in sys/conf/files or in an appropriate place
to minimise annoyance. If the changes makes new config(1) incompatible
with a previous version of config(5), embed it in config(1) using the
CONFIG_MINVERSION definition along with CONFIG_VERSION.
This has been in the tree for what, 3 years now? It's even documented...
ones, mostly network pseudo interfaces) and those which use autoconf
to attach instances dynamically, or to attach child devices.
Use a new keyword "defpseudodev" for the latter.
Issue a warning if interface attributes are used with "old" pseudodevs,
but let it work as before for now. This will be removed soon.
approved by cube
XXX docs are left out for the moment
the recover script is also left out, but provided by the older vi
The src/usr.bin/nvi directory is not descended into yet, but is otherwise
functional
in the format string) so that we can "or" it with the bits in the
formats variable. This fixes the missing " -> " in front of the real
path (when you use %SR).
Also, the ?: needs another space.
PKCS7 signatures. This was written by lha@ and discussed on
tech-security. I've slightly cleaned up the program and man page.
Contrary to the original version, this doesn't provide a default trust
anchor.
display state, i.e., hidden/exposed tags or threads. This fixes at
least two problems:
- If the current message is a duplicate that is deleted by the "deldups"
command, then the dot was invalid making all messages appear to have
been deleted. It is now set to the surviving duplicate message.
- If the current message is tagged, the "hidetags" command would leave
the dot invalid and the dislay would reset it at the top of the
current screen. It is now set the the first untagged (and
not deleted) message after the previous (tagged) dot message.
From Anon Ymous
filenames whether "-h" option (suppress filenames when multiple files
are searched) is speficied or not.
Make zgrep "-h" option actually works with using "-H" option only
when "-h" is not specified.
dholland