postgres, initdb, FreeBSD bug?

I've been fighting with a bug I can't quite seem to figure out and was told that this might be the place to come. I'm running postgresql-9.2.2 on FreeBSD 8.3-RELEASE-p5 and am having things break down when I try to run initdb. I got in contact with the pgsql-general mailing list and we debugged the

Re: postgres, initdb, FreeBSD bug?

I just compiled a generic kernel and tried it again.. same error. So no funny business going on with my kernel settings it seems. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send a

postgres, initdb, FreeBSD bug?

I've been fighting with a bug I can't quite seem to figure out and was told that this might be the place to come. I'm running postgresql-9.2.2 on FreeBSD 8.3-RELEASE-p5 and am having things break down when I try to run initdb. I got in contact with the pgsql-general mailing list and we debugged the

Re: Fix overlinking in base aka import pkgconf

On Sat, Dec 15, 2012 at 12:54:19AM +0100, Baptiste Daroussin wrote: > Hi, > > Some of our binary are overlinked, the way we handle the linking doesn't help > for that. What do you mean there ? Do you mean that some libraries specified for the linking stage of the final binary are not needed for th

Fix overlinking in base aka import pkgconf

Hi, Some of our binary are overlinked, the way we handle the linking doesn't help for that. On proposition could be to use pkgconf https://github.com/pkgconf/pkgconf which is BSD license pkg-config implementation 100% compatible with pkg-config. What I propose is to create a new PCADD variable f

Re: NetBSD's boot select MBR

> > > So I use NetBSD's MBR for disks I want > > > to boot from. > > > > Can I have a CMD sequence? > > > > First would be ... > > # fetch ... > > Read NetBSD's fdisk(8) and mbr(8). > > The MBR is only 512 bytes, and must contain the code and data. > This is very limiting, so there are multiple v