| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
in case the parent process was started with a dangling child. This style
ensures any potential parent:child interlock isn't disrupted due to the
"wrong" child being waited on first. Then the other other childs can safely
zombie.
ok millert jca brynet
|
|
|
|
| |
ok brynet@
|
|
|
|
| |
Alternative diff by Tim (trondd ! kagu-tsuchi . com), ok tedu@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Just NULL is not good practise as NULL is theoretically allowed to
be an integer rather than a pointer.
Use (char *)NULL consistently instead of scattering a few (char *)0
and (void *)NULL into the mix.
Prompted by and probably ok deraadt@ millert@ kettenis@
Definitely ok mestre@ ratchov@
|
| |
|
|
|
|
|
| |
makes no promises about compatibility nor the lack of compatibility.
suggestion & diff from micheal reed
|
| |
|
|
|
|
|
| |
the need for getpw. Not sure if I see ways to improve this program.
ok doug
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
this hardware alive is becoming increasingly difficult, and I should heed the
message sent by the three disks which have died on me over the last few days.
Noone sane will mourn these ports anyway. So long, and thanks for the fish.
|
|
|
|
| |
OK deraadt@
|
| |
|
|
|
|
| |
cannot be deduced from the dmesg output. Suggested by miod@, ok deraadt@
|
|
|
|
|
| |
asprintf(3) and `ifp' is opened via popen(3), but not closed.
from zinovik
|
| |
|
|
|
|
| |
used.
|
|
|
|
|
|
|
|
|
| |
to aid ACPI development. Output files are base64 encoded in the
report.
Add a -E flag to decode files from a report to the current directory.
Requested by deraadt, "Sweet!" marco, "Looks good to me." pirofti
|
|
|
|
|
|
| |
were categorized as "pending" and the report was never acked.
Reported by RD Thrush and bernd@, OK miod
|
|
|
|
|
|
| |
users.
Idea okayed by art and deraadt, feedback from jmc.
|
|
|
|
|
| |
(slight change made to check argc == 0)
from Daniel Dickman
|
|
|
|
|
| |
- sync architectures list with reality and fix a few names
ok theo
|
|
|
|
|
|
|
|
| |
no binary change
found by Daniel Dickman <didickman at gmail.com>
ok ray@
|
|
|
|
|
|
|
|
|
|
| |
NUL at the end of a string into the mail. Discovered by dasn.
Move newline printing into outer loop, prevents multiple newlines
from appearing if there are multiple comments in a line. Discovered
by okan.
OK okan.
|
|
|
|
|
|
|
|
|
|
|
| |
#include <bleh.h> in diffs:
- Only match <> comments from the template. No other text surrounded
by angle brackets is deleted.
- Simplify code by using C strings. We no longer handle binary
data, but I don't think binary data belongs in a bug report anyway.
- Remove dmesg and header comment checks.
"That's a nice approach." deraadt, "seems ok for me" chl.
|
|
|
|
|
|
|
|
| |
- Move <> comments in template to an array, for easier reference later.
- Rename "comment" variable to avoid shadowing.
- Change some <> comments to SENDBUG comments.
OK chl@
|
|
|
|
|
|
|
|
| |
temporarily restoring default behaviour. This is not 100% ideal.
But this fixes editor handling in mail... bah, it is really unfortunate
that got broken
- refactor the restoration code as well, to make it simpler
ok ray
|
|
|
|
| |
Discovered and tested by deanna.
|
| |
|
|
|
|
|
|
| |
worsens the problem.
cloder@ and deraadt@ agree.
|
|
|
|
|
|
| |
has a non-zero exit status, just return the exit status on success.
Hard errors still return -1. If the editor is killed, return -1
and set EINTR.
|
|
|
|
| |
Specifically, -V.
|
|
|
|
| |
OK jaredy@ and moritz@.
|
| |
|
|
|
|
| |
EAGAIN.
|
|
|
|
| |
``Slacker! We'll burn your hands if you don't get going!'' deraadt@
|
| |
|
| |
|
| |
|
|
|
|
| |
by millert@.
|
| |
|
| |
|
|
|
|
| |
``Come on, take some risks'' deraadt@.
|
|
|
|
| |
OK deraadt@ and millert@.
|
|
|
|
| |
OK millert@.
|
|
|
|
|
|
|
|
| |
of '&', but gecos fields are usually short and most do not have '&'
so the impact should be minimal. In return we get clearer and safer
code.
OK moritz@.
|
| |
|
|
|
|
|
|
|
| |
when gecos field contains multiple '&' characters with
other characters inbetween.
With and OK ray@
|
| |
|
|
|
|
|
|
| |
WIFCONTINUED can't happen in this case.
OK deraadt@.
|