I wrote:
: This problem should exist in -current since I think FreeBSD finally drops
^^
That should be "shouldn't". I shouldn't post in a hurry (like I'm doing
now).
-Ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
Exception-handling is broken with -O in -stable, and has been for years.
FreeBSD is one of the few systems that use setjmp/longjmp stack unwinds
to implement exceptions, so when the GCC folks broke that path, it was
never fixed. There are supposedly patches floating around that fix the
problem, b
Doug Barton wrote:
: Pending Mark's approval, I'd like to suggest we add a cron job to
: dump X k of data from /dev/random to a file (/boot/.periodic_entropy
: maybe?) and use that, AND ${entropy_file:/var/db/entropy} to reseed at
: boot, and only do the "long, annoying" failover process if
Doug Barton wrote:
: Pending Mark's approval, I'd like to suggest we add a cron job to
: dump X k of data from /dev/random to a file (/boot/.periodic_entropy
: maybe?) and use that, AND ${entropy_file:/var/db/entropy} to reseed at
: boot, and only do the "long, annoying" failover process if
In real life, machines don't always get rebooted in a completely
controlled fashion (panic, power failure, etc.). Anything that
makes a reboot longer or less reliable is a definite non-starter.
I can guarantee you, if the current /dev/random code isn't fixed before
it makes STABLE, folks running
Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
: This is marvellous in it's simplicity of interface.
:
: Yet, using sizeof(char) and assuming that it's going to be 1, strikes me
: like a dangerous thing to do. I have never heard of machines where this
: isn't true, but I seem to recall that the co
Just FYI; the appended message was posted to the EGCS developer's list
five days ago. Although H. J. Lu seems to be targeting only Linux, the
fact that he mentions testing under Solaris (both Sparc and x86) suggests
that he might be open to some input from us as well.
-Ed
Da
