| Age | Commit message (Collapse) | Author |
|---|
|
patches from Sevan Janiyan <venture37 at geeklan dot co dot uk>;
verified using minnie.tuhs.org/cgi-bin/utree.pl
|
|
don't help improve code because they block core dumps and there reduce
inspection of bugs thus work on fixes. Secondly, these handlers are
*stdio signal races* so they can produce different coredumps deep inside
stdio.
|
|
ok mglocker
|
|
correctly - logically complete that now by removing MLINKS from base;
authors need only to ensure there is an entry in NAME for any function/
util being added. MLINKS will still work, and remain for perl to ease
upgrades;
ok nicm (curses) bcook (ssl)
ok schwarze, who provided a lot of feedback and assistance
ok tb natano jung
|
|
|
|
|
|
|
|
malloc, calloc, realloc*
ok krw millert
|
|
Based on diff from Manuel Giraud (manuel (at) ledu-giraud.fr) Thanks!
|
|
Correct old style entries so nothing has to be done for the admin.
diff from Manuel Giraud (manuel (at) ledu-giraud.fr) Thanks!
|
|
What's worse, the tzfile.h that gets installed is over 20 years old
and doesn't match the real tzfile.h in libc/time. This makes the
tree safe for /usr/include/tzfile.h removal. The TM_YEAR_BASE
define has been moved to time.h temporarily until its usage is
replaced by 1900 in the tree. Actual removal of tzfile.h is pending
a ports build. Based on a diff from deraadt@
|
|
delete <sys/param.h> if now possible
ok guenther
|
|
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
like, oh, strchr() and prototypes for read() and write().
Mark quit() as both __dead and printf-like, and dumpabort() as __dead.
ok krw@
|
|
From: Maximilian Fillinger
|
|
the new shiny -U switch)
dumpdates part originating from, and discussed with, Maximilian Fillinger
seems reasonable to krw@, "get it in" deraadt@
|
|
sectors. This ensures that the requested data, and all the requested
data, is actually read from the device.
Should have no effect on 512-byte sector devices, but makes dump work
on 4096-byte sector devices.
Problem noted by and fix tested by David Vasek.
|
|
* Move all off_t variables that don't look like file sizes to int64_t.
* Switch blockswritten to int64_t, so it won't wrap at 2TB.
* Same for blocksthisvol (from deraadt@).
* Switch xferrate (from tedu@) and blocksperfile from long to uint64_t.
* Since blocksperfile can be set with -B, move numarg() from long
to long long and don't mark small integer constant arguments as long.
ok deraadt@, tedu@
|
|
them 'blocks' not 'sectors'.
|
|
|
|
|
|
required (from NetBSD).
ok beck@, krw@ and sthen@
|
|
actual disk sector size and not DEV_BSIZE. The sector size must be
obtained via the disklabel. Larger i/o's must be multiple sectors,
so when retrying with a smaller size shrink the attempt by one sector
and not DEV_BSIZE.
Of course if your d_secsize is DEV_BSIZE, this will all be a no-op.
This does not make non-512-byte sectors work, but puts in place the
logic to get and use the disklabel info. Which makes the next diffs
bite sized and focused.
ok guenther@
|
|
favour of DEV_BSIZE. No-op on 512-byte sector devices.
|
|
subsequent diffs.
|
|
p[read|write]. Makes the code much clearer by eliminating extra error
checking and verbiage.
No intentional functional change.
Tweaks by and ok guenther@
|
|
Careful second audit by millert
|
|
|
|
(u_int64_t) instead of (daddr_t) when casting a variable in an
expression passed to DL_SETDSIZE().
Change a variable counting open files from daddr_t to int64_t.
ok deraadt@ with the tweak to fix that pesky expression.
|
|
test period; i think 3 years ago the last bugs fell out.
ok otto beck others
|
|
|
|
|
|
|
|
|
|
disabling dumping their contents.
input and ok otto@ millert@
man page bits input and ok jmc@
|
|
|
|
local one
- replace a few magic numbers with the appropriate constants
ok millert@ (pre-lock)
|
|
|
|
ok millert
|
|
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
|
|
|
|
initially from tobias@, and I removed an unused struct too
ok moritz@ tobias@
|
|
|
|
based scheme when it makes no sense: a weekly schedule does not
benefit from it. ok mbalmer@ jmc@ ray@
|
|
OK joris@, otto@
|
|
|
|
and other reports about dump accessing wrong blocks; ok beck@ deraadt@
|
|
|
|
With help from otto@
|
