| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: Ulrich Spörlein
|
|
|
|
|
|
|
|
|
| |
in the buffer. This isn't exactly the patch that Stephen submitted, but
is based on one of his suggestions.
PR: 93841
Submitted by: Stephen Montgomery-Smith <stephen@math.missouri.edu>
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
- signed/unsigned conform.
- Better initialization of nlist[]. I think we should have
something like NLIST_NULL instead of the current (ugly)
form...
|
|
|
|
| |
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Ensure that the buffer ends with "\n\0" to avoid special cases
and allow the use of strtol().
- Use strvisx() on each complete line instead of character by
character.
Submitted by: bde
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
full, since that line is almost always incomplete. Make the parsing
of <%d> lines more strict.
Also simplify the logic a little:
- Start off by making the buffer linear so that we don't have to
deal with it wrapping around (suggested by bde).
- Process line by line rather than byte at a time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with a new implementation that has a mostly reentrant "addchar"
routine, supports multiple message buffers in the kernel, and hides
the implementation details from callers.
The new code uses a kind of sequence number to represend the current
read and write positions in the buffer. This approach (suggested
mainly by bde) permits the read and write pointers to be maintained
separately, which reduces the number of atomic operations that are
required. The "mostly reentrant" above refers to the way that while
it is now always safe to have any number of concurrent writers,
readers could see the message buffer after a writer has advanced
the pointers but before it has witten the new character.
Discussed on: freebsd-arch
|
| |
|
| |
|
| |
|
|
|
|
| |
pollution in <kvm.h>.
|
| |
|
|
|
|
|
| |
o Use ANSI function definitions
o mark usage() as __dead2
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
|
|
|
|
| |
Yes, this isn't really the right place for it. No, it really can't
remain undocumented.
|
|
|
|
|
| |
Submitted by: Ashley Penney <ashp@unloved.org>
MFC after: 3 days
|
| |
|
|
|
|
| |
Reviewed by: ru
|
|
|
|
| |
kernel, and remove setgid kmem, which is not needed any more.
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
|
|
|
| |
Requested by: rwatson
|
|
|
|
| |
PR: bin/25337
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: alex, asmodai, billf
|
| |
|
|
|
|
|
|
| |
kernel+userland when that is the case.
PR: bin/7414
|
| |
|
| |
|
|
|
|
| |
posix standard on the topic.
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed the following bugs:
- the buffer was reprinted endlessly when msg.bufx == 0 and (for a
different reason) when msg.bufx == 1.
- the last byte of the buffer wasn't printed except in the the infinite
loop cases.
- the comment about walking the buffer didn't match the (correct) code.
- minor -Wall and style bugs.
Not fixed:
- excessive newline processing which hid the non-printing of the last
byte of the buffer.
|
|
|
|
| |
Submitted by: Julian H Stacey
|
| |
|
| |
|
| |
|
|
|
|
|
| |
in `fastboot'/`fasthalt' in which the interpreter would hang around
after `reboot' or `halt' is run, causing an irritating ``Killed'' message.
|
|
Note: XNSrouted and routed NOT imported here, they shall be imported with
usr.sbin.
|