save-entropy

Since a few days, I receive this in /var/mail/root Any idea? Olivier From [EMAIL PROTECTED] Thu Jun 15 11:11:00 2006 Return-Path: [EMAIL PROTECTED] Received: from xxx.be (localhost [127.0.0.1]) by finalcut.be (8.13.3/8.13.3) with ESMTP id k5F9B0Pu051577 for [EMAIL PROTECTED]; Thu, 15 Jun

RE: save-entropy

Since a few days, I receive this in /var/mail/root Any idea? Olivier From [EMAIL PROTECTED] Thu Jun 15 11:11:00 2006 Return-Path: [EMAIL PROTECTED] Received: from xxx.be (localhost [127.0.0.1]) by finalcut.be (8.13.3/8.13.3) with ESMTP id k5F9B0Pu051577 for [EMAIL PROTECTED];

Re: save-entropy

freebsd 5.4 #!/bin/sh # # Copyright (c) 2001-2005 Douglas Barton, [EMAIL PROTECTED] # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1.

Re: gcc -pthread

On Thu, 15 Jun 2006, Mark Andrews wrote: Is there any good reason why gcc -pthread links in -lpthead except when -shared is specified? Because one may want to build applications to use different threading libraries. Application A may work better with libthr, while

Re: gcc -pthread

On Thu, 15 Jun 2006, Mark Andrews wrote: Is there any good reason why gcc -pthread links in -lpthead except when -shared is specified? Because one may want to build applications to use different threading libraries. Application A may work better with libthr, while

AMD64 kernel builds are broken

Doug, Your recent commit appears to have broken buildkernel on AMD64. For some reason the COMPAT_LINUX32 option is not honored, so I get the wrong header files. /usr/obj/usr/src/make.amd64/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O2

build fails on amd64 machine

I get the following: === ipmi (depend) make: don't know how to make ipmi.c. Stop *** Error code 2 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

[releng_6 tinderbox] failure on amd64/amd64

TB --- 2006-06-15 19:39:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-06-15 19:39:41 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2006-06-15 19:39:41 - cleaning the object tree TB --- 2006-06-15 19:40:26 - checking out the source tree TB --- 2006-06-15 19:40:26 -

[releng_6 tinderbox] failure on i386/i386

TB --- 2006-06-15 21:26:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-06-15 21:26:43 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2006-06-15 21:26:43 - cleaning the object tree TB --- 2006-06-15 21:27:19 - checking out the source tree TB --- 2006-06-15 21:27:19 - cd

Re: atheros 'device timeout'

On 6/14/2006, Sam Leffler [EMAIL PROTECTED] wrote: Reid Linnemann wrote: Thanks Sam, I've disabled power save mode in both wireless windows clients and I'll see if the problem lightens up. Also, do you know why device timeouts would be spat out by the driver when no stations are associated

Help? 6.1-S: Fatal trap 12: page fault while in kernel mode

I had one of these a couple of weeks ago or so; I had been distracted by some more urgent matters that came up (the panic was on a machine under test; the more urgent matters were little things like needing to deploy a handful of resolvers on our network because existing ones were running on

USB MGE UPS problem

Hi, I am trying to use an MGE Pulsar Extreme UPS with the NUT port using the newhidups driver. I can read the values just fine but I can't set anything which precludes the PC from shutting the UPS off (or in fact configuring it in any way). The error is... ... Looking up DelayBeforeStartup

Re: USB MGE UPS problem

On Friday 16 June 2006 11:48, Daniel O'Connor wrote: usb_control_msg: 33 9 791 0 0x514f34 8 4000 USB error: error sending control message: Input/output error Set report failed FAILED ktrace shows.. 26140 newhidups RET write 89/0x59 26140 newhidups CALL

RE: save-entropy

That would be the old 'accidentally deleted a # from a line in rc.conf' problem. There are likely to be several lines beginning '# -- ' in the file. New users often accidentally remove the # making the '--' into a command. There will also be a few messages during startup that will also complain

Re: build fails on amd64 machine

Sean McNeil writes: | I get the following: | | === ipmi (depend) | make: don't know how to make ipmi.c. Stop | *** Error code 2 That should be fixed. Doug A. ___ freebsd-stable@freebsd.org mailing list

Re: save-entropy

Thanks Scott, But unfortunately, that's not the case... With ps ax I found a process 1 ?? ILs0:00.00 /sbin/init -- Strange stuff, grrr The server is on a datacenter, I don't see the startup messages... Olivier Scott, Brian a écrit : That would be the old 'accidentally deleted a #