From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Terrence Brannon <metaperl@urth.org>
Cc: cygwin@cygwin.com
Subject: Re: postgresql setup on cygwin --- initdb fails
Date: Sat, 04 Oct 2003 16:10:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0310041129000.15176@slinky.cs.nyu.edu> (raw)
In-Reply-To: <3F7EE6C1.2020006@urth.org>
On Sat, 4 Oct 2003, Terrence Brannon wrote:
> Jason Tishler wrote:
>
> >Terrence,
> >
> >On Sat, Oct 04, 2003 at 07:33:57AM -0700, Terrence Brannon wrote:
> >
> >
> >>IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not
> >>implemented
> >
> >Did you forget to start ipc-daemon2?
>
> No, I didn't forget to read it... I just didn't know where to start with
> getting Postgresql up and running... how was I supposed to know that
> file existed? I mean this in all earnesty.
>
> Is there a common protocol that I can use to be guided through the
> initial usage phase of each module installed on my system? Ie, something
> like
>
> INIT --package=cvs
> INIT --package=pgsql
>
> or to find the user's guide for my installed packages?
>
> >Please read the README:
> > http://www.tishler.net/jason/software/postgresql/postgresql-7.3.4.README
>
> will do
Terrence,
Most packages come with a Cygwin-specific readme that should be in
/usr/share/doc/Cygwin/pkgname-ver.README. Older packages may still have
it in /usr/doc/Cygwin/pkgname-ver.README, so check both places when in
doubt. The Cygwin-specific readme will either tell you what you need to
know, or will refer you to the location of the upstream README (which is
also installed on your system, usually in /usr/{share/,}doc/pkgname-ver/.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2003-10-04 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 23:58 Utility to dereference Windows shortcuts? Tom Cyglist
2003-08-12 1:27 ` Igor Pechtchanski
2003-08-12 20:34 ` Rob
2003-08-12 23:36 ` Igor Pechtchanski
2003-09-18 17:20 ` Rob S.i.k.l.o.s.
2003-10-04 14:47 ` postgresql setup on cygwin --- initdb fails Terrence Brannon
2003-10-04 15:19 ` Jason Tishler
2003-10-04 16:08 ` Terrence Brannon
2003-10-04 16:10 ` Igor Pechtchanski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0310041129000.15176@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin@cygwin.com \
--cc=metaperl@urth.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).