Hi Keith, everyone,
> Thats interesting since "ldd initdb" and "ldd pg_ctl" show that there
aren't any
> .so's needed. Have you tried using the debugger to see whats is
causing the fault.
And this problem didn't exist on my old minimal system (Linux
2.2.20/libc-2.1.3)
pg7.1.2 either. All of which are running from pure ramdisk.
> If you are trying to build a "runtime" (Linux and PostgreSQL running
live from a
> CD) you might want to use install a minimum files system first and
then merge
> that filesystem that into something like the Slackware disc 2 CD.
I've done
> that before to make customized runtime/recovery CD's.
Well, sort of. What i'm actually trying to create is an embedded
environment
using a Slackware 9 (kernel upgraded) setup as dev't machine.
> For PostgreSQL, you'd need a way to put it on a filesystem that it
thinks is
> writeable so you'd probably need a kernel that supports a very large
ramdisk.
> I'm just guessing since I've never attempted to put PostgreSQL on
runtime CD but
> this has been discussed before so maybe someone else has had some
success.
Ok, here're some more details:
My min environment is comprised of images (initrd, tgz, and cramfs) that
boots off
from a compact flash and then exploded/mounted into ramdisk. The tgz
image tree
serves as a backupable image, and holds all common writeable paths. It
will also
hold the future postgres database if it will be required that the DB
should be
backupable.
The Postgres7.4 bins & libs (/usr/local/pgsql/*) on the other hand, is a
cramfs
image, and thus, is read-only. An attempt to create a DB on /tmp/db
(/tmp is on ramdisk) yields to the "SIGSEGV" message. Any command
involving
"initdb", "pg_ctl" and "initlocation" yields to the said error. I
repeat, this environment
uses almost pure busybox (only "mount" is taken from slackware).
Anymore hints/advise is very much appreciated.
TIA & best regards - Vic
