| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
|
|
|
| |
Obtained from: OpenBSD
|
| |
|
|
|
|
|
|
| |
vinvalbuf().
Submitted by: Chad David <davidc@acns.ab.ca>
|
|
|
|
|
|
| |
So lets stop that nonsense and allow `w!' to do something useful.
Submitted by: green
|
| |
|
|
|
|
|
|
| |
be MFC'd)
Submitted by: Dima Dorfman <dima@unixfreak.org>
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
| |
added in the previous commit; this variable is already incremented
in the previous `if' condition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Despite of a few cosmetic things like adding ``irritating silly
parentheses'' around all return values, this mainly improves FDC reset
handling by no longer gratuitously resetting the FDC all the time
(which causes it to lose the notion of the current track) but only in
case of errors, and it sanitizes the block and offset calculations in
fdstrategy() and fdstate(). Some additional cleanup added by me, in
particular the large switch in fdstate() now always uses return to
break out, and no branch falls off the end of the switch statement
anymore. Per Bruce's suggestion, removed M_NOWAIT from the malloc()s
to simplify things.
Submitted by: bde (mostly)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
until a 20ms select(2) timeout occurs, but if there is a continuous
stream of movement events, button events can be delayed indefinitely
because the select never has to wait long enough for a timeout.
The delay and mouse event reordering that result are very noticable
and sometimes quite frustrating when dragging windows etc. in X.
Add a simple mechanism that avoids this re-ordering. While a button
event is deferred, we discard up to 3 movement events to allow for
mouse jitter. If more movement events occur, then we immediately
timeout the deferred button event and let the movement proceed.
This change only affects the 3-button emulation case.
|
| |
|
|
|
|
|
|
|
| |
changed, so independant entities backing up the same thing to different
media can be made not to trip over each other.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
successful.
This part was lacked during merge.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
Previously, I had the MODE_1000 bit in the global config register set
unconditionally, which was wrong: we have to turn it off if we have
a 10/100 link. This is now handled in the nge_miibus_statchg() routine.
Discovered by: Nathan Binkert <binkertn@eecs.umich.edu>
(Note: this commit is being done from JFK airport. :P )
|
| |
|
| |
|
|
|
|
| |
BDE'd by: BDE
|
|
|
|
|
|
| |
takes from /usr/include. I cannot check them on alpha.. (will try beast)
Briefly looked at by: Warner Losh <imp@harmony.village.org>
|
| |
|
|
|
|
| |
driver (nmdm(4)).
|
|
|
|
| |
(I've been using it with vmware for over a year now.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generation scheme. Users may now select between the currently used
OpenBSD algorithm and the older random positive increment method.
While the OpenBSD algorithm is more secure, it also breaks TIME_WAIT
handling; this is causing trouble for an increasing number of folks.
To switch between generation schemes, one sets the sysctl
net.inet.tcp.tcp_seq_genscheme. 0 = random positive increments,
1 = the OpenBSD algorithm. 1 is still the default.
Once a secure _and_ compatible algorithm is implemented, this sysctl
will be removed.
Reviewed by: jlemon
Tested by: numerous subscribers of -net
|
| |
|
|
|
|
|
| |
is generated from NOTES. Also correct a bogus path;
<machine>/conf/options.<machine> doesn't exist.
|
|
|
|
| |
to reflect recent changes in the code.
|
|
|
|
|
| |
is gone, and it's not coming back, and the whole driver needed to be
rethrought to deal with a major chicken-and-egg consideration.
|
|
|
|
|
| |
is gone, and it's not coming back, and the whole driver needed to be
rethrought to deal with a major chicken-and-egg consideration.
|
| |
|
|
|
|
|
|
|
|
| |
tries to free uninitialized mbuf.
This was my mistake during recent KAME merge. This part is for
*BSD other than FreeBSD.
Submitted by: Alexander N. Kabaev <ak03@gte.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The original code was certainly broken; it knows that whereto is
to be used for a sockaddr_in, so it should be declared as such.
To support multiple protocols, there is also a sockaddr_storage
struct that can be used; I don't think struct sockaddr is supposed
to be used anywhere other than for casts and pointers.
Submitted by: Ian Dowse <iedowse@maths.tcd.ie>
MFC after: 3 weeks
|
|
|
|
| |
to consistently use <varname></varname>. No content changes.
|
|
|
|
| |
acpi_cpu_speed_sysctl().
|
|
|
|
| |
couple more sysctl's, add a section on mount options.
|
|
|
|
| |
from working right in 2.9.
|
|
|
|
| |
open CCP with no algorithm.
|
|
|
|
|
| |
are not coming back any time soon. Implement a new 'acpi_cpu' driver
with support for CPU throttling and power policies.
|
| |
|
| |
|
|
|
|
| |
not mandatory.
|
|
|
|
| |
directly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This one is strange and goes against my rusty compiler knowledge.
The global declaration
struct sockaddr whereto;
produces for both i386 && alpha:
.comm whereto,16,1
which means common storage, byte aligned. Ahem. I though structs
were supposed to be ALDOUBLE always? I mean, w/o pragma packed?
Later on, this address is coerced to:
to = (struct sockaddr_in *)&whereto;
Up until now, we've been fine on alpha because the address
just ended up aligned to a 4 byte boundary. Lately, though,
it end up as:
0000000120027b0f B whereto
And, tra la, you get unaligned access faults. The solution I picked, in
lieu of understanding what the compiler was doing, is to put whereto
as a union of a sockaddr and sockaddr_in. That's more formally correct
if somewhat awkward looking.
|
|
|
|
|
|
|
|
| |
directory, defaulting to /tmp.
PR: bin/16924
Reviewed by: dd
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
perform a key change, *and* our sequence numbers have wrapped,
ensure that the number of key changes is calculated correctly.
The previous code counted down from a negative number to zero,
re-encrypting the current key on each iteration - this took some
time and strangely enough got the answer wrong !!!
Fix a(nother) spelling mistake while I'm there.
|
|
|
|
|
|
|
|
| |
Monitor the system power profile, and use _SCP to adjust thermal zones
accordingly.
Simplify the behaviour of the timeout routine, and add some temporary
debugging.
|
|
|
|
| |
is available and "economy" when it is not.
|
| |
|