On Thu, Mar 12, 2015 at 08:42:31AM +0100, Theo Buehler wrote:
I am confused by the new documentation of HW_PERFPOLICY. Is this bound
to change? Looking at the function sysctl_hwperfpolicy() in
sys/kern/sched_bsd.c, I think the following is more accurate, although I
don't know what has to go
I am confused by the new documentation of HW_PERFPOLICY. Is this bound
to change? Looking at the function sysctl_hwperfpolicy() in
sys/kern/sched_bsd.c, I think the following is more accurate, although I
don't know what has to go wrong that the string is actually set to
`unknown'.
For
I'm progressively changing how pseudo-drivers are plugged into our
network stack with the goal to turning them MP-safe.
The diff below is a simple refactoring and should not introduce any
behavior change. It moves a bridge-specific vlan-related chunk of
code into the bridge(4) driver.
I'd like
---
ldpe.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/ldpe.c b/ldpe.c
index afba919..f643272 100644
--- a/ldpe.c
+++ b/ldpe.c
@@ -279,6 +279,7 @@ ldpe_shutdown(void)
}
close(leconf-ldp_discovery_socket);
+ close(leconf-ldp_ediscovery_socket);
Two related problems regarding mice and keyboards came to my attention
during s2k15 in Brisbane and I worked with jcs@ on solutions.
The first problem is some newer machines (such as the thinkpad x1)
have keyboard repeat or stuttering during install -- this issue only
happes on the RAMDISK
On Thu, Mar 12, 2015 at 08:20:30AM +, Jason McIntyre wrote:
i think the unknown will be a catchall for errors, and we shouldn;t
suggest to users that they can set it.
This makes sense. They actually can't set it to unknown.
so my suggestion is below. i'll commit later if no one has
Although RFC 5036 is not explicit about this, LDP should not assign
labels for BGP routes. Doing that would be very resource consuming in
some scenarios and unnecessary. The goal is generally only to establish
LSPs among all PEs in the AS since LDP is not used as an end in itself
but as a means to
Hi,
I am a pretty new user so please forgive any uninformed statements.
I just spent a few hours trying to figure out why my dmesg displays an
old kernel (May 5th), when I just compiled a new one (for recent -stable
patches). I've looked pretty much everywhere and retraced every step
until
On Fri, Mar 13, 2015 at 10:48:56AM +0900, Pascal Stumpf wrote:
On Thu, 12 Mar 2015 15:25:48 + (UTC), Christian Weisgerber wrote:
On 2015-03-12, Patrik Lundin patrik.lundin@gmail.com wrote:
===
elif [ -n $KSH_VERSION ]; then
HACKING_DIR=$(dirname ${.sh.file})
===
Hi,
I am a pretty new user so please forgive any uninformed statements.
I just spent a few hours trying to figure out why my dmesg displays an
old kernel (May 5th), when I just compiled a new one (for recent -stable
patches). I've looked pretty much everywhere and retraced every step
until
On 2015-03-12, Patrik Lundin patrik.lundin@gmail.com wrote:
===
elif [ -n $KSH_VERSION ]; then
HACKING_DIR=$(dirname ${.sh.file})
===
.sh.file and related dot variables are a ksh93 extension. I don't
think ksh88 supports this, so this is unportable even within the
ksh family. ...
On Thu, 12 Mar 2015, at 04:11 AM, Theo de Raadt wrote:
Two related problems regarding mice and keyboards came to my attention
during s2k15 in Brisbane and I worked with jcs@ on solutions.
The first problem is some newer machines (such as the thinkpad x1)
have keyboard repeat or stuttering
2015-03-11 22:30 GMT-03:00 Claudio Jeker cje...@diehard.n-r-g.com:
On Wed, Mar 11, 2015 at 04:41:08PM -0300, Renato Westphal wrote:
In the name of simplicity, remove the interface FSM that was inherited
from ospfd. In ldpd interfaces are just up or down, so keeping a FSM
for that is an
2015-03-11 22:18 GMT-03:00 Claudio Jeker cje...@diehard.n-r-g.com:
On Wed, Mar 11, 2015 at 04:41:05PM -0300, Renato Westphal wrote:
Although RFC 5036 is not explicit about this, LDP should not assign
labels for BGP routes. Doing that would be very resource consuming in
some scenarios and
On Sun, Feb 15, 2015 at 09:00:27PM -0500, Ted Unangst wrote:
ksh (and sh) have a version string embedded in them:
@(#)PD KSH v5.2.14 99/07/13.2
This is clearly a lie. We've added, removed, and fixed bugs and features since
then. I first noticed the lie in the man page, then saw that it's
15 matches
Mail list logo
