Re: BSD license compatible hash algorithm?

GC> Date: Thu, 27 Dec 2007 16:34:32 -0800 GC> From: Garrett Cooper GC> On Dec 27, 2007, at 4:30 PM, Garrett Cooper wrote: GC> GC> > Just wondering if anyone knew of a good BSD license compatible GC> > key-based hash placement / retrieval algorithm that was available GC> > anywhere. GC> GC> 1. It n

Re: BSD license compatible hash algorithm?

PJ> Date: Sun, 30 Dec 2007 08:35:21 +1100 PJ> From: Peter Jeremy PJ> On Sat, Dec 29, 2007 at 08:50:14PM +0000, Edward B. DREGER wrote: PJ> > PJ> >perfect_hash = ( hash1[x] + hash2[x] ) % entry_count ; PJ> This relies on pre-knowledge of all possible entries. It's P

ldconfig "skipping" libraries (6.1-R)

Greetings all, I'd been going nuts trying to determine why I couldn't link against "libdb-4.4.so" and a few other libraries. The ones in question didn't show up via ldconfig -r although their respective directories _were_ found. (Yes, I even ran "ldconfig -R" for good measure.)

kernel not linking (4.10-R + GCC-3.3.5 + binutils-2.15)

Greetings, Apologies in advance if this is better suited for another forum. I have a mostly-stock 4.10-RELEASE system, save for GCC 3.3.5 and binutils 2.15. After bootstrapping the GCC/binutils builds with stock versions, I self-built the new GCC and binutils. I can compile and link most softw

working(?) 4.10-R + gcc-3.3.5 + binutils-2.15

Greetings all, After several obstacles, I think I successfully upgraded the toolchain on 4.10-RELEASE. My Google searches along the way yielded tales of several other attempts, but no documented successes. Here's what I had to do: * Fix bug in binutils-2.15 ./bfd/configure that lumps 4

Re: working(?) 4.10-R + gcc-3.3.5 + binutils-2.15

EBD> Date: Sun, 12 Dec 2004 07:31:53 + (GMT) EBD> From: Edward B. Dreger EBD>* Force binutils OUTPUT_FORMAT to "elf32-i386" to match stock EBD> 4.10-R, lest I must make world due to binutils' default EBD> "elf32-i386-freebsd"

Re: urgent, need to recover superblock!

First, copy the entire drive to a file on another drive. Don't mess around with the original drive. The vnode disk driver is your friend. I can't find the quick-and-dirty tool I hacked up a few years back when I needed to recover a MBR... however one can scan a sector at a time, find likely p