| Age | Commit message (Collapse) | Author |
|---|
|
FT232R chip to interface the receiver (instead of the NetCologne
chip used on older models). Only the DCF77 and HBG receivers are
supported.
A sidenote: Gude ADS not only provides me with receivers and
documentation, but as a result of my feedback on their older receivers
the new ones now have proper USB product IDs to distinguish between
DCF77, HBG, and MSF.
|
|
- new sentence, new line
|
|
Correct misnaming in STANDARDS section
ok brad@ otto@
|
|
contains a '#' character. Make it also accept the \$ PS1 sequence
(which is supposed to automagically be $ or # depending on the user
running the shell) unless ksh has been started in sh-compatibility
mode.
pointed out by millert@ when I asked why my SUDO_PS1 was not being
honoured; ok millert@
|
|
|
|
Do not treat the first protocol 2 authentication attempt as
a failure IFF it is for method "none".
Makes MaxAuthTries' user-visible behaviour identical for
protocol 1 vs 2.
ok dtucker@
|
|
|
|
|
|
actually be used to access trap vectors.
|
|
|
|
|
|
we pretend that ssm is mainbus. Perhaps I'l turn it into a real bus driver
later.
|
|
ok thib@
|
|
ok jsg@
|
|
|
|
paths using ftp(1). Thanks ajacoutot and jmc for suggestions.
ok ajacoutot jmc, no objection deraadt
|
|
|
|
port to be set in the config file instead of using HTTP_DEFAULT_PORT
in all cases. Prevent a segfault that would happen when the SSL
connection from the proxy fails.
Problem found and analyzed by Mischa Diehm; fix by me.
|
|
|
|
nasty commands dependencies.
|
|
and simplify file: parsing scheme (trying it with file:, then without is
a bit stupid once we have the pieces to put it back together directly).
Drop the restriction on urls from the man page, no need to finish stuff with /.
|
|
|
|
|
|
|
|
that we can attach the state to, make sure to not overwrite the state key
pointer in the state that was just set to the existing state key with the
state key that was supplied with the state and just free'd (well, pool_put'd).
by the time we clean up the state and try to follow it to RB_REMOVE etc
we'd follow that garbage pointer to either an unrelated state key or the old
state key still sitting unused in the pool.
should fix the RB_REMOVE panics some people have been seeing.
"clearly ok, please commit" ryan
|
|
|
|
|
|
this permits fetching packages from thttpd
ok espie
|
|
(radeon and intel)
tested by a few (as part of the updates)
|
|
>Update the radeondrm driver to be level with drm git.
>
>adds:
>
>- support for RS400 chips
>- some cleanup of a few things
>- fixes a hard lockup for r3-500 cards.
>
>Tested by a few
|
|
changes:
- Support for intel 4 series chipsets (i'll do any relavent agp bits for
these as soon as i grab the datasheet and find a testcase)
- fix scheduled buffer swaps on non 965 chipsets
- major reorder, dedup and general cleanup of register definition and
the header file
Tested by a few, no regressions
|
|
adds:
- support for RS400 chips
- some cleanup of a few things
- fixes a hard lockup for r3-500 cards.
Tested by a few
|
|
report and testing by david@; ok millert@ jaredy@
|
|
ok deraadt@
|
|
ok henning
|
|
when we first do a pcb lookup and we have a pointer to a pf state key
in the mbuf header, store the state key pointer in the pcb and a pointer
to the pcb we just found in the state key. when either the state key
or the pcb is removed, clear the pointers.
on subsequent packets inbound we can skip the pcb lookup and just use the
pointer from the state key.
on subsequent packets outbound we can skip the state key lookup and use
the pointer from the pcb.
about 8% speedup with 100 concurrent tcp sessions, should help much more
with more tcp sessions.
ok markus ryan
|
|
|
|
OK deraadt
|
|
identical to the one above it.
OK deraadt
|
|
ok deraadt@
|
|
ok marco@
|
|
ok deraadt@
|
|
|
|
|
|
1. When checking if the pagedaemon should be awakened and to see how
much work it should do, consider the buffer cache deficit
(how much pages the buffer cache can eat max vs. how much it has
now) as pages that are not free. They are actually still usable by
the allocator, but the presure on the pagedaemon is increased when
we starting to chew into the memory that the buffer cache wants to
use.
2. Remove the stupid 512kB limit of how much memory should be our
free target. That maybe made sense on 68k, but on modern systems
512k is just a joke. Keep it at 3% of physical memory just like
it was meant to be.
3. When doing allocations for the pagedaemon, always let it use the
reserve. the whole UVM_OBJ_IS_KERN_OBJECT is silly and doesn't
work in most cases anyway. We still don't have a reserve for
the pagedaemon in the km_page allocator, but this seems to help
enough. (yes, there are still bad cases in that code and the comment
is only half-true, the whole section needs a massage, but that will
happen later, this diff only touches pagedaemon parts)
Testing by many, prodded by theo.
|
|
the native ubsa device, the patch notifies when it finds such a kind of
device.
ok jsg@
|
|
ok deraadt@
|
|
enabled, delay the fork until after replies for any -R forwards have
been seen. Allows for robust detection of -R forward failure when
using -f (similar to bz#92); ok dtucker@
|
|
|
|
Check whether client has exceeded MaxAuthTries before running
an authentication method and skip it if they have, previously it
would always allow one try (for "none" auth).
Preincrement failure count before post-auth test - previously this
checked and postincremented, also to allow one "none" try.
Together, these two changes always count the "none" auth method
which could be skipped by a malicious client (e.g. an SSH worm)
to get an extra attempt at a real auth method. They also make
MaxAuthTries=0 a useful way to block users entirely (esp. in a
sshd_config Match block).
Also, move sending of any preauth banner from "none" auth method
to the first call to input_userauth_request(), so worms that skip
the "none" method get to see it too.
|
