From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ape pwd.h not in sync ?
Date: Thu, 18 Dec 2008 14:45:48 +0000 [thread overview]
Message-ID: <638bc3e3b9d220e6fd3d756fd5b2006b@terzarima.net> (raw)
In-Reply-To: <35d1fb81-fc46-4938-bacd-32254ff345d6@o40g2000prn.googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 136 bytes --]
it won't work, so it's better to find that out when
you compile the program rather than waste time compiling
it only to fail when run.
[-- Attachment #2: Type: message/rfc822, Size: 2919 bytes --]
From: prem <prem.mallappa@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] ape pwd.h not in sync ?
Date: Wed, 17 Dec 2008 16:55:09 GMT
Message-ID: <35d1fb81-fc46-4938-bacd-32254ff345d6@o40g2000prn.googlegroups.com>
Hi All,
the ape/pwd.h has the following
(in short pw_passwd missing, is this something unwanted ?)
struct passwd {
char *pw_name;
uid_t pw_uid;
gid_t pw_gid;
char *pw_dir;
char *pw_shell;
};
Linux has:
struct passwd
{
char *pw_name; /* Username. */
char *pw_passwd; /* Password. */
__uid_t pw_uid; /* User ID. */
__gid_t pw_gid; /* Group ID. */
char *pw_gecos; /* Real name. */
char *pw_dir; /* Home directory. */
char *pw_shell; /* Shell program. */
};
BSD:
struct passwd {
char *pw_name; /* user name */
char *pw_passwd; /* encrypted password */
uid_t pw_uid; /* user uid */
gid_t pw_gid; /* user gid */
time_t pw_change; /* password change time */
char *pw_class; /* user access class */
char *pw_gecos; /* Honeywell login info */
char *pw_dir; /* home directory */
char *pw_shell; /* default shell */
time_t pw_expire; /* account expiration */
};
Cheers,
/Prem
next prev parent reply other threads:[~2008-12-18 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 16:55 prem
2008-12-18 14:45 ` Charles Forsyth [this message]
2008-12-18 15:21 ` lucio
2008-12-18 19:12 ` C H Forsyth
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=638bc3e3b9d220e6fd3d756fd5b2006b@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).