From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Guile scripts and setuid bit -> trouble
Date: Wed, 12 Jan 2005 11:48:25 +1100 [thread overview]
Message-ID: <87brbvsc9y.fsf@zip.com.au> (raw)
In-Reply-To: opcbrbwkf17.fsf@kanaha.am.mot.com
Roland Besserer<roland@motorola.com> writes:
>
> p.s. By the way, I found that the guile-1.6.4 build on OSX does not support
> the Posix user information calls like (cuserid).
It's supposed to, if they exist. The glibc manual says cuserid is
deprecated, and removed from recent posix.
(The Guile manual probably ought to say when a function, ie. a guile
function, doesn't always exist.)
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-12 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 0:26 Guile scripts and setuid bit -> trouble Roland Besserer
2005-01-08 2:08 ` Andy Wingo
2005-01-09 7:11 ` Paul Jarc
2005-01-10 8:16 ` tomas
2005-01-11 0:03 ` Roland Besserer
2005-01-11 9:06 ` tomas
2005-01-12 0:48 ` Kevin Ryde [this message]
2005-01-11 1:08 ` Roland Besserer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87brbvsc9y.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@gnu.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).