| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
so also remove mention of it in the comments.
|
|
|
|
|
|
|
| |
with a function which does the rm/mknod in one step, eliminating the
gratuitous device node removal behavior of before.
Reviewed by: bde
|
| |
|
|
|
|
|
|
|
|
| |
self-sufficient again. This is a quick fix that should
really be remedied by removing all of the gratuitous changes
made in revision 1.20.
PR: 5351
|
|
|
|
|
|
|
|
|
|
|
| |
interrupted with a SIGALRM. In fact, select() sets the
passed time to zero, making the previous implementation
terminate always after 1/10th of a second !
Also, deal with someone changing the clock while we're
sleeping (and restart the whole sleep).
Dangers pointed out by: Theo de Raadt <deraadt@cvs.openbsd.org>
|
| |
|
| |
|
| |
|
|
|
|
| |
Look in the cpu_feature (CPUID output) to see if we have it.
|
|
|
|
|
|
| |
commit.
Pointed out by: bde
|
| |
|
|
|
|
| |
got a better version.
|
| |
|
|
|
|
|
| |
also cope with some drives that return funny values.
The correct fix will come in a few days.
|
|
|
|
|
|
| |
initializing it for the (usual) (siocniobase != 0) case, but
siocnopen() doesn't initialize it if the latch registers already
have the correct values.
|
|
|
|
|
|
|
| |
have hardware tab support.
PR: 5386
Submitted by: Kevin Day <toasty@dragondata.com>
|
| |
|
|
|
|
|
|
| |
necessary to call it when the tty layer's output state has not been
changed, but siostop() sometimes changes the TS_BUSY state and then
calls comstart() mainly for its side effect of calling ttwwakeup().
|
|
|
|
|
|
|
|
|
|
|
| |
need to do it directly, since ttwwakeup() is always called just before
returning from rpstart(). The brokenness was waking up the wrong address
after clearing TS_SO_OLOWAT. It's not clear how processes waiting for
output to drain below low water ever got woken up.
Found by: when I fixed longstanding warts in output watermark
handling, this was the only driver that knew too much
(anything) about the watermarks
|
|
|
|
|
|
| |
that worked around them for the CLI devtab listing.
Print the `conflicts' flag in the CLI devtab listing.
|
|
|
|
|
|
| |
for field widths being 2 larger than specified for "%<number>p". Only
printing of null pointers is "wrong" now (it is actually "right", but
inconsistent with printf(3)).
|
|
|
|
| |
Complain to LogERROR if we have internal inconsistency (not LogDEBUG).
|
|
|
|
|
| |
blocked in the output filter. If so, proceed with the
dial despite dropping the packet.
|
|
|
|
|
|
|
| |
When CCP is originally negotiated, the only thing we can be
sure about is that we've started adding data to the inflate
dictionary either before or at the same time as the peer. This
is ok, 'cos DEFLATE is a `sliding window' compressor.
|
|
|
|
|
|
|
|
|
| |
really used any features from <sys/malloc.h> since it was "blasted
from the past" in rev.1.15, and most .c files did not depend on
the namespace pollution (others have been fixed). The mbuf allocation
control values M_DONTWAIT and M_WAIT were just defined in terms of
the malloc control values M_NOWAIT and M_WAITOK. The mbuf values
are now defined directly.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
here, but kmem_malloc() is used and it takes the same "flags" as
malloc().
Use the mbuf allocation "flags" M_WAIT and M_DONTWAIT consistently.
There is really only one boolean flag, M_DONTWAIT, but the "flags"
were always treated as enum-like values, except in some places here
where the values are tacitly converted to boolean flags. Treat
them as enum-like values everywhere, except where we tacitly assume
that there are only two values in order to convert them to the
corresponding two kmem_malloc() "flags".
|
|
|
|
| |
at IRQ 5).
|
|
|
|
|
| |
PR: 5119
Discussed with: Bruce Evans <bde@zeta.org.au>
|
| |
|
|
|
|
|
| |
PR: 3460
Pointed out by: hoek@FreeBSD.org
|
|
|
|
|
| |
PR: 5178
Submitted by: Evan Champion <evanc@synapse.net>
|
|
|
|
|
|
|
| |
to be given to ldconfig(8).
PR: 5178
Submitted by: Evan Champion <evanc@synapse.net>
|
|
|
|
|
| |
PR: 5374
Submitted by: Studded <Studded@dal.net>
|
| |
|
|
|
|
| |
to just open it as uid 0 under OpenBSD.
|
|
|
|
|
| |
PR: 5373
Submitted by: Matthew Hunt <mph@pobox.com>
|
|
|
|
|
| |
PR: 5216
Submitted by: Masahiro Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>
|
|
|
|
| |
Reviewed by: nate
|
|
|
|
|
|
| |
Show the IP range (if specified) in "show ipcp".
Close unused descriptors 0 and 2 in interactive mode.
Pass (size_t *) rather than (int *) to sysctl().
|
|
|
|
|
|
|
|
| |
Don't read(fd, buffer, 0) and think ppp has closed the
connection when `buffer' is full, instead, flush most of
buffer to the terminal and read() for a reasonable length.
This fixes "show route" when there's more than 2k of
routing output.
|
| |
|
|
|
|
|
| |
our chat script.
You can now even run chat(8) - see ppp.conf.sample.
|
|
|
|
| |
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
|
|
|
|
|
|
| |
.Fx 2.2.1
.Fx 2.2.2
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
|
|
|
|
| |
$ gzip `perl -e 'for(1..10240){ print "a"}'`
|
|
|
|
|
|
| |
used, and caused a reference to an uninitialised variable (state).
I think I've fixed it now, but since nothing in the tree seems to use it,
I'm not sure.
|
| |
|
|
|
|
|
|
| |
commented about at length in the PR audit trail.
PR: 2412
|
|
|
|
| |
Submitted by: bde
|